List webhook endpoints
Authorization
ApiKey webhooks:manageAuthorization: Bearer clk_{tenant_id}_{secret}. The header X-Api-Key carrying the same value is also accepted, for integration platforms that cannot set an Authorization header. Keys are minted in the Callens dashboard.
In: header
Scope: webhooks:manage
Response Body
application/json
application/json
application/json
application/json
curl -X GET "https://example.com/webhooks"{ "success": true, "message": "Webhook endpoints.", "data": { "items": [ { "id": "string", "url": "string", "active": true, "description": "string", "events": [ "call.completed" ], "last_delivered_at": "2019-08-24T14:15:22Z", "created_at": "2019-08-24T14:15:22Z" } ], "disclosure": "string" }}Submit a customer event POST
Records one thing that happened with a customer outside a Callens call — a message, an order, a note — from any system. One event per request. Callens recognises the customer from the identifiers in `customer` and stores the event on that customer. `event.content` is kept as descriptive text and is never parsed into fields. Sending the same `event.source` and `event.external_id` again returns the stored event and writes nothing, so the id must be the same on every retry of one event. Call this from a server you control and never from a browser or a mobile app: the response says whether an identifier already belongs to one of your customers and returns that customer's id, so a key with the `events` scope must not be readable by an anonymous client.
Register a webhook endpoint POST
Next Page