Since Cerkl API is secure, user will need to grab credentials to be able to enter OAuth 2.0, which is the security protocol used by Cerkl Broadcast.


This is an approximation based on average time spend for existing Cerkl Broadcast clients.


Comms Expert
SSO Expert
Intranet Hosting Expert
These are the suggested technical resources needed to complete this task.

In order to secure our API, Cerkl Broadcast platform uses OAuth 2.0, which has become the “industry-standard protocol for authorization”. You’ll need to grab a client ID and a client secret from the Settings → Integrations & Plugins → Cerkl API v3 page. Hit the “Generate New OAuth Credentials” button and name your new OAuth 2.0 client credentials something useful.

Getting an Access Token

Once you have your client credentials, you will need to authenticate with our OAuth 2.0 server to receive an access token. This token is your key to using Cerkl API v3 in your codebase, “the thing that applications use to make API requests on behalf of a user” if you will.

To authenticate with your client credentials and receive an access token, it depends on how you are working with Cerkl’s API.

Authenticating Programmatically

To authenticate within your codebase, use any library/tool capable of making HTTP requests to POST your client credentials to our OAuth 2.0 token endpoint. Using cURL, you might end up with something like this:

    $ curl -v \
        -H "Accept: application/json" \
        -H "Accept-Language: en_US" \
        -u "{client_id}:{client_secret}" \
        -d "grant_type=client_credentials"

Using valid client_id and client_secret credentials, you should receive an access token upon successful completion of your request to our OAuth 2.0 server. You can use this access token in your code to start making useful API calls and integrating your systems.

Authenticating in Postman and the API Reference

Authenticating in Postman and our API Reference page is straightforward and can be done completely via UI elements. Visit those documentation pages for more information.

Access Token Lifetime

As a point of security, the access tokens we issue only last 12 hours. In the event your processes that use our API take longer than that, we recommend splitting your integration tasks up into multiple jobs or utilizing the refresh token provided to you during authentication.

If you have any questions at all, don’t hesitate to reach to our team via email or use the chat support in the bottom right-hand corner of any page for a quick answer.
Getting an Access Token