Skip to main content
GET
/
user-webhooks
List webhooks
curl --request GET \
  --url https://api.dialnexa.com/v1/user-webhooks \
  --header 'Authorization: Bearer <token>'
{
  "data": [
    {
      "id": "wh_abc123",
      "url": "https://yourapp.com/webhooks/dialnexa",
      "events": [
        "call.completed",
        "call.failed"
      ],
      "is_active": true,
      "created_at": "2024-03-01T10:00:00.000Z"
    }
  ]
}
Returns every webhook subscription registered on your workspace, paginated. Each entry includes the webhook’s id, delivery url, the list of subscribed events, the active/inactive flag, and the creation timestamp. Signing secret values are never returned, they are shown only once when the webhook is created. Use this endpoint to audit which destinations DialNexa is currently delivering events to, identify endpoints that should be retired, or confirm a webhook exists before triggering a test event.

When to use this

  • Webhook audits: render a table of every webhook with its destination, subscribed events, and active status.
  • Decommissioning checks: find webhooks pointing at retired URLs before they accumulate failed deliveries.
  • Migration tooling: enumerate webhooks before re-registering them under a new event taxonomy.
  • Operational dashboards: combine with Webhook retries and failures to surface unhealthy subscriptions.

Query parameters

ParameterDescription
pagePage number, starting from 1.
limitResults per page (max 100, default 20).
is_activeFilter by active or inactive subscriptions.

Errors

  • 403 Forbidden is returned when the API key cannot read webhook configuration on this workspace.

Request

curl "https://api.dialnexa.com/v1/user-webhooks" \
  -H "Authorization: Bearer YOUR_API_KEY"

Response

{
  "data": [
    {
      "id": "whk_c9v3nz8rq4pm",
      "url": "https://yourapp.com/webhooks/dialnexa",
      "events": ["call.completed", "call.failed"],
      "is_active": true,
      "created_at": "2024-04-01T08:00:00.000Z"
    }
  ],
  "meta": { "page": 1, "limit": 20, "total": 1 }
}

Authorizations

Authorization
string
header
required

Pass your API key as a Bearer token in the Authorization header.

Response

200 - application/json

Success.

data
object[]