Skip to content
EN
Open app

API Keys

4 min read
Copy as Markdown
View as MarkdownOpen the raw .md file.md

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.

  1. Open API Keys and start a new key

    On the API Keys tab, click + Api Key.

    API Keys tab with + Api Key button
    api-keys-0Expand
  2. 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, or Initiate 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.0 as a stand-in for “any IP”; blank already means any IP.
    Create API key drawer with CRM Integration name
    api-keys-1Expand
  3. Choose the allowed operations

    Under API operation restrictions, expand each group and toggle what this key may call. Groups include Calls, Agents, Workflows, VoIP & SIP, SMS, MCP, Billing, Shopify, and Campaigns. Leave everything on for full access, or switch off what the key does not need.

    API operation restriction groups
    api-keys-2Expand
  4. 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.

    Copy your API key dialog
    api-keys-3Expand

The table lists each key’s Name, masked Key, Last Used, and Created date. Use search to find a key by name.

API keys table with CRM Integration
api-keys-4Expand
  • 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.

Authenticate requests by sending the key in the x-api-key header:

x-api-key: YOUR_API_KEY

For example, starting an outbound AI call:

Terminal window
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.

My requests return 401 Unauthorized
  • Confirm the key is sent in the x-api-key header - not as a Bearer token.
  • Check the key has not been revoked from the API Keys table.
  • If the key has an IP restriction, verify the request comes from that exact address.
My requests return 403 Forbidden
  • The key’s operation restrictions do not include the endpoint you are calling - edit the key and enable the relevant operation group.

If you run into any issues, the Voice Logica support team is available: