Skip to content

API Authentication

Eduardo Campillo edited this page May 15, 2026 · 1 revision

API Authentication

The Cerrion REST APIs require a valid Bearer token for every request. This token is issued by the Customer Success team and must be included in the Authorization header.

Requesting your token

To get access to the REST APIs, please contact your Customer Success representative. Provide the following information so they can generate the correct key for your integration:

  • Customer or account name
  • Project name or environment
  • Which API(s) you are integrating with (for example, Detections or Downtime)
  • Intended integration use case or target system

Once your request is processed, Customer Success will generate and share an authentication token for your project.

Using the token

Include the token in every API call using the Authorization header:

-H "Authorization: Bearer YOUR_ACCESS_TOKEN"

Example:

curl 'https://YOUR-PROJECT.cerrion.com/api/v1/detections' \
  -H 'Authorization: Bearer YOUR_ACCESS_TOKEN'

Best practices

  • Treat the token as a secret.
  • Do not embed it in client-side code or publish it in public repositories.
  • If you need a new token or if a token is compromised, contact Customer Success to rotate or regenerate it.

Token validation

If an API call returns 401 Unauthorized or 403 Forbidden, verify that:

  • the Authorization header is present
  • the header uses the exact format Bearer <token>
  • the token is the one provided by Customer Success

If the request still fails, reach out to Customer Success for assistance.

Clone this wiki locally