Keys and authentication
Every request carries a key in the Authorization header:
curl https://api.garmo.studio/v1/account \
-H "Authorization: Bearer gm_live_…"Live and test keys
- Live keys (
gm_live_…) make real images and spend API credits. They need an API pack on the account. - Test keys (
gm_test_…) are free. Every endpoint works and validates parameters and images exactly like live, but nothing is sent to an image model: each output is your own input photo, ready in a few seconds. Use them in development and CI. Test jobs and the files sent with a test key are deleted after 24 hours.
Jobs belong to the mode of the key that made them: a live key does not see test jobs and the other way round. Test jobs do not appear in the Studio library.
Creating and revoking keys
Keys are made on Developers › API in Garmo Studio, up to 10 live and 5 test keys per account. A key is shown once at creation; Garmo keeps only a hash of it. Revoke a key there the moment it may have leaked: requests with it then get 401 invalid_api_key.
Keep keys on the server
A key spends your credits. Call the API from your server, a serverless function or a workflow tool, never from a browser or a mobile app. The API sends no CORS headers for that reason.
Authentication errors
401 invalid_api_key: missing, unknown or revoked key.403 api_not_enabled: a live key on an account without an API pack.403 key_suspendedoraccount_suspended: contact support@garmo.studio.




