# Manage your services

> Find every service on your account, filter the list, and read a service's status, configuration and history.

Source: https://docs.coritan.com/get-started/services/

In the dashboard:

- /dashboard/services: https://www.coritan.com/dashboard/services
- /dashboard/services/…/overview: https://www.coritan.com/dashboard/services
- /dashboard/services/…/billing: https://www.coritan.com/dashboard/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.

## Before you begin

- Sign in to the [dashboard](https://www.coritan.com/dashboard). The list holds the services billed to your account.

## Find a service

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.

| Filter | Shows |
| --- | --- |
| **Active** | Services that are running and paid up. |
| **Pending** | Services waiting for their first payment, and services we are setting up. |
| **Suspended** | Services we paused, usually for an unpaid invoice. |
| **Ending** | Services with a cancellation scheduled, and services that have ended. |

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

## Read a service's page

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.

### The Overview tab

**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](/get-started/tags/) 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](/billing/invoices/), and setup starts on its own.

**Suspended**
: The box gives the reason. [Failed payments and suspended services](/billing/failed-payments/) 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.

### The 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. **Change plan** moves the service to another plan, as [Change a service's plan](/billing/change-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](/billing/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.

## Result

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

| Status | Meaning |
| --- | --- |
| `pending` | Ordered, and waiting for its first payment or for setup to start. |
| `provisioning` | We are setting it up. |
| `active` | Ready to use. |
| `suspended` | Paused, usually for an unpaid invoice. We keep its data while it is suspended. |
| `pending_termination` | Cancelled, and being removed. |
| `terminated` | Ended and removed. |
| `failed` | Setup did not finish. Contact [support](/support/). |

## Troubleshooting

**No services yet**
: The account has no services. Select **Browse products** to [order one](/get-started/order-a-service/).

**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](/support/conversations/).

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.

## Related

- [Order a service](/get-started/order-a-service/)
- [Tag your services](/get-started/tags/)
- [Pay an invoice](/billing/invoices/)
- [Cancel a service](/billing/cancel-a-service/)

## With the API

List your services with [`GET /services/`](/api/reference/client/services/#op-get-api-v1-services), newest first:

```bash
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](/api/pagination/) explains paging.

Each service has these fields:

```json
{
  "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}`](/api/reference/client/services/#op-get-api-v1-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`](/api/reference/client/services/#op-get-api-v1-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`](/api/reference/client/services/#op-post-api-v1-services-service-ref-actions) runs an action the product offers on an `active` service, with `action` and optional `params`:

```bash
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"}'
```

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

| Product | `action` values |
| --- | --- |
| Cloud Compute | `start`, `stop`, `shutdown`, `reboot`, `console`, `reset_password`, `rebuild`, `create_snapshot`, `enter_rescue`, `exit_rescue`, `regenerate_cloud_init`, `set_hostname`, `set_ssh_keys` |
| Container Apps | `start`, `stop`, `restart`, `kill`, `console`, `reinstall` |
| DDoS Shield profile | `view_alerts`, `whitelist_ip`, `blacklist_ip`, `bind_ip`, `unbind_ip` |
| External Server | `update_upstream`, `set_proxy_protocol`, `set_region`, `test_connection` |

Each product's section documents its own endpoints, which do the same work with that product's checks and limits: [Cloud Compute](/cloud-compute/), [Container Apps](/managed-containers/), [DDoS Shield](/ddos-shield/custom-profiles/) and [external servers](/proxies/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`.

## API

- `GET /api/v1/services/`: List services (https://docs.coritan.com/api/reference/client/services/#op-get-api-v1-services)
- `GET /api/v1/services/{service_ref}`: Fetch a service by numeric id OR underlying resource UUID (instance/server/IP) (https://docs.coritan.com/api/reference/client/services/#op-get-api-v1-services-service-ref)
- `GET /api/v1/services/{service_ref}/events`: Get events (https://docs.coritan.com/api/reference/client/services/#op-get-api-v1-services-service-ref-events)
- `POST /api/v1/services/{service_ref}/actions`: Execute action (https://docs.coritan.com/api/reference/client/services/#op-post-api-v1-services-service-ref-actions)