Skip to main content

Webhooks

Set Up tl;dv Webhooks

Written by Suellen Lorga

Webhooks allow you to receive real-time notifications from tl;dv when meetings and transcripts are ready. Instead of repeatedly checking the API for updates, tl;dv sends data directly to your endpoint as soon as an event occurs.

Webhook access is available on the Pro or Business plans only.


What Are Webhooks?

Webhooks automatically send data from tl;dv to your application when specific events occur.

This allows you to:

  • Trigger workflows when a meeting is processed

  • Send meeting data to external systems

  • Automate reporting and integrations

  • Receive transcript data as soon as it becomes available

All webhook payloads use the same data structure as the tl;dv API, making it easier to build integrations using both services.


Available Webhook Events

You can subscribe to one or both of the following events.

Event

Trigger

MeetingReady

A meeting has finished processing and is ready to use.

TranscriptReady

A transcript has been generated and is available.


Webhook Scope Options

Webhooks can be configured at different levels depending on how broadly you want to receive events.

Scope

Description

User

Events for a single user only

Team

Events for all users within a team

Organization

Events across the entire organization

Choose the scope that best matches your integration requirements.


Create a Webhook

  1. Navigate to Webhooks

  2. Click Configure New Webhook

  3. Select the event you want to subscribe to

  4. Enter your Endpoint URL

  5. (Optional) Add custom headers or authentication details

  6. Click Save and Activate Webhook

Once activated, tl;dv will automatically send matching events to your endpoint.

⚠️ Your endpoint URL must support HTTPS. HTTP endpoints are not supported.


Optional Header Configuration

If your endpoint requires authentication or additional configuration, you can add custom headers during setup.

Common examples include:

Authorization: Bearer YOUR_TOKEN

or

x-api-key: YOUR_API_KEY

These headers will be included with every webhook request.


MeetingReady Event

The MeetingReady event is triggered when a meeting has completed processing and is ready to be accessed.

Example payload:

{
"id": "webhook-job-id",
"event": "MeetingReady",
"executedAt": "2025-06-16T09:23:00Z",
"data": {
"id": "meeting-id",
"happenedAt": "2025-06-15T14:00:00Z",
"name": "Team Sync",
"organizer": {
"email": "organizer@example.com",
"name": "Alex Taylor"
},
"invitees": [
{
"email": "teammate@example.com",
"name": "Jordan Lee"
}
],
"url": "https://app.tldv.io/meetings/meeting-id"
}
}

This payload includes meeting metadata such as:

  • Meeting ID

  • Meeting title

  • Meeting date and time

  • Organizer information

  • Invitees

  • Meeting URL


TranscriptReady Event

The TranscriptReady event is triggered when a meeting transcript becomes available.

Example payload:

{
"event": "TranscriptReady",
"data": {
"id": "transcript-id",
"meetingId": "meeting-id",
"data": [
{
"startTime": 1,
"endTime": 14,
"speaker": "User Name",
"text": "Transcript content..."
}
]
},
"id": "webhook-job-id",
"executedAt": "2025-09-26T14:33:03.605Z"
}

The payload contains:

  • Transcript ID

  • Meeting ID

  • Transcript segments

  • Speaker information

  • Timestamps

ℹ️ Calendar event metadata is not included in the TranscriptReady payload. This means organizer and invitee information are not available for this event.


Best Practices

When building webhook integrations:

  • Ensure your endpoint responds quickly

  • Verify incoming requests before processing data

  • Store webhook payloads for troubleshooting when needed

  • Use HTTPS endpoints only

  • Monitor your endpoint for failed deliveries


Troubleshooting Webhooks

I am not receiving webhook events

Check the following:

  1. Confirm the webhook is active in your tl;dv settings

  2. Verify the selected event type matches the expected trigger

  3. Ensure your endpoint is publicly accessible

  4. Confirm your endpoint supports HTTPS

  5. Review any authentication headers configured on the webhook

My endpoint receives requests but cannot process them

Check that:

  1. Your application accepts JSON payloads

  2. Required authentication headers are configured correctly

  3. Your application can parse the webhook payload structure

I need organizer or attendee information

Use the MeetingReady event.

The TranscriptReady event does not include organizer or invitee metadata.


Need Help?

If you need help configuring webhooks or troubleshooting an integration, contact our support team:

You can also reach us through the chat widget in the tl;dv application.

Did this answer your question?