Manage your services

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 Services page lists every service on your account, from every product, with its status, its next renewal and its price.

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

1. In the sidebar, select Services.
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. 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. Clear turns the tag filter off.
6. To sort the list, select a column heading.
7. Select a service to open it.

Each row shows the service's name, with its address and tags under it and an Ending badge when a cancellation is scheduled. The other columns are Product, Status, Renews (the next renewal date, or Hourly) and Price.

A floating IP, a mail service, an Object Storage service and the other products with an area of their own open on that product's page. Any other service opens a service page with two tabs, Overview and Billing. When the product has its own page, the service page has a button at the top that opens it there.

Summary

The status, the product, the price, the next renewal, when you ordered it (Ordered), when setup finished (Set up), its address and its Service ID.

Configuration

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

Details

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

Tags

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

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, and setup starts on its own.

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, select Open a ticket and ask before that date.

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. 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.

Most product pages have the same Billing tab, so you can change the plan or cancel from there too.

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

No services yet

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

Could not load your services

The list did not load. Select Try again.

A service stays in pending

Its first invoice is unpaid. Open Billing, then Invoices, 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
• Pay an invoice
• Cancel a service

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 or smtp_relay. 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, Container Apps, 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.