Support
Write to us
Section titled “Write to us”[email protected] — one inbox, read by the people who build the API.
What makes a report fast to act on:
- the request id (
X-Request-IDheader, also inMrCharlesError.requestId); - the studio slug and, if relevant, the room id;
- what you sent and what came back (redact the guest’s phone and email);
- the time, with time zone.
What we commit to
Section titled “What we commit to”- Security issues: acknowledged within one business day, fixed first. Please do not open them in public.
- Bugs that block a booking: looked at the same business day.
- Questions and feature requests: answered within three business days. The public API grows from these — if you need lessons, bands or venues exposed, say what for.
Compatibility
Section titled “Compatibility”We add fields without notice. Inside v1 we never remove or rename a field, change a status code or change an error code. Breaking changes ship as v2 with a migration window; both run side by side. Everything is logged in the changelog.
Status
Section titled “Status”Incidents and maintenance are on the status page.