Setup → Settings → Developer API is where you generate API keys for scripting against ComplyJet's external API — CI/CD pipelines, internal tooling, Slack bots, or anything else that needs programmatic access.
Every key shows its Scope, Last Used date, Created date, and Status — useful for spotting old keys nobody's using anymore, or confirming a key is actually being hit before you assume an integration is broken.
Creating a key
Create API Key asks for two things:
Name — something identifiable, like what system or person it's for (e.g. "CI/CD Pipeline", "Slack Bot") — this is what you'll be looking at months later trying to remember what it's for.
Scope — Read Only or Read & Write. Default to Read Only unless the integration specifically needs to create or update data through the API.
Back on the list, every key is shown as a masked prefix (cj_live_...) — treat the full value as sensitive the moment it's issued, and store it in a secrets manager rather than pasting it somewhere you'll forget about.
Revoking a key
Existing keys in the list can show as Active or Revoked. If a key is no longer needed — an old integration, a departed teammate's personal key — revoke it rather than leaving it active indefinitely.