GET /v1/health) carries a secret API key as a bearer token:
https://api.fastcac.com/v1 in both modes.
Test and live keys
The key decides the mode. Responses look exactly the same in both modes and don’t say which mode
they came from, so code written against a test key runs unchanged with a live key. Objects created
in one mode can’t be seen from the other: a test registration id returns
404 with a live key.
Create, name, roll and revoke keys at developers.fastcac.com.
Developers can manage test keys; live keys need an admin or owner.
Keep keys secret
- Call the API from your server only. Requests from a browser (any request with an
Originheader) are refused, so a key can’t be used from front-end code even by mistake. - Store keys in a secret manager or environment variable, never in source control.
- If a key leaks, revoke it in the dashboard. It stops working at once.
When authentication fails
401