• Obtaining Through Client Secret

Obtaining authorization header value by Client ID and Client Secret

For evaluation and prototyping only, you can use the shared public demo client ID yjavNwKpd4HgbQes0ekYHBGjxIoszJgayIc0JkdB. This is the same client ID the API Token Generator issues refresh tokens for, so tokens generated there work with all examples in this documentation.

The demo client ID must not be used for production code and may be changed at any time without prior notice. For production, request your own dedicated Client ID via the API Contact Form — see Obtaining a ClientID for your Application for how to choose the right client type, OAuth flow, redirect URIs, scopes, and (if applicable) Client Secret.

You need to base64-encode it ("yjavNwKpd4HgbQes0ekYHBGjxIoszJgayIc0JkdB:") to get the authorization header value:

Authorization: Basic eWphdk53S3BkNEhnYlFlczBla1lIQkdqeElvc3pKZ2F5SWMwSmtkQjo=

You can use a online base64 encoding tool or in a Linux/Mac/WSL/WSL2 shell

echo -n "yjavNwKpd4HgbQes0ekYHBGjxIoszJgayIc0JkdB:"|base64

Important: The length of base64 encoded string needs to be a multiple of 4, fill up with = if needed.

Obtaining Through Client Secret

You need to base64-encode it ("<client_id>:<client_secret>") to get the authorization header value:

Authorization: Basic eWphdk53S3BkNEhnYlFlczBla1lIQkdqeElvc3pKZ2F5SWMwSmtkQjowZWtZSEJHanhJb3N6SmdheUljMEprZEI=