Skip to main content
Request and manage individual calls with retry strategies.
Base path: /call-requests

Types


Request an ad-hoc call

Immediate execution:
Response:
With fixed-delay retry:
Response:
Scheduled start:
Response:
Scheduled retry dates:
Response:
Error Responses:

Cancel a queued call

Notes:
  • No-op if call is already executing or completed
  • Only cancels calls in waiting or delayed state

Notes

  • organizationId is automatically injected from the authenticated user’s organization
  • Phone number is fetched from contact.primaryPhone. Caller ID is resolved from the DID UUID via GET /dids/available
  • jobId is a UUID that can be used to query reports via /call-report/:jobId
  • Priority is fixed at 3 for ad-hoc calls (configurable for program calls)
  • Program calls vs ad-hoc calls: This API is for ad-hoc (manual) calls. Program calls are initiated by the Program Orchestrator internally with retry: { type: 'none' } - the orchestrator manages retries externally via execution_contacts table to respect capacity limits and pause windows.