• Obtaining Through Client Secret

Obtaining authorization header value by Client ID and Client Secret

For testing purposes you can use the 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.

If you plan to deploy your client or integration, please contact us via the API Contact Form to get your unique client ID for your purpose. Please keep in mind, that the client ID mentioned here must not be used for production code and will be changed in future at any time without prior comment.

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=