Rooms and equipment you can invite

GET/api/v1/mailbox/calendar/rooms
Requires amailbox token— it acts as one mailbox holder, not as the organization.

The bookable rooms in this mailbox's own organisation.

This exists so that somebody making a meeting can PICK a room rather than know its address by heart. Without it the address is the only handle a person has, and an address typed from memory is a booking that silently goes nowhere -- which is most of the reason rooms went unused.

Read-only and mailbox-scoped on purpose. Creating a room is an admin decision and stays on /calendar-resources behind an API key; seeing what you may invite is not. The exposure is the same shape as free/busy -- your own organisation's directory, nobody else's -- so it is bounded the same way, by organization_id and nothing the caller can supply.

Inactive rooms are omitted rather than shown greyed out: a room switched off is one nobody should be trying to book, and offering it only produces an invitation that is never answered.

Request

GET/api/v1/mailbox/calendar/rooms
curl -X GET 'https://app.mailyte.com/api/v1/mailbox/calendar/rooms' \
  -H 'Authorization: Bearer MAILBOX_TOKEN'
The key names its own organization, so no X-Organization-ID header is needed.

Response

Successful Response

Returned inside the standard envelope.

Errors

Every status, with what causes it and what to do, is on the error reference.