Saltar al contenido principal

Developer documentation

NextFit + Zapier API

Production documentation for connecting a NextFit gym to Zapier using OAuth 2.0. Each connection is isolated to the gym that authorized it.

Authentication

This integration uses OAuth 2.0 Authorization Code flow. Users authenticate with a verified NextFit owner account. Zapier sends the resulting access token as a Bearer token.

Production base URL: https://gymproject-production-1240.up.railway.app

Token type: Bearer

OAuth endpoints

GET/integrations/zapier/oauth/authorize

Starts authorization and returns an authorization code to Zapier.

POST/integrations/zapier/oauth/token

Exchanges an authorization code or refresh token for OAuth tokens.

POST/integrations/zapier/oauth/revoke

Revokes an access token or refresh token.

GET/integrations/zapier/oauth/me

Returns the authenticated NextFit account and gym name for the connection label.

Polling triggers

All trigger endpoints use GET and require the OAuth Bearer token. They return records only from the gym associated with that OAuth connection. No gym ID is accepted from Zapier.

GET/integrations/zapier/oauth/triggers/members

Returns up to 50 recent members.

GET/integrations/zapier/oauth/triggers/leads

Returns up to 50 recent leads.

GET/integrations/zapier/oauth/triggers/campaigns

Returns up to 50 recent campaigns.

Response examples

[
  {
    "id": "resource-id",
    "name": "Example",
    "createdAt": "2026-10-03T19:00:00.000Z"
  }
]

Member, lead, and campaign responses include the resource fields configured in the Zapier trigger. Errors use standard HTTP status codes and a JSON message.

Data isolation

OAuth tokens are stored securely and resolve to one gym. Trigger queries use that gym context server-side, so users cannot select or submit another gym ID through Zapier.