Documentation
Build on the box office.
One engine behind three surfaces REST API, hosted portal and MCP server. These docs cover the parts you drive with code.
Quickstart
Sandbox key to first sold ticket in about ten minutes.
start hereREST reference
Every resource and endpoint auth, errors, pagination, rate limits, idempotency.
api.zatabox.comWebhooks
27 signed event types, HMAC verification, retries and replays.
x-zatabox-signatureSDKs
Official clients for Node, Python, PHP, Go and Ruby generated from the OpenAPI spec.
@zatabox/nodeWidgets
Checkout in one tag. Web components plus React, Vue and Svelte wrappers.
<zatabox-checkout>MCP server
Hand an AI agent the box office tools, scopes, audit trail, reversal window.
mcp.zatabox.comYour first call#
Grab a test key (prefix vt_test_) from the portal under API keys and make your first call test keys run every feature, including webhooks and all four payment providers, in test mode.
terminal
$ curl https://api.zatabox.com/api/v1/events \ -H "Authorization: Bearer vt_test_…" HTTP/2 200 { "data": { "items": [], "nextCursor": null } } # empty for now