Myhexfit Hexfit API

Name: Hexfit API
Brand: Hexfit API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentHealthcareAppointment Schedulingbearer34 EndpointsREST

For Agents

Onboard clients, build training programs, schedule events, and manage exercise and document data inside a Hexfit account using a bearer token.

Install Jentic One Beta

Connect the Hexfit API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Hexfit 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.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fmyhexfit.com%2Fhexfit" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fmyhexfit.com%2Fhexfit" | 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 Hexfit API.

Onboard new clients and professional accounts via /User/Create/Client and /User/Create/Professional

Build and retrieve training programs through /Training/Build and /Training/GetInfo for program assignment

Manage user metadata flexibly via /User/CreateMeta, /User/SetMeta, and /User/DeleteMeta for custom client fields

GET STARTED

Start building with Hexfit API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Hexfit API for, with concrete tasks.

★ Trainer Client Onboarding

Automate client onboarding for a personal trainer or studio. The integration calls /User/CheckEmail to detect duplicates, then POST /User/Create/Client with the client's profile. Custom intake fields are written via POST /User/CreateMeta. This collapses manual portal entry into a single chained workflow that runs from a public web form.

Call GET /User/CheckEmail with the candidate email, then POST /User/Create/Client with the profile, and POST /User/CreateMeta for the custom 'goal' field.

Programmatic Training Program Build

Generate a personalised training program based on client goals using GET /Training/Build with the client and program parameters. The integration retrieves the exercise bank via /ExercicesBank/GetInfo to validate exercise IDs before requesting the build. The built program is then fetched via /Training/GetInfo for delivery into the client's app.

Call GET /Training/Build for client 9281 with goal 'hypertrophy' and frequency 4x/week, then GET /Training/GetInfo to retrieve the structured program.

Session Scheduling and Events

Schedule training sessions and check-ins for clients via POST /Event/Create. The integration writes session details (client, professional, time, location) and uses POST /Event/SetInfo to update the event when reschedules happen. This decouples Hexfit's calendar from the trainer's portal so events can be created from a chatbot, intake form, or external CRM.

Call POST /Event/Create with the clientId, professionalId, start time, and event type 'PT session', and return the created event ID.

Business Roster Reporting

Surface a studio's full roster of clients and employees by calling GET /Business/GetClients and GET /Business/GetEmployees. The integration exports data into a BI tool or weekly digest. /Data/GetInfo supplements with operational records, giving studio operators a full view without polling individual user endpoints.

Call GET /Business/GetClients for the businessId and GET /Business/GetEmployees, join the lists, and write a CSV with active flags and creation dates.

AI Agent Fitness Concierge

An AI agent acts as a virtual receptionist for a personal training studio. It searches Jentic for Hexfit operations, loads the client creation, training build, and event schemas, and chains them to onboard a new lead, build their first program, and schedule an intro session. Jentic isolates the bearer token so the agent never holds the studio's secret.

Search Jentic for 'onboard a fitness client and book a session', execute POST /User/Create/Client, GET /Training/Build, and POST /Event/Create in sequence.

Key Endpoints

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

METHOD

PATH

DESCRIPTION

POST

/User/Create/Client

Create a new client account

POST

/User/Create/Professional

Create a new professional account

GET

/User/GetInfo

Retrieve a user profile

GET

/Training/Build

Build a personalised training program

GET

/Training/GetInfo

Retrieve a built training program

POST

/Event/Create

Schedule a new training event

GET

/Business/GetClients

List clients for a business

GET

/ExercicesBank/GetInfo/

Read the exercise bank

POST

/User/Create/Client

Create a new client account

POST

/User/Create/Professional

Create a new professional account

GET

/User/GetInfo

Retrieve a user profile

GET

/Training/Build

Build a personalised training program

GET

/Training/GetInfo

Retrieve a built training program

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Hexfit API by hand means learning its bearer auth, choosing between the staging and production host, and chaining client onboarding into training-program build yourself. Through Jentic you install once, import the Hexfit API from the API Directory, store the token once, and your agent calls it.

Permission scoping

Client, training, and event targets travel in the request body, so limit the agent to the operations it needs, such as onboarding a client or building a training program. You choose which operations are in scope, so a write call like creating a professional is not included unless you add it.

Credential isolation

Your Hexfit bearer token is stored once, encrypted, by your own Jentic One instance and injected into the Authorization header at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'onboard a fitness client' or 'build a training program', and Jentic returns the matching Hexfit operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Hexfit API through Jentic.

Why is there no official OpenAPI spec for Hexfit API?

Hexfit does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Hexfit 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 Hexfit API use?

The Hexfit API uses HTTP bearer authentication on most endpoints, plus OAuth2 flows under /oauth2/authorize and /oauth2/token for app-level integrations. Through Jentic, both the bearer token and OAuth2 client credentials are stored encrypted in the vault and injected at execution time.

Can I build a training program with the Hexfit API?

Yes. Call GET /Training/Build with the client and program parameters to generate a program, then GET /Training/GetInfo to retrieve the structured output. Validate exercise selection against /ExercicesBank/GetInfo before requesting the build to avoid invalid exercise IDs.

How do I onboard a new client through Jentic?

Search Jentic for 'create a Hexfit client', load the POST /User/Create/Client schema, and execute it with the client's profile fields. Optionally chain POST /User/CreateMeta to attach custom intake metadata to the new client record in the same agent run.

Does the Hexfit API have a staging environment?

Yes. The spec defines two servers: staging.api.myhexfit.com/v2 for development and api.myhexfit.com/v2 for production. Build and test against staging, then swap the base URL to go live - the operation surface is identical across both.

What are the rate limits for the Hexfit API?

The published spec does not document rate limits. Treat the API as throttled in production, implement exponential backoff on 429 responses, and contact Hexfit support for studio-level limits before running bulk client imports.

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

Yes. Because Jentic One is self-hosted, you decide which Hexfit operations your agent may call, so you can allow client onboarding through POST /User/Create/Client or training-program build through GET /Training/Build while leaving everything else out of scope. Client, training, and event targets travel in the request body, so a write call such as creating a professional via POST /User/Create/Professional is only reachable if you add it to the agent's allowed operations. Your own rules also govern which stored credential the agent uses, keeping its access limited to exactly the calls you have approved.

Myhexfit Hexfit API

Connect the Hexfit API to your agent

Capabilities

Start building with Hexfit API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs