Tours & Events

Changelog

API version history and notable changes

The API follows the versioning policy. Entries below are reverse-chronological; additive entries are non-breaking.

2026-05-20

Documentation refactor (Phase 18)

  • Expanded reference coverage from 6 resource groups to 20 (added API keys, billing, plans, coupons, referrals, webhooks, organizations, users, invitations, announcements, audit logs, impersonation, settings, vehicle assignments).
  • Added shared conventions pages: errors, pagination, rate limits, idempotency, request IDs, versioning, webhooks.
  • Introduced custom MDX components (<Endpoint>, <Parameters>, <Response>, <Badge>, <RateLimit>) for consistent reference formatting.
  • Bridged Fumadocs and DaisyUI theme tokens so docs match the app shell in both light and dark mode.

No behavioural API changes.

2026-05-01 — v1.0

Initial public API release.

Endpoints

  • GET, POST /events and GET, PATCH, DELETE /events/{id} plus team / guests / vehicles / expenses sub-resources.
  • GET, POST /tours and GET, PATCH, DELETE /tours/{id}.
  • GET, POST /guests and GET, PATCH, DELETE /guests/{id}.
  • GET, POST /vehicles and GET, PATCH, DELETE /vehicles/{id}.
  • GET, PATCH, DELETE /expenses/{id} and GET /expenses/reports.
  • POST /notifications/whatsapp, /notifications/email, /notifications/bulk.
  • GET, POST, PATCH, DELETE /api-keys (full lifecycle).
  • PATCH /users/me.
  • PATCH, DELETE /vehicle-assignments/{id}.

Platform

  • API key Bearer authentication.
  • Session-cookie authentication for the dashboard.
  • Per-principal rate limiting (default 100 requests / 60 seconds).
  • Page + limit pagination on list endpoints.
  • Multi-tenant scoping — cross-org resource access returns 404.

On this page