Errors
Handle RFC 9457 problems and rate limits.
Errors use application/problem+json and the RFC 9457 field set. The code and requestId fields are stable extensions.
{
"type": "https://app.myremotely.ai/en/docs/errors#invalid-api-key",
"title": "Unauthorized",
"status": 401,
"detail": "Provide a valid API key.",
"code": "invalid_api_key",
"requestId": "request_demo_01"
}| Status | Code | Meaning |
|---|---|---|
| 400 | invalid_request | A limit or other input is malformed. |
| 401 | invalid_api_key | The key is missing, wrong, expired, or revoked. |
| 403 | missing_scope | The key does not have the operation scope. |
| 404 | lock_not_found or cursor_not_found | The resource is missing or is outside the key organization. |
| 429 | rate_limited | The key request budget is exhausted. |
| 500 | internal_error | MyRemotely could not complete the request. |
invalid_request
One or more request values do not match the operation schema.
invalid_api_key
The key is missing, wrong, expired, or revoked. The response does not say which condition applied.
missing_scope
The key is valid but does not have the scope named in detail.
lock_not_found
The lock is missing, retired, or owned by another organization.
cursor_not_found
The cursor is malformed, changed, or belongs to another organization.
rate_limited
The API key request budget is exhausted. Wait for Retry-After.
internal_error
MyRemotely could not complete the request. Use requestId when you contact support.
For 429, wait for the number of seconds in Retry-After. Retry 500 with bounded exponential backoff. Do not retry 400, 401, 403, or 404 without changing the request or credential.
Last updated Sep 18, 2026