Hubfly spaceDocs
Console

API · Cell

Cell API

Deploy and operate containers through the authenticated Hubfly space Dashboard API.

What this reference covers

Cell uses the normal Dashboard JSON API at https://api.hubfly.space/api/v1. Send a Dashboard bearer token with project permissions. The Cell endpoints below operate on containers, builds, Compose stacks, network routes, volumes, GPU resources, images and webhooks. They use the same request and error envelope as the rest of Dashboard.

How Cell differs from Box, Storage and Mail

Cell is the container platform. Your application runs as a managed container, with image or source builds and container-level routes. Box runs a full virtual machine. Storage offers S3-compatible object storage; Mail offers separate direct sending credentials. These are different project platforms, even though their project management begins in Dashboard.

Choose a workflow

Each group lists its exact method and path, request body fields, response schemas and errors. The interactive endpoint explorer lets you search all endpoints together.

Shared project API

Create a project with POST /api/v1/projects/create and set its platform to Cell; use GET /api/v1/projects and GET /api/v1/projects/:projectId to find it. Project membership, settings, environment variables and billing are shared Dashboard features, so they remain in the general API reference. The authentication guide covers bearer tokens and project authorization.

A typical Cell workflow

  1. Create a Cell project in the desired region.
  2. Deploy a container from an image, a Git build, or a Compose stack.
  3. Follow its state and logs until the workload is running.
  4. Publish its internal port through an HTTP or TCP endpoint and attach a domain if needed.
  5. Add volumes, replicas, network rules or automation as the service grows.

For concepts and Dashboard steps, start with Cell quick start, image deployment, or Git deployment.

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