How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Wispr AI Meetings API

The Meetings API from Wispr AI — 7 operation(s) for meetings.

Wispr AI Meetings API is one of 50 APIs that Wispr AI publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Meetings. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 7 operations across 7 paths, and defines 17 schemas. It is described by OpenAPI 3.2.0, at version 0.5.2.

Requests are made against a single base URL, https://api.wisprflow.ai.

7 operations 7 paths 17 schemas 1 DELETE2 GET4 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
0.5.2
Base URL
https://api.wisprflow.ai
Authentication
API Key, API Key
Resource Areas
1

Authentication & Security 2

Wispr AI Meetings API declares 2 security schemes for authenticating requests. An API key is passed in the header as Authorization (ApiKeyHeaderPatched). An API key is passed in the header as X-API-Key (APIKeyHeader).

Paths & Operations 7

Across 7 paths, the API surfaces 7 operations — 1 DELETE, 2 GET, 4 POST. Each is listed below with its method, path, parameters, and response codes.

Meetings 7
POST
/api/v1/meetings/sync
Sync Meetings
sync_meetings 1 param body → 200422
DELETE
/api/v1/meetings/{meeting_id}
Delete Meeting
delete_meeting 1 param → 204404500422
POST
/api/v1/meetings/{meeting_id}/upload-url
Create Meeting Upload Url
create_meeting_upload_url 1 param body → 200429503422
GET
/api/v1/meetings/{meeting_id}/status
Get Meeting Status
get_meeting_status 2 params → 200404429422
GET
/api/v1/meetings/{meeting_id}/refined-transcript
Get Refined Transcript Download Url
get_refined_transcript_download_url 1 param → 200403404429422
POST
/api/v1/meetings/{meeting_id}/speaker-observations/upload-url
Create Speaker Observations Upload Url
create_speaker_observations_upload_url 1 param body → 200429422
POST
/api/v1/meetings/{meeting_id}/live-transcript/upload-url
Create Live Transcript Upload Url
create_live_transcript_upload_url 1 param body → 200429422

Schemas 17

The contract defines 17 schemas that model the data the API accepts and returns. The most detailed are SyncMeeting-Input (21 properties), SyncMeeting-Output (21 properties), MeetingStatusResponse (6 properties), ValidationError (5 properties). Each schema is shown below with its type and property counts.

MeetingSyncRequest
object
Request model for meeting synchronization.
4 properties 1 required
SpeakerMap
object
The meetings.speakermap blob (nullable JSONB on the meeting row). people is keyed by person id (a plain uuid4 string, minted by whoever creates the person); as…
2 properties
ValidationError
object
5 properties 3 required
SyncMeeting-Output
object
Model for meeting data in sync requests. The live transcript is uploaded out-of-band via a presigned S3 PUT; the client then sets livetranscriptuploaded on its…
21 properties 5 required
SpeakerObservationsUploadUrlRequest
object
Request for a presigned S3 slot to upload a meeting's speaker-observation log. Distinct from :class:MeetingUploadUrlRequest: NDJSON not audio, an 8 MiB cap not…
2 properties 2 required
LiveTranscriptUploadUrlRequest
object
Request for a presigned S3 slot to upload a meeting's live-transcript NDJSON. Sibling to :class:SpeakerObservationsUploadUrlRequest: same NDJSON content type,…
2 properties 2 required
MeetingStatusResponse
object
Refine-progress snapshot the desktop pulls as a backstop to sync. The client polls GET /meetings/{id}/status with the refine status it currently believes, and…
6 properties 1 required
RefineJobStatus
string
MeetingUploadUrlResponse
object
Presigned S3 POST the desktop uses to upload refine audio directly. The S3 object key is carried inside fields['key'] per the S3 presigned-POST contract, so it…
3 properties 3 required
SpeakerPerson
object
One person in :attr:SpeakerMap.people, keyed by a plain uuid4 string. platform is immutable after mint; origin changes only via the calendar-merge upgrade (pla…
4 properties 2 required
HTTPValidationError
object
1 property
MeetingRefinedTranscriptUrlResponse
object
Presigned S3 GET for a meeting's refined-transcript NDJSON. The download twin of :class:MeetingUploadUrlResponse (same shape as the notes NoteImageKey payload)…
2 properties 2 required
SpeakerAssignment
object
One refinedid's person slots in :attr:SpeakerMap.assignments. Machine slots — dom (tile consensus), mic (reserved for the owner/mic channel), llm (post-summary…
5 properties
SyncMeeting-Input
object
Model for meeting data in sync requests. The live transcript is uploaded out-of-band via a presigned S3 PUT; the client then sets livetranscriptuploaded on its…
21 properties 5 required
MeetingUploadUrlRequest
object
Request for a presigned S3 slot to upload a meeting's refine audio.
5 properties 2 required
NoteVisibility
string
MeetingSyncResponse
object
Response model for meeting synchronization.
4 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

wispr-ai-meetings-api-openapi.yml Raw ↑

Other APIs Wispr AI publishes across the network.

Wispr AI Analytics API
Wispr AI Analytics Registry API
Wispr AI Attribution Tracking API
Wispr AI Authentication API
Wispr AI Automations API
Wispr AI Calendar API
Wispr AI Connectors API
Wispr AI Cost Centers API
Wispr AI Dash API
Wispr AI Dictionary API
Wispr AI Enterpret API
Wispr AI Enterprise API
Where this information came from

This is an independent, third-party profile of Wispr AI Meetings API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.