> For the complete documentation index, see [llms.txt](https://docs.tryterra.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tryterra.co/faq/help-topics/data-api-sdk/extra-features-scores-graphs-teams-nutrition-cgm/teams-api-beta.md).

# Is the Teams API available and how do I use it?

The [Teams API](https://docs.tryterra.co/teams-api/getting-started) is in **semi-public beta** ahead of full release, and is webhook-based.

It covers team-sports and clinical systems (dynamometers, force meters, player-tracking) where one person, a coach or clinician, views data for a whole group. The third-party system's API keys are owned by that coach/clinician/customer, rather than each end user.

The flow:

{% stepper %}
{% step %}
Create a coach.
{% endstep %}

{% step %}
Receive athletes registered under that coach.
{% endstep %}

{% step %}
Update athletes with your `reference_id` mapping.
{% endstep %}

{% step %}
Receive activity sessions and tests over time.
{% endstep %}
{% endstepper %}

Beta [endpoint docs](https://docs.tryterra.co/reference/teams-api/api-endpoints) and the raw OpenAPI spec are available. Access requires credentials from a [supported team-sports data provider](https://docs.tryterra.co/reference/teams-api/supported-integrations).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.tryterra.co/faq/help-topics/data-api-sdk/extra-features-scores-graphs-teams-nutrition-cgm/teams-api-beta.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.