Skip to main content

​
Manage Your VPS the Right Way

EDIS Global Management API is used to manage active VPS services in your account. Use it to:
  • authenticate and create a session
  • check VPS status and resource usage
  • power a server on, off, or reset it
  • reinstall a VPS or mount an ISO
  • manage VNC, PTR records, traffic pool actions, settings, and webhooks
You must have at least one active VPS in your account before you can enable API Access in the control panel.

​
Let’s Keep This Simple

Think of the Management API like a secure remote control for a VPS you already own.👉 You do not start by sending a power or reinstall command.
👉 You first create an auth session and collect the temporary values required for sending management requests.After that, you reuse those values to run other endpoints.

​
The Basic Idea

The workflow is always the same:
  1. Enable API Access in the KVM portal
  2. Create an auth session
  3. Collect the session values
  4. Use those values on management endpoints
  5. Re-authenticate when the session expires
The most important values you receive are:
  • api_host
  • kvm_id
  • signature
  • valid_until
These are the core values used across the Management API.

​
Step-by-Step Overview

1

Enable API Access

Open the KVM management portal for one of your VPS services and enable API access.

API access is account-wide — enabling it for one VPS activates it for all existing and future VPS in your account until it is disabled.
2

Create auth session

Call the auth endpoint with your client area email and password.
3

Collect session values

Save api_host, kvm_id, signature, and valid_until from the response.
4

Run management endpoints

Use those values on endpoints such as power state, reinstall, mount ISO, VNC, PTR, traffic pool, and more.
5

Re-authenticate when needed

If the session expires, create a new auth session and use the new values.

​
Create an Auth Session

curl --request POST \
  --url https://session.edisglobal.com/kvm/v2/get/auth \
  --header 'Content-Type: application/x-www-form-urlencoded' \
  --data email=YOUR_EMAIL \
  --data pw=YOUR_PASSWORD \
  --data kvm_id=YOUR_KVM_ID
You can omit kvm_id if you need auth data for all VPS services in your account.

​
Example Auth Response

{
  "data": {
    "kvm_847362_918273": {
      "api_host": "7f3a21.edisglobal.com",
      "kvm_id": "kvm_947312_968273",
      "valid_until": 1789456123,
      "signature": "12345678901234567890123456789012345678901234567890",
      "primary_ip": "185.203.118.74"
    }
  },
  "status": "success"
}

​
What Do These Values Mean?

  • api_host → the VPS-specific API host you will call next
  • kvm_id → the VPS you want to manage
  • signature → temporary auth signature for that session
  • valid_until → session expiry timestamp
If the session expires, request a new one.

​
Example: Check Power State

curl --request POST \
  --url https://API_HOST/kvm/v2/get/power \
  --header 'Content-Type: application/x-www-form-urlencoded' \
  --data signature=SESSION_SIGNATURE \
  --data kvm_id=KVM_ID \
  --data valid_until=VALID_UNTIL
Example response:
{
  "data": "server powered on",
  "status": "success",
  "traffic_suspended": false
}

​
Example: Reinstall a VPS

Start by fetching a list of auto-installable OS images:
curl --request POST \
  --url https://API_HOST/kvm/v2/get/images \
  --header 'Content-Type: application/x-www-form-urlencoded' \
  --data signature=SESSION_SIGNATURE \
  --data kvm_id=KVM_ID \
  --data valid_until=VALID_UNTIL
Pick one and trigger an installation.
curl --request POST \
  --url https://API_HOST/kvm/v2/set/reinstall \
  --header 'Content-Type: application/x-www-form-urlencoded' \
  --data signature=SESSION_SIGNATURE \
  --data kvm_id=KVM_ID \
  --data valid_until=VALID_UNTIL \
  --data image=cloudinit_ubuntu-lts-22-04 \
  --data password=YOUR_PASSWORD

​
Pro Tip

Avoid hardcoding values. Always create a fresh auth session and fetch current parameters before performing actions.

​
Key Takeaway

The Management API is simple once you understand this pattern:
  1. create auth session
  2. collect session values
  3. call the endpoint you need
  4. re-authenticate when the session expires
That’s the core principle.
Last modified on April 20, 2026