Replay Webhook Events

Initiates a replay of webhooks that failed to deliver. This is particularly useful when recovering from server downtime or when you need to reprocess events with updated logic.

curl --location --request POST \
    'https://api.100ms.live/v2/analytics/webhooks/replay' \
    --header 'Authorization: Bearer <management_token>' \
    --header 'Content-Type: application/json' \
    --data-raw '{
      "start_time": "2025-12-28T00:00:00Z",
      "end_time": "2025-12-29T00:00:00Z",
      "event_names": ["peer.join.success"]
    }'

Allowed Filters

To be specified as query parameters

Response

{
  "workflow_id": "webhook-replay-customer123-a1b2c3d4",
  "status": "started",
  "message": "Webhook replay has been queued for processing",
  "filters": {
    "start_time": "2025-12-28T00:00:00Z",
    "end_time": "2025-12-29T00:00:00Z",
    "room_id": "",
    "event_types": ["peer.join.success", "peer.leave.success"]
  }
}

Status Values:

Supported Event Types

You can filter specific webhooks to replay by the following event types:

How Replay Works

Once a replay is triggered, the system:

1. Starts a workflow that fetches webhooks from the database in batches
2. Each webhook is sent to your configured webhook URL with an is_replay: true flag
3. Webhook replay events are sent at a rate of 10 events per second to your endpoint
4. Maximum 50,000 webhooks are supported per replay request
5. Duplicate replay requests with identical filters will automatically reuse the existing workflow

Pagination for Large Replays

For replays with more than 50,000 webhooks, use pagination by making multiple requests with different offsets:

# First batch (0-50,000)
curl --location --request POST \
    'https://api.100ms.live/v2/analytics/webhooks/replay' \
    --header 'Authorization: Bearer <management_token>' \
    --header 'Content-Type: application/json' \
    --data-raw '{
      "start_time": "2025-12-28T00:00:00Z",
      "limit": 50000,
      "offset": 0
    }'

# Second batch (50,000-100,000) - Run after first completes
curl --location --request POST \
    'https://api.100ms.live/v2/analytics/events/webhooks/replay' \
    --header 'Authorization: Bearer <management_token>' \
    --header 'Content-Type: application/json' \
    --data-raw '{
      "start_time": "2025-12-28T00:00:00Z",
      "limit": 50000,
      "offset": 50000
    }'

Error Responses

Why would you use this API?

• Recover from downtime: Replay failed webhooks after your server recovers from an outage or maintenance period
• Reprocess events: Replay specific event types following bug fixes, data corrections, or logic updates in your webhook handler

Check Replay Results

Monitor the status and progress of a webhook replay workflow.

curl --location --request GET \
    'https://api.100ms.live/v2/analytics/webhooks/replay/webhook-replay-customer123-a1b2c3d4' \
    --header 'Authorization: Bearer <management_token>'

Allowed Filters

To be specified as query parameters

Response

{
  "workflow_id": "webhook-replay-customer123-a1b2c3d4",
  "status": "completed",
  "started_at": "2025-12-29T10:00:00Z",
  "completed_at": "2025-12-29T10:15:00Z",
  "filters": {
    "start_time": "2025-12-28T00:00:00Z",
    "end_time": "2025-12-29T00:00:00Z",
    "room_id": "",
    "event_types": ["peer.join.success"],
    "limit": 50000,
    "offset": 0
  },
  "progress": {
    "total": 150,
    "completed": 148,
    "failed": 2
  },
  "result": {
    "total": 150,
    "completed": 148,
    "failed": 2,
    "failed_events": ["event-id-1", "event-id-2"]
  }
}

Status Values:

Why would you use this API?

• Track workflow progress: Monitor the total number of events queued for replay, completion counts, and failure rates in real-time
• Analyze failure statistics: Retrieve a detailed list of webhook events that failed to replay within the current workflow for troubleshooting

Postman collection

You can use our Postman collection to start exploring 100ms APIs.

Refer to the Postman guide to get started with 100ms API collection.