API overview
The Meetor API lets Pro workspaces read their meeting data from scripts, spreadsheets, and dashboards. It is read only.
Base URL
Section titled “Base URL”https://api.meetor.coPublic endpoints live under /v1/public. The OpenAPI document is at https://api.meetor.co/openapi.json.
Endpoints
Section titled “Endpoints”| Method | Path | Returns |
|---|---|---|
| GET | /v1/public/meetings |
Meetings with totals. No rates. |
| GET | /v1/public/reports/summary |
Totals for a period, by topic, role, and title. |
| GET | /health |
Service status. No token needed. |
The full request and response shapes are in the API reference.
Tokens
Section titled “Tokens”- API tokens are a Pro feature.
- Each token is read only and belongs to one workspace.
- Send it in the
Authorizationheader:Authorization: Bearer mt_live_...
See Authentication.
Conventions
Section titled “Conventions”- Money is an integer in minor units, for example cents for USD.
12345in USD is $123.45. Each response carries the workspace currency code. - Times are epoch milliseconds in UTC.
- No rates. The API returns totals. It never returns an individual’s salary or hourly rate.
- JSON in and out, UTF-8.
Errors
Section titled “Errors”Every error uses one shape:
{ "error": { "code": "unauthorized", "message": "Missing or invalid API token.", "details": {} }}code is a stable, machine-readable string. message is a plain sentence for people. details is optional and carries extra context, such as which query parameter failed validation.
| Status | Meaning |
|---|---|
| 400 | A parameter is missing or invalid. |
| 401 | The token is missing, unknown, or revoked. |
| 403 | The workspace is not on Pro. |
| 500 | Something failed on our side. Retry later. |
Examples
Section titled “Examples”See Examples for curl and JavaScript.