Authorization

CallRail
Prerequisites
To connect Nexla to your CallRail account, you will need a CallRail API v3 key. CallRail uses token-based API key authentication: the key is sent in the Authorization HTTP request header using the format Token token="YOUR_API_KEY". Every request Nexla makes to the CallRail API on your behalf will include this header automatically once you save your credential.
Generate a CallRail API Key
API keys are created and managed from within the CallRail application. You must have an active CallRail account to complete these steps.
-
Log in to your CallRail account at app.callrail.com.
-
Open the Integrations Library by clicking Integrations in the left navigation panel, or navigate directly to Settings > Data Access > API Keys from the left sidebar.
-
Click Create New API v3 Key to generate a new API key.
-
Copy the generated API key immediately and store it in a secure location such as a password manager. CallRail displays the key only once — it cannot be retrieved after you leave the page.
Your CallRail API key grants read and write access to your CallRail account data, including call recordings, tracking numbers, and company settings. Treat it with the same level of security as a password. If you believe a key has been compromised, delete it from the API Keys section in CallRail and generate a new one, then update your Nexla credential accordingly.
CallRail API keys are user-specific — each user can only view and manage their own keys, even at the Admin level. API keys do not expire automatically; the only way to invalidate a key is to delete it from the CallRail API Keys settings page. For complete information about the CallRail API and authentication, refer to the CallRail API v3 documentation.
Create a CallRail Credential
- To create a new CallRail credential, after selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.
Credential Name & Description
-
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.
CallRail API Key Authentication
The CallRail API authenticates all requests using a token-based API key scheme. Nexla will automatically include the key in the Authorization: Token token="..." header of every request sent to https://api.callrail.com/v3/ on your behalf.
- Enter your CallRail API key in the API Key field. This is the key generated in the steps above under Generate a CallRail API Key.
Save the Credential
-
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.
-
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.