Skip to main content
Live ordering — no test environmentEDIS Global does not provide a sandbox or test environment. Submitting a valid order to POST /kvm/v2/add/order creates a real VPS order and invoice.If account credit is applied and covers the invoice, provisioning can begin automatically.Setting "applycredit": false prevents account credit from being used for that order. It does not prevent the order from being created or make the request a test.Requests that retrieve plans, locations, or account balances do not place orders.

Let’s keep this simple

If you want to order a VPS using the EDIS Global API, think of it like this:👉 You don’t start by ordering
👉 You first collect all the pieces you need
Only after that, you send one final request.

The basic idea

Imagine ordering a VPS like ordering food:You need to decide:
  • where (location)
  • what (plan)
  • how often you pay (billing cycle)
  • how you pay (payment method)
  • extras (RAM, IPs, etc.)
The API works exactly the same way.

Step-by-step overview

1

Login

Use your EDIS Global email + password (same as Client Portal)
2

Get available options

Ask the API:
  • what billing cycles exist
  • what payment methods exist
  • what locations exist
3

Pick a location

Choose where your VPS should be deployed
4

Get plans for that location

This gives you:
  • product IDs (pid)
  • OS IDs
  • addon IDs
5

Build your order

Put everything together into one JSON request
6

Send the order

Call the order endpoint

Step 1: Get billing cycles

Just ask the API what billing cycles exist.
You’ll get something like:
👉 Pick one.

Step 2: Get payment methods

Example result:
👉 Pick one.

Step 3: Get VPS locations

You’ll see something like:
👉 Important:
  • use the id
  • ignore locations where out_of_stock = true

Step 4: Get VPS plans (this is the important one)

Now you ask:👉 “What can I buy in this location?”
Now you get everything:
  • plan IDs → pid
  • OS IDs → os
  • addon IDs → RAM, IPs, etc.

Step 5: Pick what you want

From that response, choose:
  • plan → pid
  • OS → os
  • optional:
    • RAM
    • CPU
    • IPs
    • disk 👉 Everything is just IDs.

Final step: Send the order

This sends a real VPS order. The example omits applycredit, so available account credit is applied automatically:

What happens next?

If everything is correct, you get:
That means:✅ Order created
✅ Invoice created
Order creation does not by itself confirm payment or provisioning. If available account credit covers the invoice, provisioning can begin automatically. If the invoice remains unpaid, complete payment using the selected payment method.

Key takeaway

👉 The API is simple once you understand this:
  1. Ask for options
  2. Pick IDs
  3. Send order
That’s it.

Pro tip

Always fetch locations and products dynamically.IDs can change, new locations can appear, stock can change, and new plans can appear.Available account credit is applied automatically when you omit applycredit or set it to true, regardless of the selected payment method. To place an order without using account credit, explicitly set "applycredit": false inside the order JSON.

If you get stuck

Think of it like this:👉 “What values do I still NOT have?”Then go back and call the endpoint that gives you that value.That’s the whole workflow.
Last modified on September 5, 2026