Developer API

The Vytal API is a single REST surface at https://api.vytal.fit/v1. Partner
integrations read and write members, bookings, classes, subscriptions, payments,
and more, and every call runs in the context of the organization behind your
API key.

📘
New here? Start with the Quickstart: create a key and make
your first call in two requests.

Hosts

Host	Serves
`api.vytal.fit/v1`	The REST API
`api.vytal.fit/openapi.json`	The OpenAPI contract
`pro.vytal.fit`	proVytal, the staff backoffice
`my.vytal.fit`	myVytal, the athlete portal
`vytal.fit`	The public marketing site

Authentication

Send your organization API key as a Bearer token on every request:

Authorization: Bearer vk_live_…

Create and revoke keys in Settings → API Keys (see
Authentication). The organization is implied by the key,
never passed in a body.

What you can do

Members & memberships: list, create, update, archive members; manage
subscriptions and plans.
Scheduling: read the class schedule and history; create classes; manage
bookings and the waitlist; record attendance and check-ins.
Training: publish WODs to your spaces.
Commerce: products, sales, orders, suppliers, and payments.

Personal, health, financial-internal, and BI resources (individual records and
WOD results, workout feedback and wellness check-ins, leads, expenses, dashboard
and reports) are first-party only and are not part of the external API surface.

Surface at a glance

Resource	Example
Members	`GET /v1/members` · `POST /v1/members`
Classes	`GET /v1/classes/schedule` · `POST /v1/classes`
Bookings	`POST /v1/bookings/book` · `POST /v1/bookings/cancel`
Subscriptions	`GET /v1/subscriptions` · `GET /v1/subscriptions/plans`
Payments	`GET /v1/payments` · `GET /v1/payments/stats`
Check-ins	`POST /v1/check-ins`
WODs	`GET /v1/wods` · `POST /v1/wods/publish`

The complete, always-current list is in the
OpenAPI document.

The contract

Versioned base path /v1; resources are clean nouns beneath it.
One error shape with predictable status codes.
Consistent conventions for list responses, dates, and
idempotency.
The spec is generated directly from the live backend, so it never drifts from
what's deployed.

Keep reading

Authentication: API keys in depth.
REST Principles: how paths and methods are shaped.
API Examples: copy/paste for bookings, classes, and check-ins.
Server & Integrations: patterns for server-to-server callers.
Deployment: hosts, origins, and environment variables.