API
The API does exactly what the console does, with the same permissions and the same promises. Create a token under Your account > API tokens.
Example
curl -H "Authorization: Bearer lc_your_token" https://cloud.lumcells.com/api/v1/servers
curl -X POST -H "Authorization: Bearer lc_your_token" -H "Content-Type: application/json" \
-d '{"hostname": "web-3", "plan": "s", "region": "chi", "image": "debian-13"}' \
https://cloud.lumcells.com/api/v1/servers
Endpoints
| Method | Path | What it does | Group | Needs a token |
|---|---|---|---|---|
| GET |
/api/v1/firewalls
|
Firewall groups with their rules
| servers | yes |
| GET |
/api/v1/images
|
Operating system images
| catalogue | no |
| GET |
/api/v1/invoices
|
Invoices
| billing | yes |
| GET |
/api/v1/me
|
Who this token acts as
| account | yes |
| GET |
/api/v1/notices
|
Announced changes with their countdown
| billing | yes |
| GET |
/api/v1/orders
|
Orders with their locked prices
| billing | yes |
| GET |
/api/v1/plans
|
Plans and today's prices
| catalogue | no |
| GET |
/api/v1/regions
|
Regions open for new orders
| catalogue | no |
| GET |
/api/v1/servers
|
List your servers
| servers | yes |
| POST |
/api/v1/servers
|
Create a server Starts an order at today's price, locked for 12 months. The server is "provisioning" until it is built.
| servers | yes |
| GET |
/api/v1/servers/{id}
|
One server
| servers | yes |
| DELETE |
/api/v1/servers/{id}
|
Delete a server for good Destroys the server and its snapshots on the node and stops metering. The body must repeat the hostname.
| servers | yes |
| GET |
/api/v1/servers/{id}/metrics
|
CPU, memory, network and disk samples
| servers | yes |
| POST |
/api/v1/servers/{id}/power
|
Start, shut down, power off or reboot
| servers | yes |
| POST |
/api/v1/servers/{id}/reinstall
|
Wipe the disk and install an image again
| servers | yes |
| POST |
/api/v1/servers/{id}/resize
|
Resize to a bigger plan Starts a new order at today's price with a fresh 12-month price lock.
| servers | yes |
| GET |
/api/v1/servers/{id}/snapshots
|
Snapshots and backups of a server
| servers | yes |
| POST |
/api/v1/servers/{id}/snapshots
|
Take a snapshot or backup now
| servers | yes |
| GET |
/api/v1/ssh-keys
|
SSH keys
| servers | yes |
| POST |
/api/v1/ssh-keys
|
Add an SSH public key
| servers | yes |
| GET |
/api/v1/staff/features
|
Staff: the feature registry
| staff | yes |
| GET |
/api/v1/staff/jobs
|
Staff: background jobs
| staff | yes |
| POST |
/api/v1/staff/jobs/{key}/run
|
Staff: run a job now
| staff | yes |
| GET |
/api/v1/staff/nodes
|
Staff: nodes with capacity ratios and alarms
| staff | yes |
| GET |
/api/v1/staff/reality
|
Staff: what is real (live integration checks and blockers)
| staff | yes |
| GET |
/api/v1/status
|
Region status and open incidents (same data as the status page)
| status | no |
| GET |
/api/v1/tickets
|
Support tickets
| support | yes |
| POST |
/api/v1/tickets
|
Open a support ticket
| support | yes |
| GET |
/api/v1/usage
|
This month's usage and the credit balance
| billing | yes |
Errors come back as JSON: {"error": "invalid", "message": "..."} with a matching HTTP status (401, 403, 404, 409, 422).