Endpoint
Resource URL:
POST https://api.ft.com/cont-acc-tkn/sign
For security reasons requests must be made over HTTPS.
Header |
Value |
Content-Type |
application/json |
x-api-key |
<API key value> |
A json representation containing an expiryTime and a list of content UUIDs. An example of which is shown below
{ “contentUUIDs”:[“c0ce9150-9a10-4890-936b-0b63a90fb4b0”], “expiryTime”:“2016-10-30T18:36:14Z” } |
The token is encoded with msgpack to reduce its size and signed using crypto-signatures. The token representation is <token>.<signature>. The token can be verified using the service’s public key.
Http Status |
Description |
201 Created |
The content access token is created successfully. |
400 Bad request |
The request was invalid. You may refer to response for details around why the request was invalid. |
403 Forbidden |
The x-api-key provided is invalid. Whenever the user provides an x-api-key, validation against an api key whitelist is performed. If the x-api-key provided is not in the whitelist, this error is returned. |
415 Unsupported Media Type |
Ensure you use the correct Content-Type header in the request as indicated in the Request Headers section above |
To use an access token, pass it as a query parameter with the key “accessToken” to the article link, e.g:
https://www.ft.com/content/2f52d42e-db67-11e6-9d7c-be108f1c1dce?accessToken=