Authentication

Public API requests require authentication via an org-scoped API key. Each key grants access to the supported Extract, Enrich, and Explore resources for one organization. Requests without a valid key receive a 401 Unauthorized response.

Compatible agent clients use OAuth through the separate MCP endpoint rather than an API key. See Connect through MCP.

Getting your API key

  1. Sign in to the Extralt dashboard
  2. Select your organization
  3. Navigate to API key settings
  4. Create a new API key
API key settings page

API keys are org-scoped. Each key is tied to a specific organization. If you have multiple organizations, generate a separate key for each.

Using your API key

Include your API key in the Authorization header as a Bearer token:

Authorization: Bearer your-api-key

Example request

curl "https://api.extralt.com/v1/extract/robots" \
  -H "Authorization: Bearer your-api-key"

The SDKs send the header for you.

Base URL

All API requests use the host https://api.extralt.com with a versioned, pipeline-scoped prefix:

https://api.extralt.com/v1/extract/...   # Robots, Runs, Schedules, Captures, Imports
https://api.extralt.com/v1/enrich/...    # Enrichments, Items
https://api.extralt.com/v1/explore/...   # Explore evidence and Analyses

Security

Treat your API key like a password. Do not commit it to version control or expose it in client-side code.

  • Store keys in environment variables or a secrets manager
  • Rotate keys periodically
  • Revoke compromised keys immediately from the dashboard; the API stops accepting a revoked key within a minute
  • Each key is scoped to one organization and cannot access other orgs' data

Error responses

If authentication fails, the API returns a 401 Unauthorized response:

{
  "error": {
    "code": "unauthorized",
    "message": "A valid Bearer credential is required",
    "request_id": "019..."
  }
}

See the generated OpenAPI document for endpoint-specific response schemas.

Next steps