Developers

API documentation

Create a token in your panel under API tokens, choosing what it may do. Send it as a bearer token. Responses are JSON; lists are paginated and accept per_page up to 100.

Build servers, read their state and check your balance from your own system. Every endpoint is scoped to your own account, and a token carries only the abilities you grant it.

The shortest useful example

# What can I afford right now?
curl https://your-panel/api/v1/wallet \
  -H "Authorization: Bearer $COBANTO_TOKEN"

{ "data": { "currency": "USD", "balance": 276.10, "outstanding": 84.50,
            "available": 191.60, "monthly_commitment": 84.50,
            "suspended": false, "overdue": false } }

# What is on sale
curl https://your-panel/api/v1/catalog/plans \
  -H "Authorization: Bearer $COBANTO_TOKEN"

# Build one. It returns straight away, still provisioning.
curl -X POST https://your-panel/api/v1/instances \
  -H "Authorization: Bearer $COBANTO_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"plan_id": 12, "name": "web-01", "region": "EU"}'

Every endpoint there is

Method	Path	Ability needed
`GET`	`/api/v1/ping`	none — check the service is up
`POST`	`/api/v1/tokens`	none — issue a token with your login
`GET`	`/api/v1/catalog/plans`	any token — plans on sale, with your price
`GET`	`/api/v1/wallet`	wallet:read
`GET`	`/api/v1/wallet/transactions`	wallet:read
`GET`	`/api/v1/invoices`	wallet:read
`GET`	`/api/v1/instances`	instances:read
`GET`	`/api/v1/instances/{id}`	instances:read
`POST`	`/api/v1/instances`	instances:write
`POST`	`/api/v1/instances/{id}/actions/{action}`	instances:write
`DELETE`	`/api/v1/instances/{id}`	instances:write

Questions

Straight answers before you deploy

Still deciding?

Engineers answer, not scripts.

Ask the help desk Service status

Only what you ticked when you made it. instances:read sees your servers, instances:write builds and destroys them, and wallet:read reads your balance, movements and invoices. A token for building servers cannot read your books, and the other way round.

It can order servers, which is spending. It cannot top up: adding funds moves real money and happens in a browser where a person approves it. There is no endpoint for it at all.

Everything here is paid from your balance, so an order against an empty wallet is refused. Reading /wallet first lets your own shop tell a customer before taking their money, rather than after.

Sixty calls a minute per token, and ten a minute on issuing tokens. Lists cap at a hundred rows a page whatever you ask for.

POST to /instances/{id}/actions/{action} with start, stop, reboot or rescue. The reply says it was accepted; the work finishes in the background, so read the instance back to see the new state.

Your own panel: whatever address you log in at, with /api/v1 after it. There is no separate API domain.

Ready when you are.

Configure a server now. Your account is created right before payment, with the configuration saved.

Configure your server Talk to sales

No setup fee

On any contract term

No card on file

Prepaid balance, topped up when you choose

Same price at renewal

The one you signed up for

Cancel from the panel

One click, no phone call