Skip to main content
You’ll need to authenticate your requests to access any of the endpoints in the ELAN AI Bridge API. In this guide, we’ll look at how authentication works. ELAN AI Bridge uses API Keys for authentication and a custom X-Org-Id header to identify the organization you are working with.

​
API Key authentication

The only way to authenticate with the ELAN AI Bridge API is by using an API Key. When establishing a connection using an API Key, you will need your API Key — you can find it in the developer settings under the Credentials settings. Here’s how to add the API Key to the request header using cURL:
Example request with API Key
curl https://api.elanlanguages.ai/v1/conversations \
  -H "Authorization: Bearer {apiKey}" \
  -H "X-Org-Id: {orgId}"
Always keep your token safe and reset it if you suspect it has been compromised.

​
Organization identification

The X-Org-Id header is used to identify the organization you are working with. The organization ID is a unique identifier for your organization and is used to identify the organization you are working with. You might be member of multiple organizations. If you don’t provide the X-Org-Id header, the API will default to your default (or ‘active’) organization. You can find your organization ID in the developer settings under the Credentials settings or by consulting the /v1/users/me/organizations endpoint.
Example request to get your organizations
curl https://api.elanlanguages.ai/v1/users/me/organizations \
  -H "Authorization: Bearer {apiKey}"
Response
{
    "active_organization_id": "rbr...rMi",
    "organizations": [
        {
            "organization_id": "rbr...rMi",
            "organization_name": "ascenue",
            "organization_slug": "ascenue",
            "role": "owner",
            "joined_at": "2025-12-10T14:34:34.617000+00:00",
            "is_active": true
        },
        {
            "organization_id": "C5o...9Ra",
            "organization_name": "ELAN Languages",
            "organization_slug": "elan-languages",
            "role": "member",
            "joined_at": "2025-12-10T15:30:26.949000+00:00",
            "is_active": false
        }
    ]
}