Skip to main content

​
Base URL and account

Personal and Team keys use the same base URL. Your key selects the asset library, billing account and generation configuration. Teams do not need a separate client or customer-specific hostname. For a test deployment, use the base URL shown in API Access and keep the same /v1 paths. Select Personal or your Team in Gizmo before creating a key. Personal keys use your own assets and credits; Team keys use that Team’s shared assets and credits. The API calls a Team a workspace in some field names and error codes.

​
Available features

Team integrations: use polling for progress. Job event streams, GET /v1/usage and DELETE /v1/assets/{id} currently return 403 workspace_route_unavailable with a Team key. This is an unsupported operation, not an invalid key or a transient error. Do not retry it. Use job/batch polling for progress and Team Billing for the current balance. This guide and the API reference describe one API. The table shows current availability; it does not promise that every operation works with both key types.

​
Authentication

Open API Access in the selected account, create a key, and send it with every request:

​
Verify your key

Keep API keys on your server. Do not embed them in a browser app or commit them to source control. Endpoint reference · Generate your first asset