Agents
Read and update hours, services, menus, policies, and allowed voices.
agents:readagents:writeA stable API for connecting calls, appointments, agents, knowledge, and deliveries to the software already running your business.
/v1/whoami{
"authenticated_as": "api_key",
"livemode": false,
"key_prefix": "vx_test_••••••••",
"scopes": ["calls:read"]
}Every public route starts from this origin.
https://api.vexiumvoice.app/v1Create a key in the dashboard, store it as an environment variable, and verify its identity before building the rest of your integration.
Choose test or production and grant only the permissions your system needs. The full secret is shown once.
Set VEXIUM_API_KEY in your server's secret manager. Never send it from the browser.
GET /whoami confirms the account, mode, and permissions without returning the secret.
curl "https://api.vexiumvoice.app/v1/whoami" \
-H "Authorization: Bearer $VEXIUM_API_KEY"{
"authenticated_as": "api_key",
"livemode": false,
"tenant": { "id": "…", "slug": "your-business" },
"key_prefix": "vx_test_••••••••",
"scopes": ["calls:read"]
}Read and write permissions are granted per resource. Separate integrations and revoke one without interrupting the others.
Read and update hours, services, menus, policies, and allowed voices.
agents:readagents:writeRead call history, transcripts, outcomes, and analytics.
calls:readRead captures and manage confirmations, cancellations, or no-shows.
captures:readcaptures:writeList, upload, and remove documents; test what your agent would answer.
knowledge:readknowledge:writeConfigure webhooks, test connections, and retry failed deliveries.
connections:readconnections:writeRead calls, minutes, and current-period limits.
usage:readThe credential determines the mode: use vx_test_ for testing and vx_live_ for production. Test keys cannot modify data without an isolated test environment.
Paste this prompt into Claude Code. It points to the current contract, explains authentication, and sets the security boundaries it must preserve.
The prompt never includes your key. Configure VEXIUM_API_KEY separately in your local environment or secret manager.
Integrate the Vexium Voice API into this project.
Before writing code, read:
- https://api.vexiumvoice.app/v1/llms.txt
- https://api.vexiumvoice.app/v1/openapi.json
Use https://api.vexiumvoice.app/v1 as the base URL. Read the API key only from the VEXIUM_API_KEY environment variable and send it as "Authorization: Bearer <key>". Never hardcode, log, persist, or expose the key in client-side code. Start by calling GET /whoami to verify the account, test/live mode, and granted scopes. Request only the scopes this integration needs, handle structured API errors and rate-limit headers, and show me the proposed changes before modifying files.Vexium shows the secret when a key is created or rotated and cannot display it again. Rotate it if it is lost.
Create one key per integration, restrict its scopes, and stay in test mode until you are ready for live data.
Rotate with a grace period, update your system, and immediately revoke any exposed key.
Never paste keys into tickets, chats, repositories, prompts, or frontend code. Do not record them in logs or analytics tools.