Introduction
The IBEE Solutions API gives you programmatic access to your infrastructure. You can manage virtual machines, object storage buckets, secrets, and more — all from your own code or automation tools.
Base URL
All API requests use the following base URL:
Workspace scoping
Every API request must include a workspace_id query parameter. This scopes the request to a specific workspace within your organization.
Workspaces isolate resources so that production, staging, and development environments stay separate. You choose which workspaces a token can access when you create it.
Available resources
Response format
All responses are JSON. Successful responses return the resource directly. Errors return a JSON object with a detail field:
Async operations
Some operations — creating, deleting, starting, stopping, or rebooting virtual machines — are asynchronous. These endpoints return 202 Accepted with an operation_id you can poll:
Use the Get operation status endpoint to check progress.
Idempotency
Write operations (create, delete, power actions) require an X-Idempotency-Key header. If a request fails due to a network issue, you can safely retry with the same key — the server will not create duplicate resources.
Next steps
- Authentication — Create and use API tokens.
- Rate limits — Understand request limits.
