Events as they happen.
Signed webhooks for leads, meetings, requests for a person, graded conversations and test winners, retried for three days.
Integrations
Integrate with Webhooks + API
Send chat events to your own systems the moment they happen, and read conversations, contacts and meetings.
Darwin signs and sends an event to your HTTPS endpoint whenever a lead arrives, a meeting is booked or a visitor asks for a person, and retries for three days if your server is down. The REST API reads conversations, contacts, meetings and results, with keys scoped to what each tool needs.
Your data, readable.
Read conversations with transcripts, contacts, meetings and funnel results from your own code, with paginated, versioned endpoints.
Keys that see only enough.
Each key carries scopes, so a dashboard can read numbers without ever seeing a name or an email.
How they work together.
- 01
Create a key.
Under Settings, API, create a key with the scopes your code needs.
- 02
Add an endpoint.
Choose the events to receive and send a test event to check your server.
- 03
Build on it.
Verify each signature, then route the event, or call the API for the full record.
A quick setup check.
- A server that accepts HTTPS requests and answers within 10 seconds, for webhooks.
- Owner or admin access in Darwin, to create keys and webhook endpoints.
FAQ
Webhooks + API integration questions.
Do I need to write code?
For webhooks and the API, yes, or use a tool that receives webhooks. Without code, use Darwin's Zapier app instead.
How do I know an event came from Darwin?
Each delivery is signed with your endpoint's secret using the Standard Webhooks scheme. The API reference shows how to verify it.
Is there a client library?
Yes. The TypeScript SDK is on npm as @meetdarwin/api, and the OpenAPI document describes every endpoint.
