Saltar para o conteúdo principal

Base URL

All API requests are made to:

Authentication

Every request requires an API key passed as a Bearer token in the Authorization header:
API keys start with the hyze_ prefix. You can create and manage keys from the Dashboard or via the API Keys endpoints.
Session cookie auth is also supported. If you’re calling from the browser while logged in, your session cookie will authenticate the request automatically.

Conventions

Content type

All request and response bodies are application/json, except for file uploads which use multipart/form-data.

Response envelope

All endpoints return a consistent envelope:
When an error occurs:

Rate limiting

Some endpoints enforce rate limits and will return 429 Too Many Requests with a Retry-After header. Published apps are also rate limited on the public proxy (per IP and per host). See Rate limits for defaults and how this differs from API limits.

Workspaces

Most endpoints require an active workspace. Workspaces are set via the web dashboard or via POST /api/auth/set-active-organization before using the API key. When using an API key without a session cookie, workspace-scoped endpoints require you to pass a workspaceId query parameter (where supported) or maintain an active workspace session.

Examples

Language=bash
Language=JavaScript
Language=Python
Última modificação em 17 de julho de 2026