Replay Job Webhook V1

Re-fire the terminal webhook event for an already-finished job. Useful when the receiver was down during the original event…

POST /api/v1/jobs/{job_id}/replay-webhook

cURL

curl --request POST \
  --url 'https://api.computer.stateset.app/api/v1/jobs/{job_id}/replay-webhook' \
  --header "X-API-Key: $STATESET_COMPUTER_USE_API_KEY"

200

{
  "job_id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
  "event_type": "string",
  "registered_endpoints_dispatched": 1,
  "adhoc_url_delivered": true
}

Re-fire the terminal webhook event for an already-finished job.

Useful when the receiver was down during the original event. Only works on jobs in a terminal status (succeeded or failed) — live jobs return 409 because firing twice would confuse downstream state machines that key on job.completed.

Both registered tenant WebhookEndpoint rows and ad-hoc per-job webhook_url deliveries are re-attempted using the same payload shape as the original.

Path parameters

job_id · string (uuid) · required

Response

ReplayWebhookResponse

job_id · string · required

event_type · string · required

The terminal event re-fired (job.completed | job.failed).

registered_endpoints_dispatched · integer · required

Count of registered WebhookEndpoint rows the event was queued to.

adhoc_url_delivered · boolean,null

If the job carried a webhook_url in params, the outcome of the ad-hoc delivery attempt. None when no ad-hoc URL was set.

Status codes

Code	Meaning
200	Successful Response
422	Validation Error

cURL

curl --request POST \
  --url 'https://api.computer.stateset.app/api/v1/jobs/{job_id}/replay-webhook' \
  --header "X-API-Key: $STATESET_COMPUTER_USE_API_KEY"

200

{
  "job_id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
  "event_type": "string",
  "registered_endpoints_dispatched": 1,
  "adhoc_url_delivered": true
}