Modules

Webhooks

Webhooks deliver signed tenant events to operator systems, custom backends, analytics pipelines, and AI-agent workflows.

Delivery model

Events are tenant-scoped and include trace metadata.
Deliveries are signed for verification.
Retries are handled through queued delivery attempts.
Failures are visible in the console event and webhook surfaces.

Register an endpoint

Create webhook endpoints from Console, MCP, or the API. A null event list receives all tenant events; otherwise the endpoint receives only matching event types.

curl https://api.rtie.ai/v1/webhooks \
  -H "Authorization: Bearer rtie_live_..." \
  -H "Content-Type: application/json" \
  -d '{
    "url": "https://example.com/rtie/webhooks",
    "secret": "minimum-16-character-secret",
    "eventTypes": ["room.created", "auction.started"]
  }'

Webhook request

RTIE sends a POST request with the event body and verification headers.

{
  "id": "delivery_...",
  "type": "auction.started",
  "created_at": "2026-05-13T20:00:00.000Z",
  "data": {
    "auctionId": "auction_...",
    "roomId": "room_..."
  }
}

Header	Value
`X-RTIE-Signature`	`sha256=...` HMAC-SHA256 of the exact JSON request body using the endpoint secret.
`X-RTIE-Event`	The event type, such as `auction.started`.
`X-RTIE-Delivery`	The delivery ID used for dedupe and support lookup.

Retries and timeouts

RTIE treats any 2xx response as delivered.
Each attempt times out after 10 seconds.
Failed deliveries retry on a queued schedule after roughly 1 second, 5 seconds, 30 seconds, 5 minutes, and 30 minutes.
After the final failed attempt, the delivery is marked dead_lettered.