Plan a Sendvo API workflow.Control records and retries.
Software-connected mail needs more than an endpoint call. Plan the source record, event payload, send rule, duplicate prevention, address checks, proof or approval state, campaign ID, retry behavior, mail batch, tracking join, and measurement window before software submits mail.
Last reviewed: August 26, 2026
Define the safety boundary first.
A useful integration design makes send intent, duplicate behavior, approval, and traceability explicit before production.
Keep the source record visible.
Carry the business event, stable record identifier, intended recipient, campaign context, and source timestamp into the mail workflow.
Review event payload guidance →Make repeated requests predictable.
Define an idempotency key, duplicate-send rule, retry window, and the response for an already-accepted request.
Review idempotency guidance →Separate eligibility from execution.
Document the business rule that creates send intent and the checks that can hold or reject it before mail submission.
Review send-rule guidance →Use stable campaign identifiers.
Keep the campaign ID connected to the source record, recipient set, proof state, batch, tracking events, and later response data.
Review campaign ID guidance →Define the production handoff.
Group accepted records into an auditable mail batch with clear boundaries for proof, submission, status, and exceptions.
Review batch guidance →Join tracking without overclaiming.
Connect mailstream events and response data to the campaign record while keeping delivery, attention, response, and revenue distinct.
Review measurement guidance →This is workflow guidance, not a public endpoint reference. Sendvo does not publish a complete public API authentication, endpoint, request, or response contract on this website. The authenticated workspace shows account-specific capabilities.
Build the control plan in order.
Start with the workflow overview. Then use the focused guides for records, retries, exceptions, and traceability.
Use one canonical page for each implementation question.
Start with the broad API model. Continue to the guide that owns the exact control or source event you need.
Direct mail API model
Understand records, send intent, proof state, batches, tracking joins, and measurement boundaries.
Read the canonical API overview →Implementation sequence
Plan durable records, address gates, idempotency, tests, event handling, and operating controls.
Read the implementation guide →Webhook controls
Define payload validation, duplicate handling, retry rules, pause controls, and status joins.
Read the webhook guide →Named integration recipes
Choose a verified source event and map it into a controlled direct-mail record.
Browse integration recipes →Know what this page does not promise.
Is this a public Sendvo API reference?
No. This page provides workflow guidance. Sendvo does not publish a complete public endpoint and authentication reference on this website.
What should a software-connected mail workflow control?
A software-connected mail workflow should control source records, event payloads, send rules, duplicate prevention, address readiness, proof or approval state, campaign identifiers, retry behavior, batches, tracking joins, and measurement boundaries.
Does reading this page confirm API access for my account?
No. Educational guidance does not confirm account access. The authenticated Sendvo workspace shows the capabilities and plan changes available to that account.