For AI assistants: this page as plain markdown is at https://docs.voicelogica.ai/raw/getting-started/api-keys.md, and https://docs.voicelogica.ai/llms.txt lists the docs by topic, one file each, small enough to read whole. Read those rather than this HTML page.
API Keys
API keys are optional. Finish sign-up, subscription, and your first agent before you need them.
They are programmatic credentials for the Voice Logica API. Each key is scoped to the operations you allow and can be limited to one IP address. The same key also signs MCP clients (ChatGPT, Claude) into your workspace.
Open Team and access from the Account group in the sidebar, then select the API Keys tab. That page also has Members, Pending invitations, and Access Requests.
Creating an API Key
Section titled “Creating an API Key”-
Open API Keys and start a new key
On the API Keys tab, click + Api Key.

api-keys-0 -
Choose a preset, name the key, and set an IP if needed
The Create API key drawer opens on the right.
- Preset - start from Full access (every operation) or another preset, then refine below.
- API Key Name - use a clear purpose name such as
CRM Integration,Webhook Handler, orInitiate Call. - IP Address - optional. Leave it blank to allow any IP. Only enter a real address when the caller has a fixed IP. Do not enter
0.0.0.0as a stand-in for “any IP”; blank already means any IP.

api-keys-1 -
Choose the allowed operations
Under API operation restrictions, expand each group and toggle what this key may call. The groups are Calls, Agents, Workflows, VoIP & SIP, SMS, MCP, Billing, Shopify, Campaigns, Company, Tickets, Reports, Knowledge, Integrations, and Contacts (which groups appear depends on your role - support-desk and reporting groups only show when your account has them). Leave everything on for full access, or switch off what the key does not need.

api-keys-2 -
Create the key and copy it once
Click Create API Key. The Copy your API key dialog shows the full value only this once. Click Copy, store the key somewhere safe, then click Done.

api-keys-3
Managing Your Keys
Section titled “Managing Your Keys”The table lists each key’s Name, masked Key, Last Used, and Created date. Use search to find a key by name.

- Edit (pencil) - change the name, IP restriction, and allowed operations. The secret value itself never appears again and cannot be rotated in place.
- Revoke (trash) - opens Revoke API key? Confirm with Revoke to permanently remove the key. Apps using it lose access immediately. There is no separate Delete action.
Using Your API Key
Section titled “Using Your API Key”Authenticate requests by sending the key in the x-api-key header:
x-api-key: YOUR_API_KEYFor example, starting an outbound AI call:
curl -X POST https://api.voicelogica.ai/api/v1/phones/calls/initiate-call \ -H "x-api-key: YOUR_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "destinationNumber": "+302101234567", "agentId": "your-agent-id", "voipPhoneId": "your-voip-phone-id" }'destinationNumber is required; pass agentId for outbound AI calls, and either voipPhoneId or sipTrunkId to choose the line the call goes out on. The full interactive reference for every endpoint lives at api.voicelogica.ai/api-docs.
Troubleshooting
Section titled “Troubleshooting”Why do my Voice Logica API requests return 401 Unauthorized?
Check that the API key is sent in the x-api-key header, not as a Bearer token, and that it has not been revoked in the API Keys table. If the key has an IP restriction, the request must come from that exact address.
Why do my Voice Logica API requests return 403 Forbidden?
A 403 means the API key’s operation restrictions do not include the endpoint you are calling. Edit the key and enable the relevant operation group.
Next Steps
Section titled “Next Steps”Need Help?
Section titled “Need Help?”If you run into any issues, the Voice Logica support team is available:
