Browse the docs
Documentation

Overview

What the VoiceCap API does, its base URL and the shape of every response.

The VoiceCap API lets your own code, and automation tools such as Zapier, Make or n8n, read your meetings, decisions and action items, and get a webhook when a meeting is ready. It returns the same meetings you see in VoiceCap, filtered by the same rules: your role, your groups and the meetings shared with you.

Base URL

https://voicecap.ai/api/v1

Every request sends a personal API key in the Authorization header. See Authentication for how to get one.

What you can do

EndpointWhat it does
GET /meThe person and organization the key belongs to. Use it to test a key.
GET /meetingsMeetings you can open, with sorting and filters.
GET /meetings/{id}One meeting with its summary, action items and transcript.
GET /meetings/{id}/transcriptThe transcript in 15-minute sections, for a meeting of any length.
GET /meetings/{id}/exportThe meeting as a PDF, Word, text or subtitle file.
GET /searchSearch what was said in your meetings.
GET /decisionsDecisions, newest first.
GET /action-itemsAction items, from the most recently processed meeting first.
GET /groupsGroups you can see.
POST /hooks, GET /hooks, DELETE /hooks/{id}Subscribe, list and unsubscribe webhooks.
GET /hooks/sampleRecent events, in the same shape a webhook delivers them.

The API doesn't create, change, share or delete meetings. Webhook subscriptions are the only thing it writes. Every parameter and field is listed in the API reference, which is also available as an OpenAPI 3.1 file.

Responses

Every JSON response is an envelope. A successful one carries data:

{ "success": true, "data": { "decisions": [], "hasMore": false } }

A failed one carries error, with a code your code can check:

{ "success": false, "error": { "type": "error", "code": "invalid_api_key", "message": "Invalid API key" } }

The export endpoint is the one exception: when it works, the response is the file itself.

Dates and times

Every date is an ISO 8601 instant. List endpoints return them in UTC, such as 2026-10-16T08:30:00.000Z. Webhook events carry the key owner's own time zone offset, such as 2026-10-16T11:30:00+03:00. Both describe the same moment, so compare them as instants rather than as text.