For a deeper look into our DataScope Select REST API, look into:
Overview | Quickstart | Documentation | Downloads | Tutorials
Hi Team,
Can you please help us in creating an impersonation token V3, in postman with an expired token?
We are getting the below error in postman, but in refinitiv, we can successfully generate a new token, with expired token details. (And for the new token generation we are giving expired token and application ID in the request header only)
Thannk & Regards,
Urmila.
Hi,
Thank you for your participation in the forum.
Are any of the replies below satisfactory in resolving your query?
If yes please click the 'Accept' text next to the most appropriate reply. This will guide all community members who have a similar question.
Otherwise please post again offering further insight into your question.
Thanks,
AHS
<AHS>
Case 11446200 is closed with the following resolutions:
The client’s error rate is sparse. Comparatively very low. One client receives these errors between 15K and 16K daily. I’ve tried several scenarios throughout the day and found the X-TRKD-Auth-Token must be valid, otherwise, the “Object Reference” error is thrown. Another item to note, each client experiences the same error rate on a daily basis, likely representative of the rate at which the token refresh is called.
And:
Our specialists have confirmed that the Throttling Service was down on two of our API servers and we believe this is why you received the errors. The full error stack below indicated “Object Reference” error was thrown by Throttling.
Please be informed that a reply has been verified as correct in answering the question, and has been marked as such.
Thanks,
AHS
Hello @urmila.m
This issue needs to be investigated by the RKD support team. I highly recommend you contact the RKD support team directly via the my.refinitiv.com website.
Please note that you may need to provide your username, input token, and the response message's ErrorReference and ServerReference values to the team.
Hello @urmila.m
Could you please give us more detail about your postman request setting such as the request body, request headers, and request authorization?
I can replicate the same error message in postman by not setting the "X-Trkd-Auth-Token" Token in the request header. However, your use case seems to be different.
Note: Please remove (or hide) all of your credentials data before sharing.
Hi Please find attached details.. Here i am sending expired token but response some times getting token expired and some times getting Object reference error! If i use same expired token in refinitv its generating new token successfully.
Hi @urmila.m
Can you expand on what you mean by 'If i use same expired token in Refinitv its generating new token successfully ' - how or where are you using an expired token in Refinitiv?
If you refer to the tutorial on Tokens - you will note that you need to use the Refresh Token to generate the next access token.
HI,
i have already contacted RKD team via email, they have suggested (is posting a query in the Developer portal Q&A forum (https://developers.refinitiv.com/en), as this may be answered by the community. ) and also they said that the parameters you are using look fine, ie
Request Header :
X-Trkd-Auth-Token: [TOKEN]
X-Trkd-Auth-ApplicationID: [ApplicationID]
Content-Type: application/json;
Host: api.rkd.refinitiv.com
Request Body:
{
"CreateImpersonationToken_Request_3": {
"ApplicationID": "[ApplicationID]",
"Token": "[ImpersonatedToken]"
}
}
