The Retrigger webhook failure endpoint manually re triggers delivery of a webhook event that failed.

Requirements: Base URL, Authentication, Error codes

Scope: tasks.webhooks.manage

What this does

When you send a Retrigger webhook failure request with a webhook failure ID,

Endpoint

POST /api/v4/tasks/webhook_failures/{webhook_failure_id}/retrigger

Path parameters

• webhook_failure_id
  The unique identifier of the webhook failure.

Request body

This endpoint does not require a request body.

Related endpoints

• List failures: List webhook failures
• Get failure details: Get webhook failure
• Get webhook details: Get webhook

Example request

curl -X POST "https://{cluster_id}.voiso.com/api/v4/tasks/webhook_failures/aabbccddeeff001122334455/retrigger" \
  -H "Authorization: Bearer <contact_center_api_key>" \
  -H "Content-Type: application/json"

Response

If successful, the API returns a webhook_failure object.

{
  "webhook_failure": {
    "id": "aabbccddeeff001122334455",
    "event": "call.ended",
    "status": "pending",
    "reason": null,
    "webhook": {
      "id": "0b97ce11-b6e0-49b4-8f92-68040aa324bf",
      "name": "CRM call events"
    },
    "last_attempt_at": "2026-03-15T10:45:00Z",
    "created_at": "2026-03-15T10:00:00Z",
    "updated_at": "2026-03-15T10:45:00Z"
  }
}

Notes

• Use this endpoint after you have corrected the underlying delivery issue (for example, a URL or authentication issue).
• If the webhook continues to fail, it will appear again in List webhook failures.

Troubleshooting

401 Unauthorized

Returned if the API key is missing or invalid.

403 Forbidden

Returned if the API key does not have access to Tasks resources.

404 Not found

Returned if the webhook failure ID does not exist or is not accessible.

409 Conflict

Returned if the failure cannot be re triggered in its current state.

429 Too many requests

Returned if requests are rate limited.