Errors

The MeetRox API uses standard HTTP status codes and returns errors as JSON objects.

Error Format

All error responses follow this structure:

{
  "error": "A human-readable description of the error",
  "code": "machine_readable_code"
}

Validation errors may include additional details:

{
  "error": "Invalid parameters",
  "code": "invalid_params",
  "details": {
    "recording": ["is required"]
  }
}

Status	Meaning	Common cause
`200 OK`	Request succeeded	—
`202 Accepted`	Request accepted for async processing	Call import enqueued
`400 Bad Request`	Invalid request parameters	Missing required field, wrong format
`401 Unauthorized`	Missing or invalid API key	Key not sent, revoked, or incorrect
`403 Forbidden`	Valid key but action not allowed	Workspace disabled, feature not enabled, resource not found
`404 Not Found`	Resource does not exist	Invalid call ID
`422 Unprocessable Entity`	Validation failed	Request body failed schema validation
`429 Too Many Requests`	Rate limit exceeded	See Rate Limits
`500 Internal Server Error`	Unexpected server error	Contact MeetRox support

Invalid API key:

{ "error": "API key invalid", "code": "unauthorized" }

Call not found:

{ "error": "Call not found", "code": "not_found" }

Workspace disabled:

{ "error": "Workspace is currently disabled.", "code": "forbidden" }

Feature not enabled (call import):

{ "error": "Forbidden", "code": "forbidden" }