Developer Hub

Welcome to CertCenter's Developer Hub. You'll find comprehensive guides and documentation to help you start working with CertCenter as quickly as possible, as well as support if you get stuck.

Let's jump right in!

Get Started Full API Reference

Authentication via OAuth2

OAuth2 authentication isn't as complicated as it looks like

Access to the CertCenter REST API requires previous registration as a CertCenter customer. After you signed up successfully, the authentication takes place by submitting your valid OAuth2 token (which you can obtain through the CertCenter UI) or via Client Credentials.

curl "https://api.certcenter.com/rest/v1/Limit" \
-H "Authorization: Bearer DW2JU3CRS9V3D9QST3JQ9E69.oauth2.certcenter.com"

Credentials Grant

The OAuth2 protocol can be very complicated. The good news: It is not mandatory to take care of the whole framework (RFC6749). CertCenter offers a neat user interface where you can interact with our OAuth2 system (e.g. obtaining your Bearer Tokens from.)

However, to obtain a fresh bearer token programmatically via OAuth2, use the client_credentials grant type:

curl -X POST 'https://api.certcenter.com/oauth2/token' \
-d 'grant_type=client_credentials&client_id=#ClientID#&client_secret=#ClientSecret#&scope=#scope#'

Valid scopes are: profile, read, quote, write, limit, voucher and order

To get more detailed information about ClientIDs, secrets and scopes, please create your first Application through our UI: https://my.certcenter.com/my/profile/apps

Response to the call:

{
  "access_token": "avalidtoken.oauth2.certcenter.com",
  "token_type": "Bearer",
  "expires_in": 86400,
  "refresh_token": "avalidrefreshtoken.oauth2.certcenter.com"
}

Authentication via OAuth2

OAuth2 authentication isn't as complicated as it looks like