Authentication

All API requests are authenticated with one header: your API key. A key belongs to one store, so that is all Printago needs to know which store you are working in.

Getting an API Key

API keys are managed in your Printago dashboard under Settings → Integrations → API Keys, or directly at app.printago.io/api.

When you create a new API key, it will only be shown once. Store it securely as it grants full access to your account data and printers.

Required Headers

authorization

Your API key, prefixed with ApiKey

x-printago-storeid was required in the past. It is no longer needed, because your key names its store. If you still send it, it is checked against your key's store, and a value that does not match returns 401.

Example Request

HTTP Headers

authorization: ApiKey pk_live_abc123...

Error Responses

401 Unauthorized

Missing or invalid API key; Store ID mismatch

403 Forbidden

The key is valid but lacks the permission the endpoint requires

429 Too Many Requests

Rate limit exceeded; back off and retry (see below)

See Errors for the response body format.

Rate Limits

Rate limits are enforced at Printago's edge, before a request reaches the API:

API key requests

600 / hour

Counted per store ID (the x-printago-storeid header), so every key for the same store shares one budget.

Unauthenticated requests

500 / minute

Requests without an API key and store ID header, counted per client IP address. Exceeding it bans that IP for 60 minutes.

Requests over a limit fail with HTTP 429. The response has no Retry-After header, so on a 429 back off exponentially (for example 1s, 2s, 4s, 8s… with some random jitter, up to a few minutes) instead of retrying straight away. Spreading work out, using webhooks or MQTT instead of polling, and fetching many records per list request all keep you well inside the hourly budget.

If the rate limits are too restrictive for your use case, please contact us to discuss.