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

# Quickstart

> Create an organization API key and call the BlitzBoard public API.

Get from zero to a successful `GET /v1/blitz-api/teams` call.

<Steps>
  <Step title="Generate an API key">
    Ask a **BlitzBoard super admin** to create an API key for your organization from the admin panel (admin API `POST /api-keys` with `organizationId`).

    Organization creators and organization admins cannot self-serve API keys.

    The full key (`bb_live_...`) is **shown once** — copy and store it securely.

    <Warning>
      You cannot recover the full key later. If lost, a Blitz super admin must revoke or rotate and issue a new one.
    </Warning>
  </Step>

  <Step title="Call the public API">
    Use the API key as a Bearer token on `/v1/blitz-api` routes. Do **not** use a login JWT here.

    ```bash theme={null}
    curl -X GET 'https://sandbox.blitzboardstats.com/api/v1/blitz-api/teams?skip=0&limit=20' \
      -H 'Accept: application/json' \
      -H 'Authorization: Bearer bb_live_...'
    ```

    Teams are returned only for the organization bound to that key.
  </Step>

  <Step title="Create a team">
    ```bash theme={null}
    curl -X POST 'https://sandbox.blitzboardstats.com/api/v1/blitz-api/teams' \
      -H 'Authorization: Bearer bb_live_...' \
      -H 'Content-Type: application/json' \
      -d '{
        "name": "Falcons U14",
        "footballType": "FLAG",
        "ageGroup": "14U"
      }'
    ```

    `organizationId` is taken from the API key — you do not send it in the body.
  </Step>
</Steps>

## What’s next

<CardGroup cols={2}>
  <Card title="Authentication" href="/authentication" icon="key">
    Key lifecycle, Bearer format, and how JWT vs API key differ.
  </Card>

  <Card title="Create a player" href="/api-reference/endpoint/create-player" icon="user-plus">
    Add a player with an idempotency key.
  </Card>
</CardGroup>