For a deeper look into our DataScope Select REST API, look into:
Overview | Quickstart | Documentation | Downloads | Tutorials
The intention of a Token is for efficiency / re-use.
Aim for DSS users should be to poll the Authentication/RequestToken endpoint once (or a few a times as possible) using DSS (Basic) credentials to retrieve the Token "value", then re-use that Token in any DSS requests going forward for as long as the Token is valid.
I believe a Token is valid for 24 hours.
The concept of test users does not apply relating to this question.
I confirm: a token is valid 24 hours.
Page 8 "Reuse Authentication Tokens for Faster Authentication" in Best Practices (for DataScope Select) (Developer Community access required) should help here.
Sourced from: https://hosted.datascopeapi.reuters.com/RestApi.Help/Home/Index (DSS access required)
Thank you for the answer. I understand the concept of the session token. But my scenario would make just one API Request once a day. If I can call the API directly with basic authentication without getting the token first, this would considerably reduce the implementation effort on the middleware that is making the API call. So I want to make sure: Is basic authentication supported for REST API requests?
Given you've mentioned that your scenario would make just one API Request once a day, then my view is that you should be able to use the Basic within the 1 request per day. In the 1 step workflow example you've mentioned adding the Authentication/RequestToken call first adds an unrequired step. If you find that your DSS workflow does requires more than the one request to DSS only then does it become best to retrieve the Token within a daily workflow.