Skip to main content

Authorization

Follow this guide to create a new AssemblyAI credential that will allow Nexla to authenticate to and exchange data with your AssemblyAI account.
assemblyai_api_auth.png

AssemblyAI

Prerequisites​

AssemblyAI authenticates every REST and WebSocket call using a single secret API Key generated from your AssemblyAI dashboard. The key is sent in the Authorization header on each request (no Bearer or Basic prefix is required — the key value alone is the header value).

Generate an AssemblyAI API Key​

  1. Sign in to your AssemblyAI account at assemblyai.com/dashboard. New accounts can be created free at assemblyai.com/dashboard/signup, which includes free usage credit for evaluation.

  2. From the left navigation, select the API Keys tab. The dashboard lists any keys already provisioned for the account.

  3. Click Create new API key, enter a descriptive name that identifies the integration (for example, Nexla integration), and click Create. AssemblyAI generates the key and adds it to the list.

  4. Click Copy next to the new key and store the value securely. The full key value remains retrievable from the dashboard, but it should be treated as a secret — anyone with the key can submit transcription jobs and consume credit on the account.

    If a key is exposed or no longer needed, return to the API Keys tab and click Revoke to invalidate it. Any integration that uses the revoked key will stop working immediately, so plan a rotation before revoking a key that is in use.

For complete information about retrieving and managing API keys, see the AssemblyAI Account Management documentation.

Regional Considerations​

AssemblyAI offers an EU-hosted variant of the API at api.eu.assemblyai.com in addition to the default global host at api.assemblyai.com. The connector ships with endpoint templates that target the default global host. If your account or compliance requirements mandate the EU host, configure data sources manually using the Advanced tab and substitute api.eu.assemblyai.com for api.assemblyai.com in each endpoint URL.

Important

The AssemblyAI API key grants access to all transcription, audio intelligence, LLM Gateway, and streaming features on the account, and it bills against the account's credit balance. Store it in a secure secret manager, never commit it to source control, and rotate it immediately if you suspect it has been exposed.

Create an AssemblyAI Credential​

  • To create a new AssemblyAI credential, after selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

Credential Name & Description​

  1. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

    Resource descriptions are recommended but are not required. They should be used to provide information about the resource purpose, data freshness, etc. that can help the owner and other users efficiently understand and utilize the resource.

Authentication​

  1. Enter the AssemblyAI API key in the API Key Value field. This is the full key value copied from the API Keys tab of the AssemblyAI dashboard. Nexla stores this value as a secret and sends it as the raw Authorization header on every call to the AssemblyAI API — no Bearer or Basic prefix is added.

    AssemblyAI is unusual in that it does not prefix the API key in the Authorization header. If you copy curl examples from the AssemblyAI documentation, you'll notice the header is set as Authorization: <your-api-key>, not Authorization: Bearer <your-api-key>. Nexla applies this format automatically when using the AssemblyAI credential.

Save the Credential​

  1. Once all of the relevant steps in the above sections have been completed, click the Save button at the bottom of the overlay to save the configured credential. Nexla validates the key by issuing a test call to GET https://api.assemblyai.com/v2/transcript before saving.

  2. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation and can be selected for use with a new data source or destination.