TeamUp REST API

Name: TeamUp REST API
Brand: TeamUp REST API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentProductivityCalendar Schedulingbearer461 EndpointsREST

For Agents

Manage fitness studio bookings, attendances, customers, classes, memberships, payments, and communications across the TeamUp platform.

Connect the TeamUp REST API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the TeamUp REST API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with TeamUp REST API.

Book a customer into a class or appointment and record their attendance

Sell or renew a membership and apply discounts or vouchers at checkout

Charge a customer card on file or process a refund against an existing payment

Manage class schedules, instructors, locations, and offering types

GET STARTED

Start building with TeamUp REST API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for TeamUp REST API, keeping it validated and agent-ready. The TeamUp REST API powers fitness, wellness, and class-based businesses with 461 endpoints covering bookings, attendances, classes, customers, payments, memberships, instructors, locations, communications, and reporting. Authentication uses bearer JWT or token authentication issued from the TeamUp business dashboard. The surface includes operational endpoints for daily front-of-house work and analytics endpoints for owner-level reporting.

Use Cases

Patterns agents use TeamUp REST API for, with concrete tasks.

★ Studio Front-of-House Automation

Drive the daily check-in flow at a fitness studio: list today's classes, mark attendances, sell drop-ins or class packs, and accept payment. The /attendances and /availability_schedule_offering_types endpoints power the front desk app, while /auth/password_login and refresh-token flows keep staff sessions secure across shifts.

Mark attendance for customer id 7788 in class id 33221, charge their saved card for 18.00 USD if no class pack credit is available, and email a receipt.

Membership Lifecycle Management

Sell, renew, freeze, and cancel memberships through dedicated endpoints, including discount and voucher application at the point of sale. Recurring membership renewals run on the TeamUp side and surface via the API for downstream reconciliation, while churn signals can be pulled into the owner's BI tool for retention analysis.

Sell membership product 'Unlimited-Monthly' to customer id 5544 starting today, apply voucher 'WELCOME10', and confirm the first payment was successful.

Marketing and Customer Communications

Use the communications endpoints to send class reminders, win-back campaigns, and transactional receipts to customers and leads. Combined with attendance and membership history, the studio can target lapsed members or upsell premium offerings without leaving TeamUp.

Send a personalised win-back email to all customers whose last attendance was more than 30 days ago and offer a 20% discount voucher.

AI Agent Owner Reporting

An AI agent runs nightly to fetch business advisor reports and AI content from /ai/business_advisor_reports, summarises key trends, and emails the owner. Through Jentic, the agent discovers the right endpoint by intent and uses a vault-stored token, so the studio's TeamUp credentials never appear in the agent's prompt.

Generate a business advisor report for last month, fetch its content via /ai/business_advisor_reports/{id}/content, and email a 5-bullet summary to the owner.

Key Endpoints

461 endpoints — jentic publishes the only available openapi specification for teamup rest api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/auth/password_login

POST

/auth/refresh_access_token

Refresh an expired access token

GET

/attendances

List class attendances

POST

/attendances

Create an attendance for a customer

GET

/applications

List integration applications

GET

/ai/business_advisor_reports

List AI business advisor reports

GET

/availability_schedule_offering_types

List availability schedule offering types

POST

/auth/password_login

POST

/auth/refresh_access_token

Refresh an expired access token

GET

/attendances

List class attendances

POST

/attendances

Create an attendance for a customer

GET

/applications

List integration applications

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

TeamUp credentials and refresh tokens are stored encrypted in the Jentic vault (MAXsystem). Agents call endpoints with a scoped token reference and Jentic refreshes the access token automatically, so the agent never sees raw passwords or long-lived tokens.

Intent-based discovery

Agents search by intent across the 461-endpoint surface and Jentic returns the right TeamUp operation with input schema, so the agent does not have to scan a long resource list to find the right call.

Time to first call

Direct TeamUp integration: 7-14 days for auth, multi-resource workflows, and refresh handling. Through Jentic: under 1 hour to call a specific operation.

FAQs

Specific to using TeamUp REST API through Jentic.

Why is there no official OpenAPI spec for TeamUp REST API?

TeamUp does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call TeamUp REST API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the TeamUp REST API use?

Either JWT bearer authentication or token authentication, sent in the Authorization header. Tokens are obtained from /auth/password_login (with optional /auth/two_factor flows) and refreshed via /auth/refresh_access_token. Through Jentic, the credentials and refresh token live in the encrypted vault.

Can I book a customer into a class with the TeamUp API?

Yes. POST /attendances with the customer id and the class instance id. The endpoint deducts a class pass credit if available, otherwise it returns the price to charge. The DELETE counterpart cancels the attendance and refunds the credit per the studio's policy.

How do I sell or renew a membership with the TeamUp REST API?

TeamUp's membership endpoints accept the customer id, membership product id, optional voucher code, and start date. The API returns the new membership object and the resulting payment record, which can then be charged against a saved card or handled in person.

How do I integrate the TeamUp REST API with an AI agent through Jentic?

Run pip install jentic, search 'book a class attendance' to find POST /attendances, load the schema, and execute. For owner reporting, search 'business advisor report' to find the AI endpoints. Get started at https://app.jentic.com/sign-up.

TeamUp REST API

Connect the TeamUp REST API to your agent

Capabilities

Start building with TeamUp REST API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs