Errors - Get2Dial

Every error response uses the same shape.

Error shape

{
  "status": "error",
  "message": "email is already in use",
  "code": "invalid_request",
  "request_id": "req_...",
  "field_errors": { "email": "already in use" }
}

field_errors is only present on validation failures where the API can identify which field caused the problem. request_id matches the X-Request-Id response header — include it when contacting support.

Error codes

HTTP status	`code`	Meaning	Retryable
400	`invalid_request`	The request body or parameters are malformed	No — fix the request
401	`unauthorized`	Missing or invalid credentials	No — fix authentication
403	`forbidden`	Authenticated, but not permitted for this resource	No — check capabilities
404	`not_found`	The resource doesn’t exist	No
409	`conflict`	The request conflicts with the resource’s current state	Sometimes — depends on the conflict
422	`unprocessable`	Well-formed but semantically invalid	No — fix the request
429	`rate_limited`	You’ve exceeded your rate limit	Yes — see Rate limits
500+	`internal_error`	Something failed on Get2Dial’s side	Yes, with backoff

code is derived directly from the HTTP status, so it’s always predictable from the status code alone.

Rate limits

Conventions

⌘I