Chronicle · Authentication Profile

Chronicle Authentication

Authentication

Chronicle secures its APIs with apiKey and oauth2 across 3 declared security schemes, as derived from its OpenAPI definitions. OAuth 2.0 is offered via the authorizationCode, deviceCode, and refreshToken flow(s).

CompanyCloud SaasPresentationsArtificial IntelligenceProductivityContent GenerationAgentsMCPDeveloper API

Methods: apiKey, oauth2 Schemes: 3 OAuth flows: authorizationCode, deviceCode, refreshToken API key in: header

Security Schemes

apiKeyAuthorization apiKey

· in: header (Authorization)

apiKeyHeader apiKey

· in: header (x-api-key)

mcpOAuth oauth2

· flows: authorizationCode, deviceCode

Source

Authentication Profile

generated: '2026-07-18'
method: searched
source: https://docs.chroniclehq.com/authentication
docs: https://docs.chroniclehq.com/authentication
summary:
  types: [apiKey, oauth2]
  api_key_in: [header]
  api_key_headers: [Authorization, x-api-key]
  oauth2_flows: [authorizationCode, deviceCode, refreshToken]
schemes:
- name: apiKeyAuthorization
  type: apiKey
  in: header
  parameter: Authorization
  format: 'Bearer <API_KEY>'
  scope: workspace
  key_prefix: chr_
  notes: >-
    Workspace-scoped API key for the REST API at /api/v1. Created in Chronicle web app
    Settings -> API by a workspace admin; shown once. Keys are revoked (not hard-deleted)
    to preserve audit visibility. Requests are rate limited per key.
- name: apiKeyHeader
  type: apiKey
  in: header
  parameter: x-api-key
  format: '<API_KEY>'
  scope: workspace
  notes: Alternative header form of the same workspace-scoped API key. Use one method consistently.
- name: mcpOAuth
  type: oauth2
  applies_to: MCP server (https://mcp.chroniclehq.com)
  authorization_server: https://login.chroniclehq.com
  flows:
  - flow: authorizationCode
    authorizationUrl: https://login.chroniclehq.com/oauth2/authorize
    tokenUrl: https://login.chroniclehq.com/oauth2/token
    pkce: [S256]
  - flow: deviceCode
    deviceAuthorizationUrl: https://login.chroniclehq.com/oauth2/device_authorization
  grant_types_supported: [authorization_code, client_credentials, refresh_token, 'urn:ietf:params:oauth:grant-type:device_code']
  token_type: JWT
  notes: >-
    The MCP path uses OAuth 2.0 against login.chroniclehq.com and carries a JWT bearer
    token. JWT-auth errors surface as JWT_INVALID / JWT_EXPIRED / JWT_WRONG_AUDIENCE /
    JWT_SIGNATURE_INVALID. MCP requests require workspace_id in body or query
    (else WORKSPACE_ID_REQUIRED).

Work with this as data

Every security artifact here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for security posture

4 MCP tools reach this

find_securityBrowse and filter every security artifact in the catalog.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This security artifact

curl "https://apis.io/api/v1/security/chronicle-authentication"

All security posture

curl "https://apis.io/api/v1/security?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.