Build on your meetings.

Every meeting you record with Notabium becomes structured data: a transcript, a summary, next steps, and a draft follow-up. The API and MCP server let you pull all of it into your own tools, or hand it to an agent that can read and reason over your calls.

What you get

• A REST API. List your meetings, fetch a transcript with its summary and action items, search across every call, and ask a question of any single meeting. Bearer-token auth, JSON in and out.
• A remote MCP server. Point Claude Desktop, Cursor, or any MCP client at one URL and your assistant can read what was decided and cite the moment, with no glue code.

The same data backs both. The REST API is for code; MCP is for assistants. Most people use both.

Step 1 - create an API key

Everything authenticates with a Notabium API key. Create one in the app, on the API keys page (Settings, then API). Give it a name you will recognise later.

The key is shown once, at creation. Copy it and store it somewhere safe (a password manager or your environment), because you will not be able to see it again. If you lose it, revoke it and make a new one.

Keys look like this:

The prefix ntb_live_ plus the next eight characters is what the app shows you in the key list (so you can tell keys apart). The full key is the whole string.

Step 2 - call the API

The base URL for every endpoint is:

Send your key as a bearer token in the Authorization header on every request:

curl https://api.notabium.com/v1/meetings \
  -H "Authorization: Bearer ntb_live_..."

That returns your most recent meetings as JSON. From there you can fetch a single meeting with its transcript and outputs, search across calls, or ask a question of one meeting. See the REST API reference for every endpoint.

What keys can and cannot do

API keys are read and ask only. They can list meetings, read transcripts and summaries, search, and ask questions of a meeting. They cannot create or delete meetings, change sharing, manage billing, or manage other keys. Those actions live in the app and require you to be signed in. This keeps a leaked key low-blast-radius: it can read your meetings, not reshape your account.

Keep reading