docAnalyzer

Create and manage API keys

Create persistent keys for programmatic uploads, queries, and downloads. Revocable any time.

API keys give programmatic access to the same upload, query, and download surfaces as the docAnalyzer app. Use them when you want to integrate docAnalyzer into your own software, a workflow tool, a cron job, or a backend service.

Create a key

  1. 1

    Open account settings → API keys.

  2. 2

    Click Create key.

  3. 3

    Give the key a label, something memorable like "blog ingest" or "QA bot". Labels are for your tracking only; they're not part of the key string.

  4. 4

    Copy the secret immediately. It's shown once. After you close the dialog, only the label and a few-character prefix are visible.

  5. 5

    Store the secret somewhere safe (a secret manager, your CI variables, etc.).

If you lose the secret, you can't recover it; revoke the key and create a new one.

Use a key

Every API request authenticates by including the key in the Authorization header:

Authorization: Bearer <your-key>

See the API reference for endpoints and request shapes, and the API guide for the quick start. The Agents API (v2) is documented at API v2.

What a key can do

A key has the same permissions as the user who created it:

  • Upload documents.
  • List, fetch, and delete documents.
  • Open chats, send queries, retrieve answers and outputs.
  • Run agents (Blueprint, Data Extractor, etc.).
  • Access the chatbot context endpoint for embedded chatbots.

It cannot:

  • Manage other users, workspaces, or billing.
  • Create or revoke other API keys.
  • Change account settings.

Multiple keys

Create as many keys as you need; one per integration is the cleanest pattern. A separate key per integration means revoking one doesn't break the others.

Rotate a key

Best practice for long-running integrations:

  1. 1

    Create a new key.

  2. 2

    Update the integration to use the new key.

  3. 3

    Verify the integration works on the new key.

  4. 4

    Revoke the old key.

Revoke a key

API keys → row menu → Revoke. The key stops working immediately. Any in-flight requests using it complete; new requests fail with 401.

Quotas

API usage counts against the same plan limits as app usage: uploads, chats, storage, credits. The API doesn't have a separate quota; it pulls from the same bucket.

What's next

Was this helpful?