• Obtaining Through Client Secret

Obtaining authorization header value by Client ID and Client Secret

For testing only, you can use the sandbox client ID yjavNwKpd4HgbQes0ekYHBGjxIoszJgayIc0JkdB. The API Token Generator issues refresh tokens for this client ID.

If you plan to deploy your client or integration, please create your unique client ID as described in Obtaining a ClientID for your Application. 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=

In a Linux/Mac/WSL/WSL2 shell:

printf '%s' "yjavNwKpd4HgbQes0ekYHBGjxIoszJgayIc0JkdB:" | base64 | tr -d '\n'

Obtaining Through Client Secret

You need to base64-encode it ("<client_id>:<client_secret>") to get the authorization header value. As defined in RFC 6749, section 2.3.1, encode the client ID and the client secret with the application/x-www-form-urlencoded algorithm before joining and base64-encoding them. Example for my-client-id:my-client-secret:

printf '%s' "my-client-id:my-client-secret" | base64 | tr -d '\n'

Authorization: Basic bXktY2xpZW50LWlkOm15LWNsaWVudC1zZWNyZXQ=