Retrieve a contact (legacy — no identity)
Legacy. Fully supported with no removal planned, but this response
does not include OptimalDial Identity: optimaldial_status reports the
Answer Intent value only.
Use GET /api/v2/contacts/{contact_id} for the nine-tier status and the
identity band. Existing integrations can stay here indefinitely.
Authorizations
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.
Path Parameters
Response
The contact.
E.164-normalized phone number (US/CA only).
"+15551234567"
Arbitrary extra fields echoed back from creation.
queued, processing, completed, failed, discarded x >= 0The Answer Intent classification — e.g. "Likely Answer",
"Likely Voicemail". Populated when status == "completed".
This field is frozen on v1: it keeps returning the Answer Intent
value even for contacts processed with OptimalDial Identity, so
existing filters keep working. Use /api/v2/contacts for the
nine-tier status and the identity band.
Validation pricing tier this contact was created with.
standard, max