The Get webhook failure endpoint returns information for a single webhook delivery failure.

Requirements: Base URL, Authentication, Error codes

Scope: tasks.webhooks.read

What this does

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

Endpoint

GET /api/v4/tasks/webhook_failures/{webhook_failure_id}

Path parameters

• webhook_failure_id
  The unique identifier of the webhook failure.

Related endpoints

• List failures: List webhook failures
• Re trigger delivery: Retrigger webhook failure
• Get webhook details: Get webhook

Example request

curl -X GET "https://{cluster_id}.voiso.com/api/v4/tasks/webhook_failures/aabbccddeeff001122334455" \
  -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": "inactive",
    "reason": "Connection timeout",
    "webhook": {
      "id": "0b97ce11-b6e0-49b4-8f92-68040aa324bf",
      "name": "CRM call events"
    },
    "last_attempt_at": "2026-03-15T10:32:14Z",
    "created_at": "2026-03-15T10:00:00Z",
    "updated_at": "2026-03-15T10:32:14Z"
  }
}

Notes

• Use List webhook failures to retrieve failure IDs.
• If the failure is inactive,
  Voiso
  will not retry it automatically. Use Retrigger webhook failure after correcting the delivery issue.

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.

429 Too many requests

Returned if requests are rate limited.