Technical documentation: all current API routes, permissions and examples are available at docs.fitsociety.io. Developers should start with the Public API quickstart.
In this article
The API module of the FITsociety app in Make is meant for advanced scenarios where you want to use a supported Public API route directly. For regular actions, such as updating a member or creating a booking, the available FITsociety action modules are usually simpler.
The API module uses the same connection, the same company and the same permissions as your other modules. It does not give any extra access to data. You need access to the FITsociety app; ask the helpdesk for the private app if it is not yet available in your Make account.
Prepare a read request
Look up the current description of the FITsociety Public API route you want to use.
Check the HTTP method, the path, the required permissions and the input fields.
Add the API module and select the connection with the right company.
For a read request, choose GET and enter the relative path as described in the module help.
Add the required query parameters in the fields meant for them.
Click Run once and check the response body and status code.
A connection test uses the Public API route GET /public/v1/me. Which part of it you enter in the module depends on the base path the module already uses. Follow the module help and don't just enter a full website URL or a path from the coach environment.
Authentication runs through the selected connection. Don't copy an access token from another integration into your scenario. A working connection only gives access to routes for which consent has been granted.
A request that changes data
Only use a write method that both the module and the API route in question support. Provide a stable source identifier in the field meant for it, such as Source operation key. Keep the same value and input when you repeat the same change.
A JSON body must contain valid JSON. Numbers in it use a dot as the decimal separator, for example 172.5. Don't use units or formatted amounts. Date fields without a time use YYYY-MM-DD; timestamps follow the format with time zone that the API requires.
When mapping free text, use a JSON builder so quotes and line breaks are handled correctly. Test write actions with fictional data. A successful request can cause changes, notifications and other normal effects.
Check results and multiple pages
Check in the response body whether the intended record was found or changed. A successful status code alone doesn't tell you whether your scenario processed all the records you wanted.
Don't assume that an API module automatically fetches all pages. Use the pagination that the route and module support, and check whether more results follow. Ask the FITsociety helpdesk for the right documentation if you're not sure which route, permissions or pagination fit your goal.
No connection yet? Read Connect FITsociety to Make.