canonical: https://jentic.com/apis/pike13.com/pike13

# Pike13 API

Jentic publishes the only available OpenAPI specification for Pike13 API, keeping it validated and agent-ready. Pike13 API manages fitness studio and class scheduling operations including appointment bookings, event management, people records, custom fields, and business account administration. The API supports finding available time slots, creating bookings, managing event occurrences, and handling multi-location franchise configurations.

## For AI agents

Manage fitness studio scheduling, book appointments, query available time slots, and administer people and event records for class-based businesses.

## Scope

Does not handle payment processing, membership billing, or marketing campaigns - use for class scheduling and booking management only.

## Capabilities

- Find available appointment slots for specific services and instructors
- Create and manage class bookings with participant details
- List and filter events and their recurring occurrences
- Administer people records including staff and client profiles
- Configure custom fields for business-specific data collection
- Manage multi-location franchise configurations and branding

## Use cases

### Class Availability and Booking

Query available appointment slots for fitness classes and services, then create bookings for clients. The Pike13 API returns time slots based on service type, instructor availability, and location, enabling automated scheduling for yoga studios, gyms, and wellness centers.

Example prompt: Query available slots for service ID 42 on 2026-06-20 and create a booking for the first available time

### Event and Schedule Management

Manage recurring classes, workshops, and special events through the Pike13 API. The `/front/events` and `/front/event_occurrences` endpoints handle scheduling, capacity tracking, and occurrence listing, supporting studios that run weekly classes with varying instructors and rooms.

Example prompt: List all event occurrences for the current week and retrieve participant counts for event ID 101

### Client and Staff Administration

Maintain people records for clients and staff through the Pike13 API. The `/account/people` endpoint supports profile management, custom field data, and business association, enabling studios to track membership details, attendance history, and instructor qualifications.

Example prompt: Retrieve the people list filtered by active membership and export their custom field data

### AI Agent Studio Scheduling

AI agents use the Pike13 API through Jentic to automate class bookings and schedule queries without manual API configuration. Agents search for scheduling operations by intent, load the endpoint schema, and execute calls with Jentic handling Bearer token authentication.

Example prompt: Search Jentic for 'book a fitness class appointment', load the Pike13 bookings endpoint schema, and create a booking for a client

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/front/appointments/{service_id}/available_slots` | Find available time slots for a service |
| POST | `/front/bookings` | Create a new booking |
| GET | `/front/bookings/{id}` | Retrieve a specific booking |
| GET | `/front/events` | List all events |
| GET | `/front/event_occurrences` | List event occurrences |
| GET | `/account/people` | List people records |
| GET | `/front/business` | Retrieve business configuration |
| GET | `/desk/custom_fields` | List custom field definitions |

## Key resources

- **Appointments** — Query available slots and manage scheduled appointments
- **Bookings** — Create, retrieve, and manage class bookings
- **Events** — List events and their recurring occurrences
- **People** — Manage client and staff person records
- **Custom Fields** — Configure business-specific data fields
- **Business** — Access business configuration, branding, and franchise details

## Why Jentic

- **Setup:** Wiring the Pike13 API by hand means handling its OAuth bearer tokens with refresh, resolving your account subdomain into the host, and coding each availability, booking, and event call yourself. Through Jentic you install once, import Pike13 from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Pike13 puts the booking id in the URL path (`/front/bookings/{id}`), so a rule can pin your agent to reading a specific booking. You also choose which operations it may call, so you can allow checking availability and creating a booking while leaving out anything you do not grant.
- **Credential handling:** Your Pike13 OAuth token is stored once, encrypted, by your own Jentic One instance and injected at execution time, with refresh handled for you. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'book a fitness class' or 'find available appointment slots', and Jentic returns the matching Pike13 operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Mindbody API** — Mindbody provides broader wellness business management including payments, retail, and marketing alongside scheduling
- **Acuity Scheduling API** — Acuity Scheduling offers appointment booking for any service business, not limited to fitness
- **Calendly API** — Calendly handles scheduling links and availability sharing for one-on-one meetings complementing Pike13 group classes

## FAQ

### Why is there no official OpenAPI spec for Pike13 API?

Pike13 does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Pike13 API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

### What authentication does the Pike13 API use?

The Pike13 API uses Bearer token authentication via OAuth 2.0. You include your access token in the Authorization header. Through Jentic, these tokens are stored encrypted in your Jentic One instance and refreshed automatically.

### Can I check class availability and book appointments with the Pike13 API?

Yes. Use GET `/front/appointments/{service_id}/available_slots` to query open time slots for a specific service, then POST `/front/bookings` to create a booking in an available slot.

### How do I list upcoming class occurrences through the Pike13 API?

Use GET `/front/event_occurrences` with date range filters to retrieve upcoming class instances. Each occurrence includes the event details, instructor, time, and current participant count.

### How do I book a class through the Pike13 API using Jentic?

Search Jentic for 'book a fitness class appointment', load the `/front/bookings` operation schema, and execute with participant and time slot details. Jentic handles OAuth Bearer token injection and returns the booking confirmation.

### Does the Pike13 API support multi-location studios?

Yes. The `/front/business/franchisees` endpoint lists franchise locations, and the `/account/businesses` endpoint manages multiple business entities. Events and bookings are scoped to specific locations through the subdomain configuration.

### Can I limit what my agent is allowed to do with the Pike13 API?

Yes. Jentic One is self-hosted by you, so your own rules decide which Pike13 operations and credentials the agent may use. You can allow it to check availability with GET `/front/appointments/{service_id}/available_slots` and create a booking with POST `/front/bookings` while withholding anything you have not granted. Because Pike13 puts the booking id in the URL path, you can also pin the agent to reading a single booking through GET `/front/bookings/{id}.`