The Vocatech REST API gives you programmatic access to calls, messages, users, and contacts. The same key works for every endpoint. One base URL. One token. One set of docs.
If you have used any modern REST API, this one will feel familiar. JSON in, JSON out. Bearer token in the header. HTTPS only.
Base URL
Every call goes to https://api.vocatech.com/v1. The version is part of the path, so a future v2 will never break what you already built.
Full reference lives at api.vocatech.com/docs. A longer written guide with examples lives at api.vocatech.com/guide.
Getting a token
Tokens are generated inside the admin portal. Sign in, open the integrations area, and create a new API key. You will see it exactly once. Copy it and store it in whatever secrets manager your team uses.
One key works for calls, messaging, users, contacts, and webhooks. There is no separate key per endpoint and no separate key per product.
If you lose a key, revoke it in the portal and create a new one. Old keys stop working the moment you revoke them.
Authentication
Every request needs an Authorization header with your bearer token.
A curl example looks like this:
curl -H "Authorization: Bearer YOUR_TOKEN" https://api.vocatech.com/v1/calls
Missing or invalid tokens return a 401. Expired tokens return a 401 with a specific code so you know to refresh. Tokens do not expire on a fixed schedule, but revoked tokens stop working immediately.
The endpoints
Seven endpoint families cover almost everything you will want to build.
- Calls. Search call history with filters for date, direction, user, and more. Returns metadata, AI summaries, sentiment, and transcripts when available.
- Messages. Send outbound SMS and WhatsApp. Search inbound and outbound message history.
- Media. Fetch MMS and WhatsApp attachments by ID.
- Users. List users, create users, and update user settings.
- Contacts. Full CRUD for the contact database that powers Callpop lookups.
- Webhooks. Create, update, and delete webhook subscriptions.
- Settings. Read company-level configuration.
Rate limits
Default limit is 60 requests per minute per token. The Reports endpoints (the heavier call-search queries) are capped at 30 per minute. Outbound messaging is capped at 5 messages per 10 minutes to prevent accidental blasts.
Hitting a limit returns a 429. Back off, retry, and you will be fine. If you have a real need for higher limits, contact support.
Data access limits
The API returns call metadata, AI summaries, full transcriptions, and sentiment scores. Everything you see in the Reports portal is available by API.
The API does not return raw recording audio. Recording files stay in secure storage and are accessible through the portal only. If you need an audio file for a specific call, pull it from the portal and hand it to your system from there.
Getting help
The Swagger reference at api.vocatech.com/docs is interactive. You can paste your token in and fire real requests from the browser to see the exact response shape.
If you are stuck on a specific endpoint, call 718.395.1550. The engineers who wrote the API answer the phone.