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

# Introduction

> The endpoints your game server calls, and the callbacks BluMint calls on it.

This reference lists the endpoints and callbacks of the integration that lets your players go from one tournament match to the next without anyone opening a lobby or typing in a score. It uses the words the [guide](https://docs-staging.blumint.com/index.md#words) defines, and [The tournament lifecycle](https://docs-staging.blumint.com/tournament-lifecycle.md) walks through the same calls in the order a tournament makes them.

## Authentication

Send your BluMint API key as the `X-Api-Key` header on every call. You get one key for each environment, and each is bound to your game, so a key works only for your game and only on its own environment ([Before you start](https://docs-staging.blumint.com/before-you-start.md)).

## Servers

The reference lists two servers, staging first. Build and test on staging, and switch to production once your integration works there. Each server address ends in `/api`, so a path shown here as `/tournaments/match/submit` is `/api/tournaments/match/submit` on the environment you call.

## Callbacks

Each registration endpoint, such as `setCreate`, lists the callback BluMint then calls on your game server, with its request and its answers. The decision table for what each answer does is on the guide page each registration links to.

## Try it

Use your staging key in Try it, never your production key. Try it requests pass through Mintlify, and a registration call you make there replaces the URL BluMint calls for your game on that environment.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.