Connect your systems to Round Connect

For studios on the Digital plan. A key sees one studio only. There is no health data in the API — no cautions, consent records, heart rate or “it hurt” details — by design.

1. Create a key

In the console: Connections → API and MCP → Create key. The key starts with rck_ and is shown once. Tick can send bookings only for the key your booking system uses. Revoke a key there at any time.

Every request: Authorization: Bearer rck_… · up to 120 requests a minute per key · JSON.

2. Read

Request	What you get
`GET /api/v1/studio`	Studio, product, plan, language, rooms with their `id` and format
`GET /api/v1/classes?since=…&room_id=…`	Classes, newest first, with attendance (default: last 30 days)
`GET /api/v1/classes/{id}/attendance`	Who attended a class
`GET /api/v1/clients?drifting=true`	Clients: visits in 30 days, last visit, drifting away
`GET /api/v1/programmes`	Class programmes

Machine-readable description: /api/v1/openapi.json (OpenAPI 3.1).

3. Send bookings — so the brief knows in advance

When someone books, or cancels, your booking system (directly, or through Zapier or Make) sends:

POST https://app.roundconnect.uk/api/v1/bookings
Authorization: Bearer rck_…            (a key with «can send bookings»)
Content-Type: application/json

{
  "booking_id": "your-booking-id-123",
  "room_id": "<room id from GET /api/v1/studio>",
  "starts_at": "2026-11-03T18:30:00Z",
  "client": { "name": "Anna", "email": "[email protected]" },
  "status": "booked"                    ("cancelled" withdraws it)
}

Sending the same booking_id again updates it — safe to retry.
The client is matched by email (or, the first time, by a unique name of someone who joined by QR).
Before the class, the instructor’s brief lists booked people as “booked, not checked in yet”, and the lines already include them. Check-in on the day still tells us who is really there and on which reformer.

Zapier: trigger “New booking” in your booking app → action Webhooks by Zapier → Custom Request, method POST, the URL and headers above, and the JSON body with your booking fields. A second Zap with “Booking cancelled” sends the same body with "status": "cancelled". Make: the same with the HTTP module.

4. Your AI assistant (MCP)

Round Connect speaks MCP (Streamable HTTP) at https://app.roundconnect.uk/mcp, read-only, with the same key. In Claude Code:

claude mcp add --transport http round-connect https://app.roundconnect.uk/mcp \
  --header "Authorization: Bearer rck_…"

Then ask, for example: “Who has stopped coming in the last month?” or “How full were Tuesday evening classes?”. Tools: get_studio, list_classes, get_class_attendance, list_clients, list_programmes. Any MCP client that lets you set an authorization header works the same way.

5. Webhooks (events out)

Connections → Webhooks: Round Connect posts session.completed, safety.event_created, feedback.hurt_reported (no details), client.level_reached and client.retention_risk to your https address, signed with HMAC-SHA256 (x-rc-signature), with an idempotency-key and retries for up to a day.

Questions: [email protected] · roundconnect.uk