Getting Started
Common error codes and response examples you may encounter when calling the RDPLINE API.
Every error response consists of success, status, message, errorCode.
The data field is included only in successful responses.
Field
Description
successAlways false in an error response.
statusThe HTTP status code.
messageAn English message describing the cause of the error. It tells you which parameter is invalid and why.
errorCodeA string indicating the category of the error. Its values are fixed, making it a reliable branching criterion for error handling in your application.
errorCode indicates the broad category of an error, while the specific cause is distinguished by message.
For example, parameter-related errors are returned as INVALID_ARGUMENT, and message tells you which parameter caused the problem.
errorCode
HTTP
When it occurs
message
INVALID_ARGUMENT
400
Request parameter errors such as missing required values, format or range errors, fields that do not match the query mode, an invalid cursor, an invalid search sort value, exceeding the page × size limit, or a body parsing failure
Missing required parameter
The required parameter is missing: <parameter>e.g. The required parameter is missing: page
Invalid value, format, or combination
The parameter is invalid: <parameter>e.g. The parameter is invalid: publishedAtStart
UNAUTHENTICATED
401
The API Key is missing, or the API Key is invalid
Missing API Key / Invalid or expired API KeyPERMISSION_DENIED
403
No valid ACTIVE contract exists, or the company identifier cannot be verified, so access is denied
Company is unauthorized or does not exist. / No active client contract found.RESOURCE_EXHAUSTED
429
Rate limit exceeded
Too many requests. Please retry later.INTERNAL
500
Internal server error
An unexpected error occurred.UNAVAILABLE
503
The service is temporarily unavailable due to a backend or search engine failure
Service is temporarily unavailable. Please try again later.DEADLINE_EXCEEDED
504
The search engine response timed out
The search provider did not respond in time. Please try again later.