Webhook API

Webhook API lets you automatically send Krisp meeting outputs (like transcripts, notes, and outlines) to another tool or internal system via a secure URL endpoint.

What can you send?

When enabled, Krisp can send webhook events when:

• Transcript is created.

• Notes are generated (key points / action items).

• Outline is generated.

You can choose one event or multiple events during setup.

Before you start

You’ll need:

• A Webhook URL (an endpoint that can receive HTTPS POST requests).

• (Optional) Any required authentication headers (for example, an API token).

Set up a webhook

1. In Krisp, go to Settings.

2. Select Integrations.

3. Find Webhook and choose Connect.

4. In Create Webhook, fill in:

   • Webhook name (for your reference).

   • Webhook URL (where Krisp will send events).

   • Trigger Events (select the events you want).

   • Request Headers (Optional)
     Add any headers your endpoint requires (example: Authorization).

5. Click Create.

Add or remove request headers (optional)

In the webhook setup, you can add multiple headers as key/value pairs.

• Use the + control to add a new header row.

• Use the trash/delete control to remove a header.

Common examples:

• Authorization: <token>
• X-Api-Key: <key>

Test your webhook

After creating the webhook:

1. Open the webhook’s Configure tab.

2. Click Send sample note.

Krisp will send a sample payload to your Webhook URL so you can confirm your system receives it.

What success looks like:

• Your endpoint/tool receives a POST request.

• Krisp indicates the sample was sent successfully.

View delivery history

Open the webhook’s History tab to see recent deliveries, including:

• Date
• Meeting
• Event ID
• Trigger event

• Status (for example: Success)

Manually send a meeting to your webhook

From a meeting page in Krisp:

1. Open the meeting.

2. Use the integrations dropdown menu (top-right area).

3. Select Send to Webhook.

What data is included in the webhook payload

Krisp sends a JSON payload that includes:

• An event identifier (Matching the trigger type).

• Meeting details (For example: Meeting ID, title, link/URL, start/end time, duration).

• Generated content (For example: Notes/summary text; and where applicable, transcript/outline content).

• A unique event ID.

Exact fields may vary depending on which trigger event fired.

FAQ

• Why is nothing arriving at my endpoint?

  • Confirm the Webhook URL is correct and publicly reachable.
  • Confirm that the meeting has the data that should be sent (Transcript, notes, or outline).

  • Try Send sample note again.

• Why am I getting authentication errors?

  • Add the required Request Headers (e.g., Authorization token).

  • Confirm the token/key is valid and not expired.

• Why are some events that I'm expecting are not triggering?

  • Check you selected the correct Trigger Events in the webhook configuration.