...
Client uses client ID and client secret to obtain an access token
Request
Description
When you were established as a PKB partner, you will have been issued with a client ID and a client secret. You use these to obtain an access token when you need one.
...
Parameter | Type | Optionality | Description | Example |
grant_type | Form parameter | Required | Must be "client_credentials" | client_credentials |
Authorization | HTTP header | Required | This is a standard HTTP basic authorization header. The value should be a Base64 encoding of your client ID and client secret, concatenated together with a colon (:) separator, and prepended with "Basic ". For example, if your client ID was example_client_id and your client secret was example_secret then your header value should be: Basic ZXhhbXBsZV9jbGllbnRfaWQ6ZXhhbXBsZV9jbGllbnRfc2VjcmV0 | ZXhhbXBsZV9jbGllbnRfaWQ6ZXhhbXBsZV9jbGllbnRfc2VjcmV0 |
Content-Type | HTTP header | Required | Must be "application/x-www-form-urlencoded" | application/x-www-form-urlencoded |
Response
Description
PKB responds with the access token in JSON. Note that a refresh token is never provided from a Client Credentials Grant workflow; when your access token expires you can repeat the Client Credentials Grant workflow to obtain a new one.
...