Creating API keys

Keys live in Settings → Developer. Pick scopes deliberately — read, download, collections:write — and revoke from the same page.

Create a key

1. Open Settings → Developer.
2. Under API keys, name the key and choose scopes: read (search and metadata), download (licence-checked downloads), collections:write (create and edit shot lists).
3. Copy the key when it is shown — for security it is stored hashed, so it cannot be displayed again. Lost it? Revoke and create a new one.

Using a key

Send it as a bearer token: Authorization: Bearer bv_live_…. The REST API base and endpoint reference are on the Developers page, with an OpenAPI spec at /api/v1/openapi.json. Responses carry X-RateLimit headers; quotas follow your plan (Free 200 requests/hour, Pro 5,000/hour).

Keys vs OAuth

Keys suit scripts and file-based tools (Cursor, Claude Code). Connector UIs like ChatGPT and Claude never ask for a key — they use OAuth sign-in instead; see the connector guides in this category.