Submits one phone number for processing. Charges 1 credit and stores
the contact in queued status. Returns 403 with
error: "feature_not_enabled" until your organization has the
single_contact_api_enabled feature flag turned on — contact
[email protected] to enable Enterprise access.
Re-posting with the same idempotency_key returns the existing
contact without an additional credit charge.
Documentation Index
Fetch the complete documentation index at: https://docs.optimaldial.com/llms.txt
Use this file to discover all available pages before exploring further.
OptimalDial API key, prefixed od_live_, sent as Authorization: Bearer ....
Mint keys in the in-app developer panel; they are scoped to a single organization.
Any common format. Normalized to E.164. Must be US or Canadian.
"+15551234567"
Arbitrary extra fields echoed back in the result payload. Use these to correlate the result with your own row IDs.
Optional per-contact webhook URL. Receives a signed POST when the contact's result is ready, with the same retry semantics as registered org-level webhook endpoints (6 attempts with backoff).
HMAC-SHA256 secret used to sign the callback_url payload.
Optional. Re-posting with the same key returns the existing contact without an extra credit charge. Scoped per (organization, api_key).
255Contact created (or returned via idempotency).
E.164-normalized phone number (US/CA only).
"+15551234567"
Arbitrary extra fields echoed back from creation.
queued, processing, completed, failed, discarded x >= 0The classification — e.g. "Likely Answer", "Likely Voicemail".
Populated when status == "completed".