Authentication

Every authenticated request to the Teak API must include a bearer token so we can identify the calling organization. Tokens are scoped to a single organization, and you can create or revoke keys at any time.

To create a token, open your organization settings, navigate to API keys, and generate a new key. Store it in your secrets manager and reuse it across server-side jobs or integration services.

Send the token in the Authorization header using theBearer scheme. Authenticated endpoints return a 401 response when the header is missing or invalid.