Skip to content

Commit a415e2e

Browse files
committed
formatting
1 parent c5cb271 commit a415e2e

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

README.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -142,6 +142,8 @@ But seriously... this is a bummer. We really want you to use the API. If you are
142142

143143
What if you want to use our API for a production service that cannot depend on the performance uncertainties of the free and open public API? What if you don't want to be affected by impolite people who do not follow the [API Etiquette](#api-etiquette) guidelines? Well, if you’re interested in using these tools or APIs for production services, we [have a service-level offering](https://www.crossref.org/services/metadata-delivery/plus-service/) called "Plus". This service provides you with with access to all supported APIs and metadata, but with extra service and support guarantees.
144144

145+
#### Authorization token for Plus service
146+
145147
When you sign up for the Plus service, you will be issued an API token that you should put in the `Authorization` header of all your rest API requests. This token will ensure that said requests get directed to a pool of machines that are reserved for "Plus" SLA users.
146148

147149
## API overview
@@ -735,4 +737,4 @@ Each major version has no backwards incompatible changes within its public inter
735737
- v57, 2018-02-01, document ISBN filter
736738
- v58, 2018-02-13, document `reference-visibility` filter for `/works` and `/members` routes
737739
- v59, 2018-02-13, added info about Mtedata Plus service. Corrected spelling. Added example of using `reference-visibility` filter.
738-
- v60, 2018-02-22, added info for "Plus" users on use of toekn in `Authorization` header.
740+
- v60, 2018-02-22, added info for "Plus" users on use of toekn in `Authorization` header.

0 commit comments

Comments
 (0)