Skip to main content
GET
/
api
/
webhooks
/
{id}
Get Webhook
curl --request GET \
  --url https://app.tuco.ai/api/webhooks/{id} \
  --header 'Authorization: Bearer <token>'
{
  "id": "<string>",
  "url": "<string>",
  "events": [
    "<string>"
  ],
  "name": "<string>",
  "description": {},
  "isActive": true,
  "lastTriggeredAt": {},
  "lastSuccessAt": {},
  "lastFailureAt": {},
  "failureCount": 123,
  "createdAt": "<string>",
  "updatedAt": "<string>"
}

Documentation Index

Fetch the complete documentation index at: https://docs.tuco.ai/llms.txt

Use this file to discover all available pages before exploring further.

Returns details for a single webhook. The secret is never returned.

​
Authentication

Authorization: Bearer tuco_sk_xxxxxxxxxxxxx

​
Path parameters

​
id
string
required
Webhook ID (returned when you created the webhook).

​
Response

​
id
string
Webhook ID
​
url
string
Endpoint URL
​
events
string[]
Subscribed event types
​
name
string
Webhook name
​
description
string | null
Optional description
​
isActive
boolean
Whether the webhook is active
​
lastTriggeredAt
string | null
Last event sent (ISO UTC)
​
lastSuccessAt
string | null
Last successful delivery (ISO UTC)
​
lastFailureAt
string | null
Last failed delivery (ISO UTC)
​
failureCount
number
Consecutive failure count
​
createdAt
string
Creation timestamp
​
updatedAt
string
Last update timestamp

​
Example

curl "https://app.tuco.ai/api/webhooks/680a1b2c3d4e5f6789012345" \
  -H "Authorization: Bearer tuco_sk_xxxxxxxxxxxxx"
200 Response
{
  "id": "680a1b2c3d4e5f6789012345",
  "url": "https://example.com/webhooks/tuco",
  "events": ["message.sent", "message.failed", "message.reply"],
  "name": "Production webhook",
  "description": "Sends events to our CRM",
  "isActive": true,
  "lastTriggeredAt": "2026-04-12T10:30:00.000Z",
  "lastSuccessAt": "2026-04-12T10:30:00.000Z",
  "lastFailureAt": null,
  "failureCount": 0,
  "createdAt": "2026-03-01T00:00:00.000Z",
  "updatedAt": "2026-04-12T10:30:00.000Z"
}
Use lastSuccessAt, lastFailureAt, and failureCount to monitor your endpoint’s health. If failureCount is climbing, your endpoint might be down.