Making calls
The Calls API is the main reason to integrate with HollrAI programmatically.
Build and deploy your agent in app.hollr.ai, then use your backend to trigger calls whenever something happens in your product: a new lead arrives, an order needs confirmation, a candidate needs screening, a customer needs a follow-up, or any other workflow that benefits from a phone conversation.
You can trigger one call at a time or send a batch of contacts.
Single call
Bulk calls
Use /v1/call/make-call to trigger one outbound call.
campaign_id and to are required. metadata is optional and accepts arbitrary JSON values you want associated with the call request.
Which endpoint should I use?
- Single event-driven call: use
make-call. - Batch of contacts: use
bulk-calls. - Repeated or scheduled workflows: keep the business logic in your application and trigger the appropriate endpoint when the call should happen.
HollrAI handles the voice conversation itself. Your application decides when to call and who to call.
Response
The call endpoints currently pass through the response returned by HollrAI’s underlying call server, so the API reference intentionally exposes the response as an open object rather than pretending it has a fixed schema.
Limits
The current API contract documents a 60 requests/minute limit per API key. make-call also has a 5 concurrent-call limit per API key; bulk-calls does not enforce that specific concurrent-call limit.
See errors and rate limits for the full details.
After triggering a call
A completed call can be read through the Conversations API. Use the conversation record when your application needs the transcript, summary, sentiment, recording information, call identifiers, or other call data.

