Data Hub APIs let authorized partners retrieve EGYM data for external reporting, business intelligence, customer success, and member management workflows.
Availability
- Enterprise Pack only: Data Hub is available exclusively to customers with the EGYM Enterprise Pack.
- Pilot mode: Data Hub is currently in pilot. Functionality and API contracts may change, and access is granted on a case-by-case basis. Contact your EGYM representative to participate.
This section contains guides and the API reference for exporting analytics, workout, assessment, and measurement data for an EGYM gym location.
Data Hub is designed for server-to-server integrations that need to process EGYM data in external reporting, business intelligence, or customer success systems.
The API supports two export modes:
- Synchronous exports return paginated JSON directly in the API response. Use these endpoints for regular incremental syncs: weekly analytics can cover up to 365 days, while event data exports can go back only one month.
- Asynchronous exports create a background job and return a download URL when the file is ready. Use async exports for historical event data and larger backfills. Async exports can go back up to one year, but not beyond that.
Before you start
- Do not fetch daily data before 09:00 UTC: Data processing for the previous day completes overnight. If you schedule daily exports, run them at 09:00 UTC or later to make sure all records are processed.
- All times are in UTC: Request parameters such as
startDateandendDateare interpreted as UTC calendar days, and timestamp fields in responses (for example,eventTimestamp) are returned in UTC using the ISO 8601Zsuffix. - Event exports require member opt-in: Event exports (Smart Strength workouts, Smart Strength assessments, flexibility measurements, and body measurements) only include records for members who have opted in to health data and consumer-to-business (C2B) sharing. Weekly analytics metrics are aggregated and are not subject to this filter.
- Always store externalAccountId for deletions: Whenever you fetch user-related data, save the
externalAccountIdfield in your database. When a member opts out,GET /api/v1/data/opted-out-usersreturns only theirexternalAccountId(no names, emails, or phone numbers). You must use this stored ID to map back to your database and delete that user's records.
To stay compliant with GDPR and other data protection regulations, follow this three-step lifecycle:
- Store the ID when fetching: Every workout, assessment, and measurement export includes an
externalAccountId. Save this ID alongside the member's data in your database or data warehouse. - Check for opt-outs: Call
GET /api/v1/data/opted-out-userson a regular schedule. - Map and delete: The opt-out endpoint returns only
externalAccountIdandlastSeenAt; names and emails are omitted. Use that ID to look up the member in your database and delete all previously exported data associated with them.
If your system does not save externalAccountId during the initial export, you will not have a way to match opted-out users to the data you stored.
| Data set | Export type | Recommended mode |
|---|---|---|
| Weekly analytics metrics | Not applicable | Synchronous |
| Smart Strength workouts | SMART_STRENGTH_WORKOUTS | Synchronous for recent data, asynchronous for historical data |
| Smart Strength assessments | SMART_STRENGTH_ASSESSMENTS | Synchronous for recent data, asynchronous for historical data |
| Flexibility measurements | FLEXIBILITY_MEASUREMENTS | Synchronous for recent data, asynchronous for historical data |
| Body measurements | BODY_MEASUREMENTS | Synchronous for recent data, asynchronous for historical data |