Skip to main content
POST
Automations resume
Requires the messaging rollout flag and explicit personal-key permissions. Live publishing and lifecycle changes require an expiring preparation and idempotent execution.

Authorizations

Authorization
string
header
required

Integration key for backend workloads, or a scoped personal key (sr_user_) for account discovery and supported project operations. MCP accepts only personal keys.

Headers

X-Sendrealm-Project-Id
string<uuid>
required

Explicit authorized project. Its team is derived server-side.

Path Parameters

id
string<uuid>
required

Body

application/json
prepared_action_id
string<uuid>
required
idempotency_key
string
required
Required string length: 1 - 160

Response

200 - application/json

Successful operation

status
integer
required
data
object
required