GEgetsales
messages

Send failed messages again

Send a failed message again: the same row goes back to queued. gtm-api is asked first: a send that went out after all reads delivered or sent instead; one in flight, in doubt or settling is 409 conflict (context.retry_after) on one sid, left failed by the filter arm. Other states are 409 message_not_retryable; a withdrawn AI SDR row is 409 message_superseded; a sender down 409 sender_unavailable.

Contract:

  • MCP tool retry_messages, registry package mcp.unibox/messages, mount unibox.inbox.
  • Operation action, response envelope action.
  • Flags: mass action: this verb's own request accepts a filter or targets[] set, which the owning service drains.
post/api/messages/retry

Request

  • Base URL
    https://beta.getsales.io/unibox/v1
  • Auth
    HTTP bearer and API key in header Team-SID

Request body

sidstring nullable

One failed send to send again (one of sid | filter, else 422). Fix failure_reason first: browser_unreachable (start the sender's browser from its LinkedIn card), delay_not_elapsed (wait minutes), gtm_connection_revoked (relink in Settings).

resend_unverifiedboolean nullable

Send again although gtm-api cannot tell whether the earlier attempt went out (an email taken unconfirmed, a lost LinkedIn answer). One sid only (422 with a filter), and only after a person confirmed it never arrived: a second send may reach them twice.

Response

action success envelope.

successtrue required
operation'action' required
actionstring required

kebab-case verb; matches the route segment.

Changes

No recorded changes to this operation across all 1 revision of this API.