Quickstart

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

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.

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

Call the public API

Use the API key as a Bearer token on /v1/blitz-api routes. Do not use a login JWT here.

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.

Create a team

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.

What’s next

Authentication

Key lifecycle, Bearer format, and how JWT vs API key differ.

Create a player

Add a player with an idempotency key.

Get started

API reference

What’s next

Authentication

Create a player

​What’s next

Authentication

Create a player

What’s next