Overview

The Uptivo Club API lets external systems work with club data such as contacts, athletes, trainings, telemetry, subscriptions, classes, challenges, and webhook subscriptions.

It is a REST API. Requests and responses use JSON, standard HTTP methods, and standard HTTP status codes. Integrators access the production API through this public base URL:

https://api-gw.uptivo.fit/club

There is no shared public sandbox. When testing is required, Uptivo can provide a dedicated test club with a limited number of licensed users.

Choose how to integrate

Use the Club API directly when you need full control over request handling, pagination, or a custom synchronization process. If you want to connect Uptivo to another service without building and hosting an API client, start with the Uptivo app for Zapier. It exposes selected Club API events, lookups, and write operations as Zapier triggers, searches, and actions.

Integration model

Every request is associated with both an integration and a club:

1. the Subscription Key identifies the authorized integration;
2. the Club Token (named Club API Key in the API reference) selects the club and grants read-only or read-write access.

See Authentication for the required headers and error responses. When the club license enables Club API, use the club profile’s Club API tab as described in Manage Club API access to obtain and rotate the credentials and inspect webhook delivery health.

Server-to-server only

Build Uptivo integrations on a trusted backend. Never embed the Subscription Key or a Club API Key in a browser application, mobile application, distributed binary, public repository, or client-visible configuration.

If a user-facing application needs Uptivo data, expose only the operations it needs through your own authenticated backend.

Synchronization

Prefer webhooks for change notifications instead of frequent polling. The Club API allows 50 calls per minute and 25,000 calls per 30 days. Integrations should cache stable data, avoid duplicate requests, and use efficient synchronization strategies. Use bulk summaries and bookings instead of issuing one request for every Athlete or Class. See Errors for response headers and 429 Too Many Requests handling.

Versioning

The current endpoints are not prefixed with a version. Additive changes may be introduced without changing the base path; breaking changes use a separate versioned path.

Use of the Club API and this documentation is subject to an agreement with Uptivo s.r.l. See the glossary for definitions of the public resource and credential names.