Mattering Calendar API
Event types, live slot feeds and bookings for Mattering Calendar.
https://calendar.mattering.io/api/user/v1/
Service tierhttps://calendar.mattering.io/api/internal/v1/
Resources
15 endpoints, 8 on the User API, 7 service-only.
| Resource | Endpoints | Methods | Tiers |
|---|---|---|---|
| Bookings | 3 | GETPOST | User API |
| Event types | 3 | GET | User API |
| Search | 1 | GET | User API |
| Spaces | 1 | GET | User API |
Service tier only
These resources are reachable with the internal secret only. They are documented for operators and for anyone reading the MCP tools that wrap them.
| Resource | Endpoints | Methods |
|---|---|---|
| Org erasure | 1 | GET |
| Org export | 1 | GET |
| Sync | 3 | POST |
| User erasure | 1 | GET |
| User export | 1 | GET |
Shape against the shared standard
Mattering is converging every app on one API shape (the Base API Template). This is where Calendar stands, measured from its code. Read it before assuming the envelope on one app matches another.
| Yes | User tier mounted (/api/user/v1/) | |
| Yes | Internal tier versioned (/api/internal/v1/) | |
| Yes | One api_urls.py included on both tiers | |
| Not yet | Responses use the {data, meta} envelope | 12 of 15 endpoints |
| Not yet | Collection reads paginate with meta.total | 1 of 8 list endpoints paginate |
| Yes | Errors carry a snake_case code and a detail | 34 of 34 error returns use a stable code |
Source: CalendarCore/api_urls.py. Regenerated by tools/build_api_docs.py.