All endpoints in this reference use HTTPS with a bearer API key. The base URL is https://api.bitstudio.ai. Include the full path shown on each endpoint page: for example, POST /v1/images/generate becomes https://api.bitstudio.ai/v1/images/generate.
/v1 identifies the API version; it is separate from model names such as V6. Endpoints in the Legacy API section keep their original unversioned paths.
Create a key
- Sign in to Studio.
- Open your account menu and choose API Keys, or open the API Keys page.
- Create a key for the intended personal or team workspace. Team keys require the appropriate owner or admin role.
- Copy the secret when it is shown. The complete key is only displayed at creation.
The key stays scoped to the selected workspace. Switching the active workspace in the Studio interface does not retarget existing keys. Use a separate key for each integration and environment so you can revoke one without disrupting the others.
Store the key in your server environment or secret manager:
Then make a read-only request. Replace ASSET_ID with the ID of an asset accessible to your key:
Never put an API key in browser JavaScript, a mobile application bundle, a public repository, or a support screenshot. Make authenticated calls from your server.
Account access and revocation
API requests use the scoped workspace’s available features and credits. A valid key does not bypass plan restrictions or model access rules. A virtual fitting room key may have a different account scope and cannot be assumed to grant access to Studio creation endpoints.
Manage and revoke keys on the API Keys page. If a key is exposed, create a replacement, update your server configuration, and revoke the old key. Existing keys cannot create further keys through the Studio key-management routes.
Run your first generation → 
