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.
Simple Guide
Developer Version
Full Example
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 needOnly 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
Login
Use your EDIS Global email + password (same as Client Portal)
Get available options
Ask the API:
- what billing cycles exist
- what payment methods exist
- what locations exist
Pick a location
Choose where your VPS should be deployed
Get plans for that location
This gives you:
- product IDs (pid)
- OS IDs
- addon IDs
Build your order
Put everything together into one JSON request
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 createdOrder 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:
- Ask for options
- Pick IDs
- 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.Order a VPS the right way
When ordering a VPS through the EDIS Global Order API, the most important step is not sending the final request first.👉 First collect all required values
👉 Then send one clean order requestThis approach avoids errors and ensures successful provisioning.This guide uses curl examples for clarity. The same workflow works with Python, PHP, JavaScript, Postman, or any HTTP client.
API workflow
Authenticate
Use your EDIS Global Client Portal email and password
Collect values
Retrieve billing cycles, payment methods, locations, products, and addon IDs
Build payload
Combine all selected values into one JSON structure
Submit order
Send the final request to the order endpoint
Important: Payment method behavior
The selected paymentmethod defines how the first invoice and all renewal invoices are issued.Available account credit is applied automatically when applycredit is omitted or true. Explicitly setting false prevents account credit from being applied to this order. If applied credit covers the invoice, provisioning can begin automatically.
The optional applycredit field belongs inside the order JSON:To opt out of using account credit, add this field to your order JSON. Use the JSON boolean false:This is a field example, not a complete order payload. Setting false does not make an order a test.
Try the API directly in the documentation
The documentation portal sends requests to the production API. There is no sandbox or test environment.You can execute live requests and switch between multiple programming languages such as cURL, Python, JavaScript, PHP, Go, Java, and Ruby.
Use discovery endpoints to inspect plans, locations, and other available options. Order, upgrade, and cancellation requests perform real actions on your account.Available endpoints
Final order endpoint
This endpoint creates a real VPS order and invoice. The example omits applycredit to use the default automatic credit behavior:
Example: Successful response
Example when available account credit covers the invoice:
Best practices
Always fetch locations, products, and addon IDs dynamically.Inventory, availability, and IDs can change at any time.
Before submitting an order, verify:
- location is not out of stock
- product exists in that location
- OS is valid for that product
- addon IDs belong to the same product response
Summary
To order a VPS:
- get billing cycles
- get payment methods
- get locations
- get products
- collect IDs
- submit order
👉 Collect first. Order last.Full example (end-to-end)
This example walks through the complete workflow:👉 collect all required values
👉 build the payload
👉 submit the order
Step 1: Get billing cycle
Example result:👉 We choose: monthly
Step 2: Get payment method
Example result:👉 We choose: paypal
Step 3: Get VPS locations
Example result:👉 We choose: location_id = 94
Step 4: Get VPS products in location
Example result (simplified):👉 We choose:
pid = 892
os = 208
additional_ram = 396
additional_ip = 10
Step 5: Build order payload
This example omits applycredit, so available account credit is applied automatically. To opt out, add "applycredit": false inside the order JSON.
Step 6: Submit order
Live order: Sending this request creates a real VPS order and invoice. It is not a test request.
Successful response
In this example, available account credit covers the invoice:
What just happened
- Order was created
- Invoice was generated
- Account credit was applied automatically because
applycredit was omitted
- In the response shown,
invoicepaid: true confirms that the invoice is paid; provisioning can begin automatically
If invoicepaid is false, the invoice remains unpaid. That flag alone does not mean the order failed.
Key insight
👉 Every value used in the final request comes from previous API callsThere are no hardcoded values.
Pro tip
Final summary
- get billing cycles
- get payment methods
- get locations
- get products
- collect IDs
- submit order
👉 This is the complete workflow.