Authentication
API keys, base URLs, and authentication headers.
Base URLs and headers
Rilla API keys can be used with both API families. The base URL and header format depend on which API you call.
Data Export API
- Base URL
customer.rillavoice.com- Authentication header
Authorization: YOUR_API_KEY
Custom CRM API
- Base URL
api.apirilla.com- Authentication header
x-api-key: YOUR_API_KEY
Authentication headers
POST /export/conversations HTTP/1.1
Host: customer.rillavoice.com
Authorization: YOUR_API_KEY
Content-Type: application/jsonAccess scope
A key belongs to a Rilla organization. Data Export access may be restricted to selected teams and their subteams. Filters narrow what you request; they do not grant additional access.
Confirm your intended scope with your account manager. Don’t assume an export key’s team restriction describes the CRM ingestion API’s authorization behavior.
Troubleshooting
| Response | What to check |
|---|---|
401 · Data Export | Confirm the Authorization header contains the raw key, with no Bearer prefix or extra whitespace. |
403 · Custom CRM | Confirm the x-api-key header is present and your key is valid. |
422 · Custom CRM | A gateway-recognized key may not be mapped to a Rilla organization. Check the response body and contact support. |