APIs
Where Keboola's public APIs are documented, one portal per stack, how to authenticate, and how to find the endpoint of each service in your own stack.
Every Keboola service has a public API. The documentation portal at api.keboola.com covers the US Virginia AWS stack; every other stack has its own portal on the same pattern, and a token only works against the portal of its own stack:
| Stack | API documentation portal |
|---|---|
| US Virginia AWS | api.keboola.com |
| US Virginia GCP | api.us-east4.gcp.keboola.com |
| EU Frankfurt AWS | api.eu-central-1.keboola.com |
| EU Ireland Azure | api.north-europe.azure.keboola.com |
| EU Frankfurt GCP | api.europe-west3.gcp.keboola.com |
Most calls take a Storage API token in the X-StorageApi-Token header and
exchange JSON. Each service runs on its own host inside the stack, such as queue.keboola.com or
encryption.eu-central-1.keboola.com. Use the hosts of your own stack: a token-authenticated call to
another stack’s host answers with an invalid-token error.
The authoritative list of service URLs for your stack is the Storage API
index call, GET /v2/storage (no token needed), in its services array. For tooling and AI agents, each portal also publishes a machine-readable index at
https://api.<stack domain>/apis.json. It lists the services the portal documents, not every service in the
stack, each with its apiUrl and a link to its OpenAPI specification; use apiUrl from the index as the base
URL rather than the servers inside the spec, and take openApiSpecUrl exactly as given. A Postman collection
holds sample requests; for a worked call, see running a job through the API.