Skip to main content

Documentation Index

Fetch the complete documentation index at: https://help.daylit.com/llms.txt

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

Daylit receives inbound webhooks from three third-party services: Merge.dev (accounting data), Nylas (email), and Vonage (voice calls). These webhooks are configured automatically when you connect each integration — you do not register them yourself. They keep your AR data, communication threads, and call records up to date in real time without you needing to trigger manual syncs.
These webhooks are incoming — they are called by third-party services and received by Daylit. You do not need to handle or forward these requests yourself.

​
Merge.dev webhook

POST /api/webhooks/merge
Merge.dev calls this endpoint when a linked accounting account finishes syncing data (for example, when new invoices or payments are available from NetSuite, QuickBooks, or Xero). Daylit processes the event and updates your AR data accordingly.

​
Trigger event

Merge sends a linked_account.synced event. Daylit ignores all other event types.

​
Request payload

{
  "hook": {
    "id": "hook-uuid",
    "event": "linked_account.synced"
  },
  "linked_account": {
    "id": "linked-account-uuid",
    "end_user_organization_name": "Acme Corp",
    "status": "COMPLETE"
  },
  "data": {}
}
​
hook.event
string
Event type. Daylit processes linked_account.synced.
​
linked_account.id
string
The Merge linked account ID used to identify which integration connection to update.
​
linked_account.end_user_organization_name
string
Human-readable name of the organization in Merge.

​
Security

Merge signs every webhook with an HMAC-SHA256 signature transmitted in the X-Merge-Webhook-Signature header. Daylit verifies this signature automatically — requests with a missing or invalid signature are rejected with a 401 Unauthorized response.

​
Response

{
  "status": "processed",
  "connection_ids": ["conn-uuid-1"],
  "skipped": []
}
Daylit always returns 200 OK to Merge, even when a sync is already in progress, to prevent unnecessary retries.

​
Nylas webhook

GET  /api/webhooks/nylas
POST /api/webhooks/nylas
Nylas calls this endpoint when a new email arrives in a connected mailbox. Daylit processes the event and updates the relevant customer communication thread.

​
Verification handshake

When you register a Nylas webhook, Nylas sends a GET request with a challenge query parameter. Daylit echoes the challenge value back automatically — no action required on your part.

​
Trigger event

Daylit processes message.created events. All other event types are acknowledged and ignored.

​
Request payload

{
  "specversion": "1.0",
  "type": "message.created",
  "data": {
    "object": {
      "grant_id": "<NYLAS_GRANT_ID>",
      "id": "<MESSAGE_ID>"
    }
  }
}
​
type
string
Event type. Daylit processes message.created events.
​
data.object.grant_id
string
The Nylas grant ID identifying which connected email account received the message.

​
Security

Nylas signs POST bodies with an HMAC-SHA256 hex digest in the X-Nylas-Signature header. Daylit verifies this signature before processing — requests without a valid signature receive a 401 Unauthorized response.

​
Response

{
  "status": "processed",
  "connections": [
    {
      "status": "triggered",
      "connection_id": "conn-uuid"
    }
  ]
}

​
Vonage webhooks (voice)

Vonage calls three endpoints during a voice call session. These are used by the Daylit voice agent feature to manage call control, status updates, and recording delivery.

​
Answer webhook

GET  /api/webhooks/vonage/answer
POST /api/webhooks/vonage/answer
Called by Vonage when a call is answered. Daylit responds with call control instructions that configure recording and connect the call.

​
Events webhook

POST /api/webhooks/vonage/events
Called by Vonage throughout the call lifecycle to report status transitions. Daylit uses these events to update the call session status.
Vonage statusCall session status
started, ringing, answeredpending
completedcompleted
timeout, failed, rejected, busy, unanswered, cancelledfailed

​
Recording webhook

POST /api/webhooks/vonage/recording
Called by Vonage when a call recording is ready. Daylit stores the recording and triggers transcription. The transcript is linked to the customer’s communication thread.

​
Setting up webhooks

Webhooks are configured when you connect each integration in Settings → Integrations:
  • Merge.dev — Set up when you connect your accounting system. Daylit handles webhook registration with Merge automatically.
  • Nylas — Set up when you connect your email account. Daylit registers the webhook with Nylas as part of the OAuth flow.
  • Vonage — Set up when you activate voice calling for your workspace.

Integrations

Connect accounting, email, and voice integrations that power these webhooks.

Integrations API

Manage integration connections programmatically via the REST API.