---
title: "Errors and limits · API docs | Rdp.Vision"
description: "Manage Rdp.Vision servers from code or an AI agent: order, start, stop, renew and top up with an API key, or connect Claude, Cursor and other agents to the MCP server."
url: https://rdp.vision/docs/api/errors
---

Open in AI

[ChatGPT](https://chatgpt.com/?q=Read%20https%3A%2F%2Frdp.vision%2Fdocs%2Fapi%2Ferrors.md%20and%20help%20me%20use%20the%20Rdp.Vision%20API.)[Claude](https://claude.ai/new?q=Read%20https%3A%2F%2Frdp.vision%2Fdocs%2Fapi%2Ferrors.md%20and%20help%20me%20use%20the%20Rdp.Vision%20API.)

# Errors and limits

Errors come back with a status code and a JSON body with a `detail` field, usually a sentence you can show as is.

{
  "detail": "This API key lacks the 'power' scope"
}

## Status codes

- 400 | Bad request | Something in the request is wrong, for example an unknown plan or a duration over 12.
- 401 | Unauthorized | No key, a wrong key, or a revoked or expired one.
- 402 | Payment required | The balance doesn’t cover it. detail has message, required and balance.
- 403 | Forbidden | The key lacks the scope, the endpoint isn’t open to keys, the balance is frozen or the server is suspended.
- 404 | Not found | No such server or order on this account.
- 409 | Conflict | The server is busy, for example still setting up after an order or reinstall.
- 422 | Unprocessable | A field has the wrong type or is missing. detail lists each problem.
- 429 | Too many requests | More than 120 requests a minute with one key, or too many wrong keys from one address.
- 503 | Unavailable | The data centre didn’t answer in time. Safe to retry.

## Rate limits

120 requests a minute per key. Over that, requests answer 429 until the minute has passed. Poll a setting-up server every 15 to 30 seconds, not faster.