Kitman Labs

Kitman Labs signs in once for your whole organization with OAuth2 client credentials. No athlete invitations are needed.

Connect Kitman Labs

1. Get a client ID and client secret from your Kitman Labs API settings. Kitman provisions the scopes for each client.
2. Find your numeric organization ID in Admin, then Settings, or ask your Kitman Labs contact.
3. Add the connection and run Test connection.

What it syncs

On by default:

Stream	Contents
Athletes	Athlete roster for the organization
Squads	Squad and team definitions
Positions	Position and role definitions
Fixtures	Match fixtures and scheduled events
Availabilities	Athlete availability records
Injury occurrences	Injury onset and return records per athlete
Injuries	Injury diagnosis records per athlete
Illness occurrences	Illness occurrence records per athlete
Illnesses	Illness diagnosis records per athlete
Chronic issues	Chronic and recurring issue records per athlete
Questionnaires	Wellness questionnaire responses

Off by default: organisation, accounts, roles, questionnaire templates, fixture participants, sessions, session participants, treatment sessions, training variable answers, chronic issue occurrences, conditional answers, integrations, third-party metrics, external entity mappings and medical notes.

Scopes

Each stream needs its own read scope on your client, for example injuries and illnesses need the injuries and illnesses scope. If a stream's scope is not provisioned, ask your Kitman Labs contact to add it before you enable that stream.

Runs take longer

Kitman Labs makes many requests per run, because most data is fetched per athlete. Kitman Labs runs are given a larger time allowance.

Fields

Client ID

The OAuth2 client ID from your Kitman Labs API settings.

Client secret

The OAuth2 client secret from your Kitman Labs API settings. It is stored encrypted.

Organisation ID

Your numeric Kitman Labs organization ID.

Start date

Records are pulled from this date onwards. The default is 1 January 2022.