1FIT Zapier Webhook API

Name: 1FIT Zapier Webhook API API
Brand: 1FIT Zapier Webhook API
Availability: InStock

★ Only Publicly Available SpecHR recruitingEmployee Managementbearer3 EndpointsREST

For Agents

Register a Zapier connection for a 1FIT trainer account and post client, prospect, check-in, activity, and workout events into 1FIT through user-scoped webhook URLs.

Quickstart

Get started with 1FIT Zapier Webhook API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"send a client created event to 1FIT"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with 1FIT Zapier Webhook API API.

Validate that an existing Zapier connection and its credentials are still working

Post a client.created or prospect.created event with name, email, mobile, and check-in cadence into 1FIT

Send activity.logged events with duration, distance, heart rate, and calories from a connected fitness tool

GET STARTED

Start building with 1FIT Zapier Webhook API API

Explore with Jentic

View OpenAPI Spec

Jentic publishes the only available OpenAPI specification for 1FIT Zapier Webhook API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for 1FIT Zapier Webhook API, keeping it validated and agent-ready. The 1FIT Zapier Webhook API connects external automation tools to a personal trainer's 1FIT account, letting third-party systems register a Zapier connection, validate it, and post lifecycle events into 1FIT through a user-scoped webhook URL. It accepts a fixed set of event types covering client and prospect creation, client activation and deletion, check-in submissions, activity logs, and completed workouts. Authentication is a JWT bearer token, and every event uses a shared envelope with an event name, timestamp, and event-specific data block.

Use Cases

Patterns agents use 1FIT Zapier Webhook API API for, with concrete tasks.

★ Sync new clients from a sales tool into 1FIT

When a personal trainer closes a deal in an external CRM, an automation can post a client.created event to the 1FIT Zapier webhook with first name, last name, email, mobile, and check-in cadence. 1FIT receives the payload via the user-scoped webhook URL returned at connection setup and creates the client record without manual entry. This removes the duplicate data work between sales pipelines and the trainer's coaching platform.

Call POST /api/integrations/webhooks/zapier/{endpoint} with event=client.created and a CreateClientData payload containing first_name, last_name, email, mobile, and checkin_frequency=weekly

Forward fitness tracker activity into 1FIT

When a client completes a session in a third-party fitness app, an automation can send an activity.logged event to 1FIT with the activity name, duration in seconds, distance in meters, average heart rate, and calories. 1FIT uses the user's webhook endpoint to attribute the activity to the right client by email or mobile. This lets trainers review external workout data inside 1FIT alongside their own check-ins.

Call POST /api/integrations/webhooks/zapier/{endpoint} with event=activity.logged and an ActivityLoggedData payload containing email, activity, duration, distance, hr, and calories

Capture check-in submissions from external forms

When a client submits a weekly check-in through an external form tool, an automation can post a checkin.submitted event to 1FIT with the client's contact details and submission timestamp. 1FIT records the check-in against the matching client so the trainer sees it in their normal check-in review flow. This is useful when a coach prefers a form builder for the questionnaire itself but wants the response logged in 1FIT.

Call POST /api/integrations/webhooks/zapier/{endpoint} with event=checkin.submitted and a CheckinSubmittedData payload containing email, requested_at, and submitted_at

AI agent integration via Jentic

An AI assistant for a personal training business can use the 1FIT Zapier Webhook API through Jentic to register a connection on behalf of a trainer and then route client lifecycle events from upstream tools into 1FIT. The agent searches Jentic for an intent like sync a client into 1FIT, loads the schema for receiveZapierWebhook, and posts each event with the correct envelope. The bearer token is stored in the Jentic vault, so the agent never sees the raw JWT.

Search Jentic for sync a client lifecycle event into 1FIT, load the receiveZapierWebhook schema, and execute a POST to /api/integrations/webhooks/zapier/{endpoint} with event=client.activated

Key Endpoints

3 endpoints — jentic publishes the only available openapi specification for 1fit zapier webhook api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/api/integrations/connections/zapier/setup

POST

/api/integrations/connections/zapier/test

Validate that a Zapier connection is still working

POST

/api/integrations/webhooks/zapier/{endpoint}

Receive a Zapier event (client, prospect, activity, check-in, workout)

POST

/api/integrations/connections/zapier/setup

POST

/api/integrations/connections/zapier/test

Validate that a Zapier connection is still working

POST

/api/integrations/webhooks/zapier/{endpoint}

Receive a Zapier event (client, prospect, activity, check-in, workout)

Why though Jentic?

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

Credential isolation

The 1FIT JWT bearer token is stored encrypted in the Jentic vault and injected only at execution time. Agents call the API by name and never see the raw token, which removes the risk of leaking trainer credentials through logs or prompts.

Intent-based discovery

Agents search Jentic with intents like sync a client into 1FIT or post a workout completed event, and Jentic returns the matching operation (setupZapierConnection, testZapierConnection, or receiveZapierWebhook) with its WebhookEnvelope schema so the agent can build a valid payload without reading docs.

Time to first call

Direct integration with the 1FIT Zapier endpoints: 1-2 days to handle setup, JWT refresh, the seven event payload variants, and retry logic. Through Jentic: under 30 minutes — search, load the schema, execute the call.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Zapier Natural Language Actions

Zapier's automation layer that fires the events this 1FIT API is designed to receive.

Use Zapier NLA to trigger the upstream automation (form submission, CRM update, fitness tracker sync) and route the result into the 1FIT webhook endpoint.

Complementary

HubSpot CRM Contacts

Source of new client and prospect records that can be forwarded into 1FIT.

Choose HubSpot Contacts to read or create the customer record first, then send a client.created or prospect.created event to 1FIT.

Alternative

Mindbody Public API

Broader fitness business platform covering booking, payments, and client records.

Use Mindbody when a trainer needs scheduling, point-of-sale, and class management — 1FIT focuses on coaching and check-ins.

Complementary

Calendly API

Books the consultation that becomes a 1FIT prospect.

Use Calendly to schedule the discovery call, then forward a prospect.created event to 1FIT once the call is booked.

FAQs

Specific to using 1FIT Zapier Webhook API API through Jentic.

Why is there no official OpenAPI spec for 1FIT Zapier Webhook API?

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

The API uses HTTP bearer authentication with a JWT. Every request to /api/integrations/connections/zapier/setup, /api/integrations/connections/zapier/test, and /api/integrations/webhooks/zapier/{endpoint} requires an Authorization: Bearer <jwt> header. When called through Jentic, the JWT is stored in the Jentic vault and injected at execution time so the agent never handles the raw token.

Can I post completed workouts and activities to 1FIT through this API?

Yes. POST /api/integrations/webhooks/zapier/{endpoint} accepts event=workout.completed with a WorkoutCompletedData payload (workout name, rating, started_at, completed_at, duration, exercises) and event=activity.logged with an ActivityLoggedData payload (activity, duration, distance, hr, calories). Both are routed to the trainer who owns the {endpoint} identifier returned at setup.

What event types does the webhook endpoint accept?

The WebhookEnvelope schema enumerates seven event types: activity.logged, checkin.submitted, client.activated, client.created, client.deleted, prospect.created, and workout.completed. Any other event value is rejected with a 400 response.

What are the rate limits for the 1FIT Zapier Webhook API?

The OpenAPI specification does not define explicit rate limits. Treat the webhook endpoint as a per-user ingest channel and batch unrelated events on the client side. If 1FIT introduces limits in the future, retry on 429 responses with exponential backoff.

How do I register a Zapier connection for 1FIT through Jentic?

Run pip install jentic, then search for register a 1FIT zapier connection. Jentic returns the setupZapierConnection operation; load its schema and execute it with a ConnectionSetupRequest containing key_id, secret, and endpoint_id. The 200 response includes the user-scoped endpoint value to use in subsequent webhook calls.