API reference
LatinSync Central runs on a REST API. Access is granted per studio rather than published openly, so integrations start with a conversation.
What the API covers
Studios and classes
Studio profiles, class definitions, recurring schedules and instructor assignments.
Students and memberships
Student records, membership plans, subscription state and usage against class limits.
Bookings and attendance
Class and event bookings, check-in, cancellation and attendance history.
Events
Socials, workshops, showcases and competitions, including multi-day events and RSVPs.
Payments
Payment intents and transaction records. Card data is handled by Stripe and never passes through the API.
How access works
Bearer token authentication
Requests are authenticated with a short-lived access token obtained from the auth endpoints and refreshed as needed.
Scoped to one studio
Every request is authorised against the studio it targets and the role of the caller. There is no cross-studio access.
Public endpoints are limited
A small number of routes are unauthenticated — the shareable calendar, class and booking pages. Everything else requires a token.