1FIT Zapier Webhook API

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 your Jentic One instance 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.

Can I limit what my agent is allowed to do with the 1FIT Zapier Webhook API?

Yes. Because you run Jentic One yourself, your own rules decide which of the API's three operations the agent may call and which bearer token it uses. You can allow just the read-only checks, such as registering or testing a Zapier connection, while withholding live webhook delivery to POST /api/integrations/webhooks/zapier/{endpoint} for client, prospect, activity, check-in, and workout events. Only the operations you pick can run, so the agent cannot post events into a trainer's 1FIT account unless you grant that.