Getting Started
Intro
We empower partners and Club Management Systems (CMS) to seamlessly control the integration setup process. When a partner integrates with us and selects their system, we automatically store the necessary information for integration. In cases where manual intervention is required, we liaise directly with the CMS to obtain all necessary data. This manual step may take longer and involve manual interventions. The Integration Setup API is designed to automate this process, empowering both the partner and CMS. The API notifies the CMS when a new partner selects their system, allowing the CMS to manage the partner's webhooks and access the list of partners associated with it. This streamlined process ensures the quick availability of partners on the Wellhub app.
Authentication
Wellhub will provide you with the Authentication Token which will be used as the Authorization Bearer Token for authentication when calling our Integration Setup API. You can use the same token if you already have one to access the Booking API. Every API interaction must use the Wellhub API Key as an authentication Bearer token, otherwise, the standard HTTP status code in the response will be 401 Unauthorized
. In practical terms, every request made is expected to define an Authentication header, and its value is expected to be something like Bearer {{Wellhub API Key}}
.
Integration Setup API request example
curl1curl -X GET "{{integration-setup-api-url}}/v1/systems/gyms/000000/webhooks" \2 -H "accept: application/json" \3 -H "Authorization: Bearer {{Wellhub Auth Token}}"
Environments
All operations related to integration setup use the base URL api.partners-integrations
.
Production: https://api.partners-integrations.gympass.com
Responses
Code | Description |
---|---|
2XX | The request was successfully processed. |
4XX | Error detected in the request that the server cannot process the request. For example: the payload is poorly formatted. |
401 | Unauthorized. Missing or wrong access token. |
5XX | Internal server error. |