Replay an event to a webhook destination

POST /v1/developer/events/{eventId}/replay

Operation ID: replayDeveloperEvent

Queues a retained event for an enabled, same-installation destination subscribed to its type. Requires events.read, webhooks.read, webhooks.write and the event-family grant. The event ID and body stay unchanged; dispatch uses a fresh signature timestamp. queued=false means an attempt is already sending. Repeated queued requests coalesce; receivers must deduplicate by event ID. Server credentials only. Application, installation, collection, and TEST/LIVE scope are resolved from the credential. Legacy collection webhook destinations are separate. TEST and LIVE events are isolated; neither event grants charging, booking or marketing authority.

Contract status

Field	Value
Maturity	`beta`
Required capability	`webhooks.write`
Freshness class	`authenticated-state`
Quota cost	`1`

All operations require a Kismet Developer Bearer credential. Collection and resource authority is resolved from the credential’s installation grants; identifiers in the URL never grant access.

Request parameters

Name	In	Type	Required	Description
`eventId`	path	string	yes

Request body

The request body is JSON. The canonical schema is:

{
  "type": "object",
  "additionalProperties": false,
  "required": [
    "subscriptionId"
  ],
  "properties": {
    "subscriptionId": {
      "type": "string",
      "format": "uuid"
    }
  }
}

Minimal example:

{
  "subscriptionId": "string"
}

cURL

Set KISMET_API_ORIGIN=https://api.ksmt.app and configure KISMET_DEVELOPER_API_KEY in your environment. Run server-credential requests from your backend, not browser code.

curl --request POST \
  "$KISMET_API_ORIGIN/v1/developer/events/{eventId}/replay" \
  --header "Authorization: Bearer $KISMET_DEVELOPER_API_KEY" \
  --header "Accept: application/json" \
  --header "Content-Type: application/json" \
  --data '{"subscriptionId":"string"}'

Responses

Status	Meaning
202	Accepted for processing. See the response body for the current state.
400	Invalid request parameters or body.
401	Missing, invalid, expired, or inappropriate credential/session.
403	Credential lacks the required grant/capability, or an origin/CSRF check failed.
404	The authorized resource was not found.
409	Request conflicts with the installation environment or current state.
429	Rate limit or quota exceeded; inspect response metadata before retrying.
503	A required Kismet dependency is temporarily unavailable.

202 response example

{
  "deliveryId": "88888888-8888-4888-8888-888888888888",
  "queued": true
}

202 response schema

Content type: application/json. Required fields, nullable values, and nested structures are defined below.

View complete response schema

{
  "type": "object",
  "properties": {
    "deliveryId": {
      "type": "string",
      "format": "uuid"
    },
    "queued": {
      "type": "boolean"
    }
  },
  "required": [
    "deliveryId",
    "queued"
  ],
  "additionalProperties": false
}