Skip to main content
POST
Send failed messages again

Authorizations

Authorization
string
header
required

Access token issued by gs.service.id. Its access_identity claim carries team_sid, actor_sid and actor_type, and that team scope is authoritative.

Team-SID
string
header
required

Team scope for tokens that do not carry one. Ignored when the token already names a team.

Body

application/json

Request body of retry_messages.

sid
string | null

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).

Required string length: 18
Pattern: ^ub_ms_
filter
object | null

Fan-out arm: send every matching failed row again (the backend ANDs state=failed in), so { conversation_sid: { eq } } retries one thread and {} every failed send of the workspace once its senders are back.

resend_unverified
boolean | null

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.

success
enum<boolean>
required
Available options:
true
operation
enum<string>
required
Available options:
action
action
string
required

kebab-case verb; matches the route segment.

item
object | null
required
result
object
required
meta
object
required