RyzenRDP reseller API v1 reference

Four steps take you from a funded account to a running server. Replace rzk_YOUR_API_KEY with a key from the Reseller API page of your console.

# 1. Your account: status, balance, discount and server cap
curl https://ryzenrdp.com/api/v1/account \
  -H "Authorization: Bearer rzk_YOUR_API_KEY"

# 2. Plans, with your price and live stock for each location
curl https://ryzenrdp.com/api/v1/plans \
  -H "Authorization: Bearer rzk_YOUR_API_KEY"

# 3. Order a server: the first month is charged from the wallet
curl https://ryzenrdp.com/api/v1/servers \
  -H "Authorization: Bearer rzk_YOUR_API_KEY" \
  -H "Idempotency-Key: order-2026-0001" \
  -H "Content-Type: application/json" \
  -d '{"plan": "amd-ryzen-t1", "location": "new-york",
       "os": "ws2022", "label": "client-42"}'

# 4. Poll until "state" is "active", then read the login details
curl https://ryzenrdp.com/api/v1/servers/srv_0123456789abcdef \
  -H "Authorization: Bearer rzk_YOUR_API_KEY"
curl https://ryzenrdp.com/api/v1/servers/srv_0123456789abcdef/credentials \
  -H "Authorization: Bearer rzk_YOUR_API_KEY"

A new server is usually active within minutes. If the build fails, the charge is refunded to the wallet and the state becomes failed.

• Base address: https://ryzenrdp.com/api/v1. Every path on this page is relative to it.
• Format: JSON in, JSON out, UTF-8.
• Money is a decimal string in US dollars, for example "14.99".
• Times are ISO 8601 in UTC, for example "2026-12-11T10:04:00Z".
• Server ids look like srv_0123456789abcdef.

• Rate limits are per account: 120 reads and 30 writes a minute. A request over the limit is answered with 429 rate_limited and a Retry-After header.
• Account caps also answer 429: server_limit when the account has reached its cap on running servers, and create_rate when too many servers were ordered in the last hour. GET /account returns your running servers and your cap.
• Idempotency. POST /servers accepts an Idempotency-Key header of 8 to 80 characters: letters, digits, -, _, . and :. Repeating the call with the same key returns the same server and charges the wallet once, so a timed-out order is safe to retry. Keys are compared exactly: a key that differs only in case is a new order.

GET /servers and GET /servers/{id}

GET /servers lists your servers; add ?all=1 to include terminated and failed ones. GET /servers/{id} returns one server.

{"server": {"id": "srv_0123456789abcdef", "label": "client-42", "plan": "amd-ryzen-t1",
  "location": "new-york", "os": "ws2022", "state": "active",
  "ip_address": "203.0.113.10", "hostname": "…",
  "price": "13.49", "list_price": "14.99", "discount_pct": 10, "currency": "USD",
  "auto_renew": true, "paid_until": "2026-12-11T10:04:00Z", "overdue": false,
  "created_at": "2026-11-11T10:02:11Z", "terminated_at": null, "error": null}}

POST /servers

Orders a server. label is optional.

{"plan": "amd-ryzen-t1", "location": "new-york", "os": "ws2022", "label": "client-42"}

The first month is charged from the wallet and the build is queued. The API answers 202 with the server in the state queued; poll GET /servers/{id} until the state is active. If the build fails, the charge is refunded and the state becomes failed.

PATCH /servers/{id}

Changes auto_renew, label or both.

{"auto_renew": false, "label": "new label"}

With auto_renew off, the server is deleted at the end of the paid period.

DELETE /servers/{id}

Destroys the server and its data, and answers 202. POST /servers/{id}/terminate does the same. The current month is not refunded. A server that has not started building yet is canceled and refunded in full. While a server is being built the call answers 409 busy: try again in a few minutes.

GET /servers/{id}/status

The server's state, power state and usage.

{"id": "srv_…", "state": "active", "power_state": "running",
 "usage": {"cpu_percent": 3, "ram_used_mb": 1210, "ram_mb": 2048,
           "disk_used_gb": 21, "disk_gb": 40, "bandwidth_used_gb": 12},
 "pending_restart": false}

POST /servers/{id}/power

action is start, stop, restart or poweroff. Answers 202.

{"action": "restart"}

POST /servers/{id}/password

Generates a new administrator or root password. If the answer carries "applies_on_next_boot": true, restart the server first, then read /credentials.

GET /servers/{id}/credentials

The login details of the server.

{"id": "srv_…", "username": "Administrator", "password": "…", "ip_address": "203.0.113.10",
 "port": 3389, "protocol": "rdp", "available_until": "2026-11-18T10:04:00Z"}

The password is held only for a set period after a build or a reset, shown as available_until. After that this call answers 409 refused: reset the password and read it again. Every read is recorded in the audit log.

POST /servers/{id}/reinstall

Reinstalls the operating system and erases all data on the server. confirm must be the id of the server. Answers 202.

{"os": "ubuntu2404", "confirm": "srv_0123456789abcdef"}

• Keep API keys on your own server. Do not put a key in a browser, a mobile app or a public code repository.
• If a key may have leaked, revoke it on the Reseller API page of your console and create a new one.
• Every change made through the API and every read of /credentials is recorded in the audit log.
• A password is held only for a set period after a build or a reset. Read it, store it the way you store other secrets, and reset it if you need it again later.
• A reinstall needs the server id in confirm, which guards against erasing the wrong server by mistake.