Authentication

Seal uses organisation API keys. Pilot access is configured with the team running the workflow, then keys are managed in Settings → API Keys.

Use a key

Aqta keys begin with aqta_.

http
Authorization: Bearer aqta_your_key

python
import os
from openai import OpenAI

client = OpenAI(
    base_url="https://api.aqta.ai/v1",
    api_key=os.environ["AQTA_API_KEY"],
)

typescript
import OpenAI from 'openai';

const client = new OpenAI({
  baseURL: 'https://api.aqta.ai/v1',
  apiKey: process.env.AQTA_API_KEY,
});

Key handling

  • Store keys in a server-side secret manager or environment variable.
  • Do not put keys in browser code, source control, tickets, or screenshots.
  • Use separate keys for separate environments where that helps you investigate a workflow safely.
  • Revoke a key immediately if you believe it has been exposed.

Rotate a key

  1. Create a replacement key in Settings → API Keys.
  2. Update the deployed secret.
  3. Confirm the workflow is using the replacement.
  4. Revoke the old key.

Errors

A missing, invalid, or revoked key returns 401. Check the key and its organisation before retrying. A temporary request limit may return 429; use bounded exponential backoff rather than repeatedly sending the same request.

Next steps

Last updated: May 2026