Risk Cloud API: Webhook Delivery Replay

​

Replay a Webhook Delivery endpoint

POST /api/v1/jobs/webhook-history/{job-execution-operation-id}/replay

​

Requirements

• Build permission. Your user must have the Build or Admin - All entitlement. Requests without it are rejected with 403.
• Entitlement to the triggering Application. Same rule as the Webhook Delivery Attempts endpoint: with Build permission only, you can replay a job execution when the job runs on a fixed schedule, its triggering Workflow has no permissions restrictions, or you’re entitled to that Application. A job execution ID you’re not entitled to responds the same as one that doesn’t exist. See Errors.
• A saved request payload on the attempt. Only attempts recorded after Webhook Observability was enabled have a saved payload. An attempt from before the feature was turned on can’t be replayed.

​

Path parameter

​

What happens on replay

• The most recent delivery attempt for the given execution is looked up, and its exact original payload is resent to the webhook’s current URL, not the URL that was in effect at the time of the original attempt.
• A new attempt is recorded with attemptType: REPLAY. It does not overwrite or modify the attempt it replayed.
• Exactly one delivery is attempted. A failed replay is not retried automatically.
• If the resend succeeds, the webhook’s status changes from FAILING to ACTIVE (if it was FAILING).

​

Response

{
  "jeoId": "FJr4xLId",
  "jeoStatus": "FAILED",
  "webhookName": "test",
  "webhookUrl": "https://testing.com",
  "webhookId": "123",
  "jobId": "234",
  "jobName": "webhook job",
  "recordId": "456",
  "recordName": "record 54",
  "recordExists": true,
  "webhookExists": true,
  "jobExecutionId": "678",
  "lastWebhookDeliveryAttempt": {
    "status": "FAILED",
    "attemptType": "REPLAY",
    "responseBody": "{\"error\":\"bad request\"}",
    "httpStatusCode": 400,
    "fireDate": "2026-08-14T13:05:22.000+00:00"
  }
}

​

Errors