Outbound

Get an Outbound mutation status

For requests that included an idempotencyKey, use the Outbound-Operation-Id response header or the ID in an operation conflict. Unkeyed requests do not create operation receipts. Operations are scoped to the workspace and initiating admin. Completed/failed records remain for at least 7 days. Unknown outcomes never automatically expire or execute again: inspect the target message and coordinate recovery before a new mutation key. This endpoint does not return recipient data.

GET

/v2/outbound/operations/{operationId}

curl --request GET \
  --url https://do.featurebase.app/v2/outbound/operations/{operationId} \
  --header 'Authorization: Bearer <token>' \
  --header 'Featurebase-Version: 2026-09-03.pulsar'

{
  "createdAt": "<string>",
  "error": {
    "code": "<string>",
    "message": "<string>"
  },
  "expiresAt": "<string>",
  "id": "<string>",
  "messageId": "<string>",
  "object": "outbound_operation",
  "operation": "<string>",
  "status": "pending"
}

Authorizations

Authorizationstringheaderrequired

API key as Bearer token. Use: Authorization: Bearer sk_...

Path Parameters

operationIdstringrequired

Pattern: ^[a-f0-9]{64}$

Headers

Featurebase-Versionenum<string>header

API version for this request. Defaults to your organization's configured API version if not specified.

Available options: 2026-09-03.pulsar, 2026-08-19.orbit, 2026-01-01.nova, 2025-12-12.clover

Example: 2026-09-03.pulsar

Response

Success

createdAtstringrequired

errorobject | nullrequired

Show child attributes

expiresAtstring | nullrequired

idstringrequired

messageIdstringrequired

objectenum<string>required

Available options: outbound_operation

operationstringrequired

statusenum<string>required

Available options: pending, completed, failed, unknown

Still need help? Ask the team