• Obtaining Through Client Secret

Obtaining authorization header value by Client ID and Client Secret

The sandbox client yjavNwKpd4HgbQes0ekYHBGjxIoszJgayIc0JkdB is a system-defined, long-lived public OAuth client used by the API Token Generator and all examples in this documentation. It is intended for demo and ad hoc scripting only — not for production applications. It has no client secret, so you only need to base64-encode the client ID with a trailing colon.

For any real integration — end-user OAuth, server-to-server flows, or anything other than throwaway experiments — register a dedicated OAuth client for your app. See Obtaining a ClientID for your Application for how to choose the right client type and flow.

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=