Specifically I do not know what to enter in the ‘Authorization’ header field. The documentation states that the “header parameter contains the token_type and the access_token”. Can anyone enlighten me as to what a ‘token_type’ and ‘access_token’ are as I cannot find any prior reference to these two terms in any of the documentation?
What I have done is set a header called “Accept” with the value “Application/pdf”. Then created a Authorization header using basic Authorization with your API key as the username and the password being blank
Anyway I have subsequently tweaked my code and it now works, but have since discovered the document fetch process consists of two-stages. The first stage is the call to “document/FIxRR8teCKodjkBLRDHv2Cb8y0-nQ7T5G3BEXfWtOu4/content” (as per your example and with the correct request headers) which returns a HTTP response “Location” header, the value of which is the document download URL location. The second stage requires making a connection to that URL to retrieve the actual document.
Returning to the online form I can now take a stab at what input is required (although I could not get it to work ):
id field : document/FIxRR8teCKodjkBLRDHv2Cb8y0-nQ7T5G3BEXfWtOu4
authorisation: Basic T3FKdC1GekxLNHU2ePlusRestOfEncodedKey
accept: application/pdf
I understand the service is still Beta but hopefully the documentation will be improved to remove the guesswork and confusion.
Part of having the service out there in beta is to test the API design and associated documentation to find where it doesn’t meet user need.
The authorisation API’s and documentation are currently being extended, so the documentation will improve over coming months. If you find anything that is just plain wrong, of course shout !
Response body*
Failure while contacting API. Some possible causes are connection problems or cross-origin resource sharing protection. Please check javascript domains registered against APIKey / OAuth2 registration.