question

Upvotes
Accepted
58 0 3 4

"Invalid client" error for sub-sequent requests via POST /token from RDP API

Client stucks with requesting a token for sub-sequent requests via POST /token from our API.


Can you give me some hint what might be our client_id and whether this really is the issue I am facing? The highlighted (yellow) parts are related to where I believe the issue is located, but still maybe I'm wrong.


Thanks

Ronny

rdp-apirefinitiv-data-platformauthenticationtoken
icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Upvote
Accepted
14k 61 39 63

Hi @ronny.holzaufderheide,

The client_id is a unique ID used by the platform to identify a specific application. The client should refer to the Quick Start guide which describes what this ID is and how to obtain it.

They can refer to the following section within the Quick start and click on the associated link to create the ID:


ahs.png (24.2 KiB)
icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Upvotes
18.1k 35 12 12

Hello @ronny.holzaufderheide

Please note that you can create the Client ID (aka App Key) via the following ways:

  • via Eikon Desktop/Refinitiv Workspace application: go to the Search Bar and type "APP KEY", then select the AppKey Generator
  • via AppKey Generator website.
icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.