Errors

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"
}

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.

feature_not_enabled

The key is valid, but the organization cannot use the public API channel or the operation's owning feature. The details object contains feature and either failed with optional via, or grace and until. These fields identify the feature and the reason. They never contain vendor credentials, secrets, or arbitrary error bodies. New provider work requires enabled access even when retained data has a read grace period. Administrators can inspect and revoke keys in Settings while public API access is disabled.

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.