Go to production
Go-live checklist
What to confirm before the first live post, before volume, and once leads are flowing.
Work through these before Entrovox activates your campaign and you send live leads. Each item links to the page that explains it.
Before the first live post
- Run the quickstart: post an
is_testlead and read it back from itsstatus_url. - Confirm your key is bound to the right campaign. You can omit
lead_source_id; naming another campaign is403 LEAD_SOURCE_NOT_ALLOWED. See Authentication and keys. - Send your own
external_idon every lead, unique per campaign. - Send an
Idempotency-Keywith every post and reuse it on retries. See Safe retries and idempotency. - Keep the key on a server. Never ship it to a browser or a mobile app.
- Make sure the consent certification for each list is in place with your Entrovox contact. It is not collected on this API. See Compliance: what we enforce.
Before you turn volume on
- Branch on the error
code. Resell every definitive rejection, and retry only the transient codes. - For batches, read every item's
statusand persist everystatus_url. HTTP200does not mean every row landed. See Batch post. - Stay inside your rate limits, honor
Retry-After, and ask for a higher ceiling before a big send. - Count a lead once per
external_id, not once per201. - If your floor can sell a lead elsewhere, wire up pause.
Once leads are flowing
- Read outcomes from the status URL on a schedule. Webhooks are a preview and nothing is delivered yet.
- Fetch a fresh signed recording URL when you need audio. Never store the signed URL. See Recordings and transcripts.
- Quote the
X-Request-IDwhen you contact us about a request.
Next steps
Questions while you integrate: reply to the thread that included your key, or email the Entrovox contact who provisioned you.
Updated Nov 7, 2026