Changelog

Notable changes to AvailEngine.

v2.1.0 — 2026-06-15

Dynamic (Instant) Booking: New /v1/dynamic/ API surface — real-time resource availability without a time grid. Guests pick any time, the API checks if something is free right now. Gated behind the Scale plan.
Dynamic booking docs: Full integration guide with use cases (restaurant live seating, gym spot booking, co-working, hotel breakfast).

Pricing restructured: New Free tier (1 business, 50 bookings/mo — no credit card). Starter €9.99/mo (5 businesses, 100 bookings each). Growth €29.99/mo (25 businesses, 1,000 each). Scale €129/mo (unlimited + dynamic booking). Platform tier removed.
Booking limits are now per-business (not per-developer). Each business gets its own monthly allowance under the developer's plan.
Sandbox replaced by Free tier: is_dev businesses no longer bypass limits. Every developer starts on the Free tier automatically.

Terminology: "Restaurant" → "Business", "Table" → "Resource", "Guest" → "Customer"
Booking body: first_name/last_name/phone moved into customer object
API versioning: All endpoints under /v1/ prefix
Auth: Dual-path — API key (primary) or JWT (fallback). Old business-owner-only JWT still works.
Pricing: 4-tier developer subscription (€9.99–€199.99/mo) based on businesses and booking volume. Replaces per-business subscription model.

API Key Auth: Bearer token authentication with scoped keys (read, write)
Developer Portal: Registration, business CRUD, quickstart snippets, billing management
Stripe Billing: Metered subscription (per active business), 402 enforcement, invoicing
Usage Tracking: api_usage table with fire-and-forget middleware
Rate Limiting: Per-key RPM limits with Retry-After header
Idempotency: Idempotency-Key header on all POST/PATCH
Cursor Pagination: All list endpoints
Google Calendar: Two-way sync — bookings ↔ Google Calendar events
Webhook Signing: X-AvailEngine-Signature with HMAC-SHA256 verification
Status Page: /status endpoint with DB + Stripe health checks
Structured Logging: JSON log format
VitePress Docs: Full documentation site at docs.availengine.com

Error Format: All errors use {"error": {"code": "...", "message": "..."}}
Auth Middleware: API key checked before JWT fallback
Route Structure: /v1/manage/ for staff, /v1/developer/ for developers, /v1/public/ for unauthenticated
Business Schema: Added owner_user_id, is_active, is_dev, business_type

Per-business subscription plans (trial/basic/pro). Replaced by 4-tier developer subscription.
Old restaurant-specific terminology in the API (backward-compat aliases remain where safe)

Next: Getting Started →