Manage your subscriptions

A service is one thing you pay for: an instance, a server, a floating IP, a mail service, a bucket plan and so on. The Subscriptions tab of Billing lists every service on your account, from every product, with its status, its price and when it renews. Old links to the Services page open this tab.

• Sign in to the dashboard. The list holds the services billed to your account.

1. In the sidebar, select Billing, then the Subscriptions tab. You can also select Search services and pages at the top of the dashboard and type subscriptions.
2. Type part of a name, an address or a service ID in Search by name, address or ID.
3. To see one status group, select Active, Pending, Suspended or Ending. Failed and Ended appear too while a service has that status. Each one shows how many services it holds. All shows every service again.
4. If you have more than one product, choose one in the product menu. All products shows them all.
5. To show only services with a tag, select the tag in the row of tags under the search box. Select more than one tag to show services that have all of them. Select a tag again to take it out of the filter.
6. To sort the list, select a column heading.
7. Select a service to open its billing. Where a service opens lists where each one goes.

Clear filters turns every filter off. The page's address keeps the filters, so a reload or a link you share opens the list as you left it.

Each row shows the service's name, with its address and tags under it and an Ending badge when a cancellation is scheduled. Product names the product, with the product you ordered under it. Status shows the service's status, and Price what each billing cycle costs, or Billed by use for a service that has no price of its own (How usage billing works). Renews shows the next renewal date, Hourly for a service billed by the hour at a flat price, a dash for a service billed by use, or the date a cancelled service ends, such as Ends 16 Oct 2026.

A service opens where you manage its billing. For most products that is the Billing tab of the product's own page:

A server or an instance that we are still setting up opens its page under Subscriptions until it is ready.

A service with no product page of its own has a page under Subscriptions. All subscriptions at the top takes you back to the list, with the filters you left it with.

The top of the page shows the service's name, its status, its product, and an Ending badge when a cancellation is scheduled. Under the name are the product you ordered, the address, the day you ordered it and the service ID. An add-on names the service you added it to, such as Add-on to service #1042. Select that to open the other service. When the product has a page of its own, a button at the top opens it there, such as Open in Snapshot Storage.

A box at the top explains a service that needs something from you:

Waiting for payment

The first invoice is unpaid. Select Open invoices and pay it. We set the service up as soon as you pay.

Suspended

The box gives the reason. Failed payments and suspended services explains how to restore the service.

Cancellation scheduled

The service ends on the date shown. To keep it, contact support before that date.

The page shows the same billing cards as each product's Billing tab:

Current plan

The product, the plan, the price and the status. It also shows the next renewal, or for an hourly service what it has cost this month (Used this month) against its monthly cap. A service billed by use has no price of its own, so the card shows a price of zero and Change plan… has nothing to change (How usage billing works). Set up is when setup finished, and Service ID the service's number. Change plan… moves the service to another plan, as Change a service's plan describes.

Activity

The service's history, newest first: When it happened, the Event, the Details and By whom.

Cancel service

Ends the service. Cancel a service explains the choices.

Tags

Your labels for the service. Tag your services explains them.

Configuration

What you chose when you ordered, such as the location or the size. Values that look like passwords, secrets, tokens or keys are left out.

Details

Technical details that setup recorded, such as the address a service got.

You can see where each service stands, what it costs and when it renews. A service moves through these statuses:

No subscriptions yet

The account has no services. Select Browse products to order one.

No matches

No service matches the search and the filters. Select Reset filters.

Could not load your subscriptions or Could not load this service

The list or the page did not load. Select Try again.

Subscription not found

The page says This service is not on your account. The service belongs to another account, or the address has a typo. Select All subscriptions to go back to the list.

A customer's service is not in the list

The list holds your own account's services. The services your organization's customers hold are on the organization's Services tab (Manage customer services).

A service stays in pending

Its first invoice is unpaid. In the sidebar, select Billing, then the Invoices tab, and pay it. If it is paid and the service has not moved, contact support.

A service shows failed

Setup could not finish. Open a ticket with the service ID so the team can set it up again or cancel it.

• Order a service
• Tag your services
• Change a service's plan
• Cancel a service
• Pay an invoice

List your services with GET /services/, newest first:

curl "https://api.coritan.com/api/v1/services/?status=active&resource_type=vps&limit=50" \
  -H "Authorization: Bearer $CORITAN_TOKEN"

status

One status from the table above.

resource_type

The product: vps (or cloud_compute), container, ip (or floating_ip), mail, smtp_relay or storage (Snapshot Storage). Another word answers 422 with "error": "invalid_resource_type" and the words it accepts in allowed.

tag

A tag on the service, such as production.

limit and offset

The page size (default 100, at most 500) and how many services to skip. Pagination and filtering explains paging.

Each service has these fields:

{
  "id": 1042,
  "product_id": 7,
  "pricing_id": 21,
  "hostname": "web-1.example.com",
  "status": "active",
  "billing_cycle": "monthly",
  "amount": 12.0,
  "next_due_date": "2026-10-16T09:30:00",
  "product_name": "Cloud Compute 2 GB",
  "module_name": "vps",
  "pricing_name": "Monthly",
  "termination_date": null,
  "tags": ["production"],
  "resource": {"type": "vps", "label": "web-1.example.com", "status": "running", "address": "203.0.113.10", "detail": {}}
}

amount is the price per cycle, and next_due_date the next renewal. termination_date is set once a cancellation is scheduled. config holds what you ordered, module_data what setup recorded, and suspension_reason why a service is suspended. For an hourly service, hourly_usage_this_month, monthly_cap and hourly_cap_reached show its spend against the cap. resource summarises what the service runs: its type (vps, container, ip or external_server), label, status and address, with product details in detail.

Get one service with GET /services/{service_ref}. service_ref is the service ID, or the UUID of the instance, server or floating IP behind it. A service that does not exist answers 404 Service not found, and someone else's answers 403 Access denied.

Read its history with GET /services/{service_ref}/events, newest first. It takes page and limit (default 50, at most 200). Each event has event_type, description, actor_type (such as user or system), metadata and created_at. The event types are created, provisioning_started, provisioned, provisioning_failed, suspended, unsuspended, upgrade, downgrade, termination_requested, terminated, action_executed and config_changed.

POST /services/{service_ref}/actions runs an action the product offers on an active service, with action and optional params:

curl -X POST https://api.coritan.com/api/v1/services/1042/actions \
  -H "Authorization: Bearer $CORITAN_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"action": "reboot"}'

{"success": true, "message": "Power action 'reboot' executed", "data": null}

Each product's section documents its own endpoints, which do the same work with that product's checks and limits: Cloud Compute, App Deployment, DDoS Shield and external servers. Use those for day-to-day work. Floating IPs, Mail Hosting and SMTP Relay answer "success": false with the endpoints to use instead. A service that is not active answers 400 Service is not active, and an action the product does not offer answers 400 Action 'name' not available.