Client reports
Read bookings by tenant and build a weekly report for each business.
Agent API
Read booking data from your own server.
VoxelBooking exposes a small, read-only REST API for automation tools, reporting scripts, and private integrations. Bearer tokens. Scoped keys. JSON responses.
Bearer token auth
OpenAPI 3.0.3
Read-only v1
Current contract
Four resource routes. Nothing hidden.
The v1 API reads operational booking data. It does not create bookings, edit tenants, upload assets, trigger jobs, collect payments, or sync external calendars.
Read API docs| Route | Scope | Reads |
|---|---|---|
| GET /tenants | tenants:read | Businesses and booking patterns |
| GET /bookings | bookings:read | Bookings for one tenant |
| GET /services | services:read | Services for one tenant |
| GET /availability | availability:read | Available schedule rows |
| GET /schema | public | OpenAPI schema |
curl "https://your-domain.com/api/agent/v1/bookings?tenant_id=01HTENANT0000000000000000" \
-H "Authorization: Bearer vb_your_api_key" \
-H "Accept: application/json"Authentication
Keys are scoped before data leaves the server.
Each authenticated route checks the API key scopes before returning data. Keys are stored as SHA-256 hashes with a short prefix for identification. Successful requests update the key usage time record.
Scope checks
Missing scopes return a JSON 403 response.
Rate limit
60 authenticated requests per minute per key.
Use cases
Useful for reporting, not for replacing the admin panel.
The Agent API is built for read access. Use it to pull booking data into private dashboards, reporting jobs, backup checks, or operational scripts.
Operational checks
Confirm tenant, service, and booking data is reachable from monitoring scripts.
Private integrations
Feed booking data into internal tools without exposing database credentials.
Own the booking system. Read the data cleanly.
VoxelBooking runs on your server with full source code, MySQL data, and a small JSON API for the reads integrators need first.