Skip to main content
API keys authenticate every request to Adapter. Keys are prefixed pk_live_… and are accepted on every public endpoint — connections, knowledge, runtime, and custom-connector ingest.

​
Creating an API key

1

Open the console

Log in at app.adapter.com and go to Settings → API keys.
2

Create a new key

Click Create API key. Give it a descriptive name (e.g. the service or environment that will use it).
3

Copy and store it

The full secret is shown once. Store it as an environment variable; never commit it to source control.
export ADAPTER_API_KEY="pk_live_..."

​
Using a key

Pass the key in the Authorization header as a bearer token: 
curl https://api.adapter.com/v1/knowledge/search \
  -H "Authorization: Bearer $ADAPTER_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"q": "Q1 launch plan"}'

​
Scopes

Keys carry scopes that restrict what they can do. A request without the required scope returns 403 insufficient_scopes with details.missing_scopes listing the gaps. See Errors for the full response shape. If you need finer-grained scopes than the console exposes, contact support.

​
Rotation

To rotate a key without downtime:
  1. Create a new key in the console.
  2. Deploy the new key to your services.
  3. Verify traffic on the old key has stopped.
  4. Revoke the old key.

​
Revoking a key

In Settings → API keys, find the key and click Revoke. Revocation is immediate — in-flight requests authenticated with the key complete, but new requests fail with 401 authentication_error. If you suspect a key has leaked, revoke it first and create a new one second.