DevelopersDocsStart
Authentication
Send a bearer API key from your server. Keys are admin-issued, revocable, and not safe in a browser.
Every /api/v1 route and the MCP endpoint require a bearer key. Documentation pages are public. The retrieval routes are not.
Authorization: Bearer $PROBLEMS_API_KEY- The secret matches
pcc_followed by the issued token. A hash is what Problems.cc stores. - Missing header: 401
missing_api_key. A header that is not a bearer key of that form: 401invalid_api_key. - Revoked keys return 401
revoked_api_key. Disabled keys return 403disabled_api_key. - REST and MCP share the same key, allowlist, and quotas. Revoking the key stops both.
- Treat the secret like a password. Rotate it by asking an admin to revoke it and issue another.
A browser call exposes the key to anyone who can read the page. Call the API from your backend, or from an MCP client that can attach a static Authorization header, and send your users the statement, not the key.