The Jurnie API

Create API keys so your own tools and scripts can read your meetings, summaries and transcripts through Jurnie's read-only API, and send summaries to other tools with webhooks.

The Jurnie API lets your own tools and scripts read what you can see in Jurnie: your meetings with their summaries and transcripts, your teamspaces and, when memory is on for your organization, what Jurnie remembers. It's read-only. Each API key belongs to one person and sees exactly what that person can see.

Turn on API access

Admins: API access is turned on for each organization by Jurnie. To turn it on or off for yours, email support@jurnie.ai.

Until it's on, the API keys tab doesn't appear in Settings. Turning it off later pauses every key until it's turned back on; no key is deleted.

Create a key

  1. Click your name at the bottom of the sidebar, then Settings, and open API keys.
  2. Click Create API key.
  3. Give the key a name, such as "Reporting script", and click Create key.
  4. Copy the key and store it somewhere safe. You won't be able to see it again.
  5. Click Done.
The API keys settings with two keys, when each was created and last used, and the API documentation link

Keys start with jrn_. You can have up to 10 active keys.

Use a key

Send the key as a bearer token in the Authorization header. For example, to list your meetings:

curl https://app.jurnie.io/api/v1/meetings/ \
  -H "Authorization: Bearer $JURNIE_API_KEY"

Click API documentation on the API keys tab for every endpoint and field. The documentation is public, at https://app.jurnie.io/api/v1/docs/, so you can read it before you have a key.

Each key can make 600 requests an hour. Every response carries X-RateLimit-Limit and X-RateLimit-Remaining headers so your script can slow down in time.

Revoke a key

In the list, open the menu at the end of the key's row, click Revoke and confirm. Anything using the key stops working immediately, and this can't be undone. The Last used column helps you spot keys nobody uses any more.

A key works in the organization it was created in. It also stops working if its owner is deactivated in that organization or leaves it.

Send summaries to other tools with webhooks

A webhook sends each meeting's summary to a URL you choose as soon as it's ready, so a tool like Zapier, Make or n8n can pass it on to your CRM, project tool or team chat. It sends the meetings you can see in Jurnie, with their title, time, invitees and speakers. Transcripts aren't included.

  1. In the other tool, add a step that receives a webhook (in Zapier, Webhooks by Zapier with Catch Hook) and copy its URL.
  2. In Jurnie, click your name at the bottom of the sidebar, then Settings, open API keys, and click Add webhook under Webhooks.
  3. Give the webhook a name, paste the URL and click Add webhook.
  4. Click Send test event to check that the other tool receives it, then click Done.

When a summary changes later, for example after you fix a name, Jurnie sends it again marked as updated. Click a webhook's name to see what was sent recently and whether it arrived.

If the URL keeps rejecting events, Jurnie turns the webhook off and emails you, and its status shows Turned off — failing. Fix the receiving side, then choose Resume in the webhook's menu. Summaries from while it was off aren't sent again.

Developers: every event is signed with the webhook's signing secret, which Show secret in its menu reveals. How webhooks work, next to the Webhooks heading, describes the event and how to check the signature.

Tip: To ask an AI assistant such as Claude about your meetings, you don't need a key. See Use Jurnie from Claude, ChatGPT and other AI tools.

Last updated November 10, 2026