> ## Documentation Index
> Fetch the complete documentation index at: https://docs.nexrex.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Developer API

> Programmatic, org-scoped access to your organization's training data.

The NexRex Developer API gives coaching organizations programmatic access to the
training data they already manage in NexRex — athletes, activities, training
plans, groups — plus the ability to run **data exports** on demand. It is the
API behind our [Data Portability Promise](https://nexrex.ai/data-portability):
your training data is yours to read, move, and build on.

<Note>
  This is a **read-and-export** API. It does not modify athlete data. Writes
  (proposing workout adjustments or plan revisions) are handled through NexRex's
  mediated coach workflows, not this API.
</Note>

## Who it's for

Developers building tools on top of a coaching organization's data — analytics
dashboards, roster reports, migrations to or from other platforms, or AI
assistants that summarize team status. Access is **org-scoped**: a key issued by
an organization can only ever see that organization's data.

## Base URL

```
https://api.nexrex.ai/api/v1/developer/v1
```

Every path in this reference is relative to that base. For example,
`GET /org` is `https://api.nexrex.ai/api/v1/developer/v1/org`.

## Versioning

The API is versioned by date. The current version is **`2026-07-01`**, returned
on every response in the `X-API-Version` header. Breaking changes are announced
at least 90 days in advance — see the [Deprecation policy](/api-reference/deprecation-policy).

## The machine-readable spec

The full contract is published as an OpenAPI 3.1 document and served live:

```
GET https://api.nexrex.ai/api/v1/developer/v1/openapi.json
```

Point your client generator, Postman, or IDE at that URL to generate types and
requests directly.

## Get started

<Steps>
  <Step title="Enable the Developer API">
    Developer API access is part of the **Club** plan. If your organization is on
    Club, the feature is already enabled.
  </Step>

  <Step title="Create an API key">
    A head coach or org admin creates a key under **Settings → Security** in the
    Coach Console. See [Authentication](/api-reference/authentication).
  </Step>

  <Step title="Choose scopes and an expiry">
    Grant only the [scopes](/api-reference/scopes) your integration needs, and set
    an expiry (90 days is the default).
  </Step>

  <Step title="Make your first call">
    ```bash theme={null}
    curl https://api.nexrex.ai/api/v1/developer/v1/org \
      -H "Authorization: Bearer nrx_prod_your_key_here"
    ```
  </Step>
</Steps>

<CardGroup cols={2}>
  <Card title="Authentication" icon="key" href="/api-reference/authentication">
    Create keys, choose an expiry, and send them on requests.
  </Card>

  <Card title="Scopes" icon="lock" href="/api-reference/scopes">
    The seven permissions and how legacy keys map to them.
  </Card>

  <Card title="Exports" icon="file-export" href="/api-reference/exports">
    Run asynchronous data exports and download the results.
  </Card>

  <Card title="Errors" icon="triangle-exclamation" href="/api-reference/errors">
    The error envelope and every machine-readable code.
  </Card>
</CardGroup>