C:\> Documentation

01

Getting your API key

Documentation

Everything starts with an ingest token — what your CI pipeline uses to push code snapshots to Codepanion.

Create one yourself: in the app, go to Settings → API key, give it a name (e.g. "GitHub Actions"), optionally set an expiry, and click Create token. It's shown once — copy it immediately and store it as a secret in your CI system (e.g. CODEPANION_TOKEN in GitHub Actions secrets). Your tenant ID is shown alongside it.

You can hold as many tokens as you like — one per CI system, say — and each can be revoked on its own. That makes rotation zero-downtime: create a new token, point your CI at it, then revoke the old one. No hard cutover, so nothing breaks mid-rotation. Each token shows when it was last used, so a stale or unexpectedly-active one is easy to spot.

Note

Ingest tokens are scoped to a single tenant and can only push code. They cannot read data, run queries, or access any other tenant.

Need help getting set up?

Every pilot customer gets hands-on onboarding from the founding team. We'll walk through setup together and make sure everything is working.