Hubfly spaceDocs
Console

API · Box

Box API

Create and operate virtual machines through the authenticated Hubfly space Dashboard API.

Which API to use

All customer Box operations use https://api.hubfly.space/api/v1 with a Dashboard bearer token. Box host control is private to Hubfly space. The paths below are the public customer contract; you do not connect to the Box host directly.

Most paths include :projectId. Replace it with the ID of a Box project you can access. Pricing and eligibility are account-level reads and do not include a project ID. Request bodies are JSON.

Endpoint groups

These five groups cover all 48 Box endpoints in the Dashboard API schema. Each operation page includes its method, path, request fields, response schema, and status codes.

Asynchronous operations

Create, resize, power, volume, NIC, mapping, firewall, and deletion actions may return an operationId before the host has finished. Read project operations until the operation reaches succeeded, failed, partial, or canceled. A Box may be powered on while guest initialization has failed, so inspect its initialization endpoint separately.

Keep operation IDs

Use the returned operation ID when showing progress or recovering from a network timeout. Do not treat an accepted API response as a completed machine change.

Authentication and errors

The bearer token must belong to a member allowed to access the project. Use authentication for token setup and errors for the standard error envelope and retry guidance. Start with the Box platform guide for workflow explanations.

Something unclear or out of date? Emailsupport@hubfly.spaceBack to top