Authentication & API Keys
All partner endpoints on Fotobots require an Organization API Key transmitted via an HTTP header.
In-Docs Interactive PlaygroundSANDBOX
Sign in directly on this documentation site to auto-inject your Sandbox API Key into all examples and the API Explorer.
Header Requirement
Include your API Key in the x-api-key header with every request:
POST /openapi/albums/list HTTP/1.1Host: sandbox-api.fotobots.runContent-Type: application/jsonx-api-key: fb_test_YOUR_KEY[!CAUTION] Keep Your API Keys Secret: Never commit API keys to public repositories or expose production keys in client-side mobile/web code. All production API calls should be proxied through your backend server.
Key Types
| Key Prefix | Environment | Purpose | Credit Usage |
|---|---|---|---|
fb_test_... | Sandbox | Integration testing, local development, staging verification. | Free Mock Credits |
fb_live_... | Production | Live marathon events, official runner search platforms. | Deducts Real Credits |
Key Scopes & Permissions
When creating an API Key in the Web Admin, you can select granular permissions:
search:read: Allows querying runner faces and bib numbers. Ideal for frontend timing search apps.photo:upload: Allows generating presigned upload URLs and triggering indexing. Ideal for photographer upload stations.album:manage: Allows creating and editing race albums.
👉 See the Web Admin API Keys Guide for screenshots on how to generate keys.