Manage Outbounds
Use these endpoints when you need to inspect or control outbound verification attempts after an order has already been created. All six routes are scoped to a search within an order.Pause and resume operations require the search to be
IN_PROGRESS. You can list outbounds for a search in any status.Shared Path Parameters
Verification order ID (UUID).
Search ID (UUID) within the order.
Get Outbounds
Returns current actionable outbound work for the search.Returns current actionable outbounds only (those in
SCHEDULED, PENDING, or PAUSED status). Sent, delivered, failed, and
cancelled records are excluded. Use the returned id as the outboundId when pausing or resuming a single outbound.Example Request
Response
Current actionable outbound activities and contact attempts for the search.
Outbound Item Fields
Outbound identifier. Activity records use their UUID. Contact attempts without a matching activity use
attempt-<contactAttemptUuid>.Contact associated with the outbound, when available.
Contact name associated with the outbound, when available.
Entity being contacted.
Outbound channel, such as
EMAIL, FAX, VOICE, or a system method.Destination for the outbound, such as an email address or fax number.
Human-readable activity description.
Additional status, scheduling, cancellation, or system metadata.
Activity or attempt creation timestamp.
Scheduled outbound time when the outbound is pending, scheduled, or paused.
Send timestamp when the outbound has been sent.
Current actionable status:
SCHEDULED, PENDING, or PAUSED.Attempt number when available.
Attempt sequence across all outbound attempts for the search.
Attempt sequence for this contact.
Attempt sequence for this channel.
Whether this outbound is cancelled.
Cancellation reason when available.
Failure reason when available.
Example Response
Cancel Outbounds
Permanently cancels pending outbound work without cancelling the search itself.Request Body
Optional contact destination. When provided, only pending outbound matching this normalized destination is cancelled.
Example Request
Behavior
Cancels all pending outbound work — scheduled contact attempts and matching unsent outbound records. WhencontactDestination is provided, cancellation is scoped to pending outbound matching that normalized destination.
Cancellation is permanent. Resume operations do not recreate cancelled outbound. Cancelling while paused clears pause state and
marks paused attempts as
CANCELLED.Pause Outbounds
Pauses all pending outbound work for the search.Request Body
Optional pause reason stored in outbound control metadata and webhook payloads.
Example Request
Behavior
pause-outbounds affects pending outbound work only. It pauses:
SCHEDULEDcontact attemptsTRIGGERED_BY_SCHEDULERcontact attempts that have been claimed but not completed- pending delayed or queued outbound jobs
- matching unsent outbound activity records, when a corresponding activity can be identified
pause-outbounds again while
the search is already paused is idempotent and returns a successful response with previousOutboundStatus set to PAUSED.
Repeating a pause when the search is already paused succeeds without changing state or emitting another webhook.
Pause Outbound
Pauses one pending outbound while leaving the search-level outbound control statusACTIVE.
Request Body
Outbound activity ID, contact attempt ID, or
attempt- prefixed contact attempt ID. Use GET .../outbounds to discover this
value.Optional pause reason stored in outbound control metadata and webhook payloads.
Example Request
Behavior
pause-outbound affects only the matching pending outbound. The search-level outbound control status remains ACTIVE, so other
pending outbound attempts for the same search can continue.
The endpoint accepts an activity UUID, a contact attempt UUID, or attempt-<contactAttemptUuid>. Already sent, delivered, failed,
cancelled, or superseded history is not changed.
Resume Outbounds
Restores paused outbound work to an active scheduled state.Request Body
Optional resume reason stored in outbound control metadata and webhook payloads.
Example Request
Behavior
resume-outbounds restores paused outbound work to an active scheduled state. It resumes:
- attempts paused by
pause-outbounds - attempts paused individually via the single-outbound endpoint
- delayed outbound jobs captured in the pause snapshot
- matching activity metadata, with the pause marker removed and a resume marker added
resume-outbounds when there is no paused outbound state is idempotent and returns a successful response with
previousOutboundStatus set to ACTIVE.
Repeating a resume when no paused state exists succeeds without changing state or emitting another webhook. Permanently
cancelled and superseded attempts are never recreated.
Resume Outbound
Restores one paused outbound identified byoutboundId.
Request Body
Outbound activity ID, contact attempt ID, or
attempt- prefixed contact attempt ID. Use GET .../outbounds to discover this
value.Optional resume reason stored in outbound control metadata and webhook payloads.
Example Request
Behavior
resume-outbound restores only the paused outbound tracked for the supplied outboundId. If the original scheduled time is
already in the past, the attempt is restored with an immediate scheduled time so the scheduler can process it on the next run.
Calling resume-outbound when the supplied outbound is not paused is idempotent and returns a successful response with
previousOutboundStatus set to ACTIVE.
Repeating this request for an outbound that is already active succeeds without changing state or emitting another webhook.
Mutation Response
Whether the request was processed.
Internal search UUID.
External search identifier when present.
Single-outbound response only. The outbound identifier supplied in the request.
PAUSE_OUTBOUND or RESUME_OUTBOUND.Previous outbound control status:
ACTIVE or PAUSED.Current outbound control status:
ACTIVE or PAUSED. For single-outbound pauses, this remains ACTIVE because the search is
not globally paused.Cancel response only. Number of pending outbound jobs plus contact attempts cancelled.
Cancel response only. Number of outbound activity records marked as cancelled.
Pause response only. Number of queue jobs plus contact attempts paused.
Pause response only. Number of outbound activity records marked as paused.
Resume response only. Number of queue jobs plus contact attempts restored.
Resume response only. Number of outbound activity records marked as resumed.
Search-level pause/resume response. Outbound attempts paused or resumed by this request. Each item includes
id, method,
contactId, attemptDate, and destination.Human-readable summary of the action taken.
Search-Level Pause/Resume Response Shape
Webhook Behavior
Only successful pause and resume operations that change outbound state emit a
verification.notification webhook. Listing or
cancelling outbounds does not emit an outbound-control notification, and idempotent pause or resume requests do not emit a
duplicate event.
The webhook includes an
outboundControl object with:
action:PAUSE_OUTBOUNDorRESUME_OUTBOUNDoutboundId: the requested outbound ID for single-outbound operationsreason: the optional reason supplied in the requestcount: number of outbound items paused or resumedactivitiesMarked: number of activity records marked as paused or resumedtrigger:apioutbounds: affected outbound summaries for search-level operations
GET .../outbounds and cancel-outbounds do not emit outbound-control webhook notifications. See
Webhook Events for the complete payload definition.
Additional Behavior
contactDestinationscoping is supported for cancel operations. Pause and resume always apply to all pending outbound (or a single outbound when using the single-outbound endpoints).- If a replacement outbound supersedes a paused outbound, the old attempt is marked as superseded and is not recreated on resume.
- Use Manage Search Contacts to inspect or update the contact plan.

