Skip to Content

API tokens

Create personal tokens for scripts and tools that use the CodeLynq API, and manage connected AI assistants.

An API token lets a script, a CI pipeline or another tool use CodeLynq on your behalf. Each token belongs to your own account: it can do what you can do, limited to the scope you give it.

Create a token

  1. Click the shield icon at the bottom of the sidebar (Security settings).
  2. Under API tokens, click Create token.
  3. Enter a Token name that tells you where it is used, for example CI pipeline.
  4. Choose the Scopes:
    • Read only: view projects, tasks and runs.
    • Read and write: also create tasks, approve technical designs and start runs.
  5. Optionally set Expires in (days). Leave it blank for a token that never expires.
  6. Click Create token.
  7. Copy your token now: it is shown only once.

Use a token

Send the token with every request in the Authorization header:

Authorization: Bearer clp_...

The same token also works for connecting an AI assistant over MCP - see External AI assistants.

Everything done with a token is subject to the same limits and checks as in the app, and is recorded in the organization's audit log under your name.

Manage tokens

The list shows each token with the start of its value, its scopes, and when it was created, when it expires and when it was last used. Expired and revoked tokens are marked.

Click Revoke to stop a token. Anything using it stops working immediately.

Connected AI assistants

AI assistants you have connected through the sign-in and approval screen (OAuth) appear in the same list as OAuth · {name}, with a Connected app badge. Click Revoke to disconnect one.

Good to know

  • Give each tool its own token, so you can revoke one without affecting the others.
  • Choose Read only when a tool only needs to look.
  • Set an expiry for tokens in shared places such as CI.

Test it on a task from your own backlog

Send us one real task. We run CodeLynq on your repository and you review the pull request. Free, within 5 working days of approving the spec.