OPEN Public API

The API is a read-only JSON REST API served over HTTPS at https://app.openmanagerapp.com/api/v1. Every endpoint returns JSON and is scoped to a single studio: a request can only ever see the data of the studio that owns the API key it was made with.

A typical first call lists your studio locations: send a GET request to https://app.openmanagerapp.com/api/v1/locations with your API key in the Authorization header. From there you can read the schedule for a date range, drill into a single class, search students, and look up memberships.

All requests must use HTTPS. Responses are UTF-8 JSON. Dates are ISO 8601 (YYYY-MM-DD); times are returned per class as start and end fields.

Authenticate every request with your API key. Send it either as a bearer token in the Authorization header — Authorization: Bearer <api_key> — or in the X-API-KEY header. Requests without a valid key return 401.

Keys are per-studio and scoped: a key only ever grants read access to the data of the studio it belongs to. There is no cross-studio access and no write access. Treat your key like a password — anyone with it can read your studio data. If a key is exposed, revoke it in the dashboard and generate a new one.

API keys are generated from the admin dashboard. Open OPEN Manager (openmanagerapp.com), go to Business Profile, and open the API Keys section. Generate a key there, copy it, and store it somewhere safe — it is shown once.

You can hold more than one key and revoke any of them at any time from the same screen. Revoking a key takes effect immediately and breaks any integration still using it, so rotate deliberately: generate the replacement first, switch your integration over, then revoke the old key.

All paths are relative to the base URL https://app.openmanagerapp.com/api/v1. Every endpoint is GET and read-only. The machine-readable contract (request and response schemas) is in the OpenAPI document linked below.

Errors are returned as JSON in the shape { "error": <code>, "message": <text> }, with a matching HTTP status. 401 means the API key is missing or invalid. 404 (not_found) means the requested resource does not exist or is not in your studio. 422 (invalid_params) means a parameter was malformed or out of range — for example a schedule range longer than 31 days.

The API is rate limited per key (429 when you exceed the limit). If you receive a 429, back off and retry after a short pause. Because limits are per key, heavy automated workloads should use their own dedicated key.