For the complete documentation index, see llms.txt. This page is also available as Markdown.

Webhooks API

Manage webhook subscriptions programmatically.

Method
Path
Scope

GET

/webhooks

webhooks:read

GET

/webhooks/{id}

webhooks:read

POST

/webhooks

webhooks:write

PATCH

/webhooks/{id}

webhooks:write

DELETE

/webhooks/{id}

webhooks:write

This manages subscriptions. For what the deliveries contain and how to handle them, see Webhook events.

Create a subscription

curl -X POST https://app.limecall.com/api/v1/webhooks \
  -H "Authorization: Bearer sk_live_..." \
  -H "Content-Type: application/json" \
  -d '{
    "url": "https://example.com/hooks/limecall",
    "events": ["call.completed", "message.received"],
    "description": "Production CRM sync",
    "maxRetries": 5
  }'
Field
Rules

url

Must be a valid URL.

events

Array, at least one entry.

description

Optional, for your own bookkeeping.

maxRetries

Integer 0–10. Defaults to 3.

Returns 201 with the created subscription.

Update

url, events, description, isActive and maxRetries can all be changed. Setting isActive: false pauses deliveries without losing the subscription or its secret β€” the right move during a deploy, rather than deleting and recreating.

Delete

Permanent, and the secret goes with it.

Choosing maxRetries

Retries cover a brief outage on your side. They do not fix an endpoint that returns an error for a payload it cannot handle β€” that will exhaust its retries and be dropped.

Return 2xx as soon as you have accepted the payload and process asynchronously, so a slow database does not turn into a retry storm.

Was this helpful?