Skip to main content

Documentation Index

Fetch the complete documentation index at: https://reporting.continu.com/llms.txt

Use this file to discover all available pages before exploring further.

The API uses a static API token issued by Continu. The token is long-lived — you do not need to refresh it.

​
Getting a token

Contact your Continu account team. Tokens are issued per organization. Treat the token like a password:
  • Store it in a secret manager (AWS Secrets Manager, GCP Secret Manager, Vault, 1Password, etc.).
  • Never commit it to source control.
  • Rotate it immediately if you suspect exposure.

​
Sending the token

Include the token in the Authorization header on every request: 
Authorization: <your-token>
Confirm the exact header format (raw token vs. Bearer <token>) with your Continu contact when you receive your credentials — this can vary by deployment.

​
Token compromise

If you believe a token has been exposed:
  1. Email support@continu.co immediately to have the token revoked.
  2. A new token will be reissued.
  3. Audit recent API activity from your side for anything unexpected.
​
200 OK
success
Token accepted, request processed.
​
401 Unauthorized
error
Token missing, malformed, or revoked. Verify the Authorization header is present and the token is current.
​
403 Forbidden
error
Token is valid but lacks access to the requested resource. Contact your account team if you believe this is in error.