Skip to main content
The Meetings API gives integrations the same operations the Meetings app offers: create and plan meetings, invite people, keep the agenda, run and close a meeting, and read or record its outcomes, decisions and polls. Every call runs as the person who issued the token, with exactly the rights that person has in Collabase.

​
Meeting lifecycle

A meeting starts as a draft that only its organizers see in their calendar view. Planning it sends the invitations. A planned meeting is started by a moderator, then closed, which freezes it and queues the meeting note. A closed meeting can be reopened for a correction. Drafts and planned meetings can be cancelled. A call in the wrong state, for example starting a draft, returns 409 CONFLICT.

​
Scopes

A token without the scope receives 403 INSUFFICIENT_SCOPE. A token with the scope still cannot do more than its owner: a person who may not edit a meeting gets 403 FORBIDDEN through the API too.

​
Conventions

  • Visibility. A meeting the caller may not see answers 404 NOT_FOUND, exactly like one that does not exist. Private meetings are visible only to their participants.
  • Times. Instants in responses are ISO 8601 in UTC. When you create or move a meeting, date (YYYY-MM-DD) and time (HH:mm) are wall-clock values in the time zone of the token owner’s profile, the same way the app reads them. Instants you send, such as baseUpdatedAt and a poll’s closesAt, must be UTC with a Z (2026-10-15T08:05:12.000Z); an offset such as +02:00 is rejected with 422.
  • Concurrent edits. Changes to agenda sections, agenda items, outcomes and decisions carry baseUpdatedAt, the updatedAt you read. If someone changed the object since, the request returns 409 CONFLICT with the object as it is now in current, next to error. Re-read, merge and send again. Draft polls carry baseUpdatedAt as well; their conflict returns 409 CONFLICT without current.
  • Strict bodies. Unknown fields are rejected with 422 VALIDATION_ERROR, not silently dropped. A missing or malformed JSON body answers 422 too, except on the endpoints whose body is optional (Cancel meeting, Close meeting).
  • Limits. A meeting holds up to 500 participants, 50 agenda sections, 200 agenda items, 500 outcomes, 300 decisions and 50 polls. Going beyond answers 400 VALIDATION_ERROR.

​
Errors

On top of the general errors:
409

​
Endpoints

​
Reacting to changes

There is no separate webhook subscription for meetings. Build an automation on one of the meeting events (created, updated, cancelled, closed, decision recorded, note published) and add an HTTP action that calls your system. An event reaches only automations whose owner may see the meeting. It carries identifiers, dates and a decision’s title, never agenda text or notes; read the details through this API with a token of your own. The other direction works too: the Collabase connector has the automation actions Create Meeting, Add Agenda Item (also to the next occurrence of a series) and Invite to Meeting, which act with the automation owner’s rights. See the Collabase connector.

Meetings

List, create, read, change and delete meetings.

Lifecycle

Plan, start, close, reopen and cancel a meeting.

Participants

Invite members and guests, change roles, answer invitations.

Agenda

Sections, items and their order.

Outcomes

What came out of each agenda item while the meeting ran.

Decisions

Record, reword, replace and revoke decisions; search the register.

Polls

Prepare, open and close polls; read turnout and results.

Series

Turn a meeting into a series, change its rule, page through occurrences.
Last modified on October 4, 2026