Search Documentation
API Response Status Errors
If your request encounters problems during processing, the eBay servers can respond with either an error or warning condition. While processing might continue if a warning is encountered, the processing stops when errors are encountered.
REST API Errors
4xx and 5xx HTTP Status Codes
When you make a call to an eBay API, you can get a response that contains errors or warnings as described above. However, each API can also return common errors, which are error conditions that can occur while processing a call to any API. Common errors stop processing and they must be addressed before you can get a successful response from your call.
Types
- ErrorType
This error type is used by both REST and GraphQL APIs, and defines the details of a specific error or warning.
- ErrorCategory
This enumerated type defines the classification of the error or warning. This can be one of three following values:
Possible Values:Value Description APPLICATION This value indicates an exception or error occurred in the application code or at runtime. BUSINESS This value indicates that your service or a dependent service refused to continue processing due to a business rule violation. REQUEST This value indicates there is something wrong with the request, such as authentication, syntactical errors, or missing headers.
HTTP Status Codes
HTTP 400: Bad Request
Error ID
Error Category
Message
Long Message
Domain
1002
REQUEST
Missing access token
Access token is missing in the Authorization HTTP request header.
OAuth
1003
REQUEST
"Token type in the Authorization header is invalid:" + scheme
"Token type in the Authorization header is invalid:" plus scheme
OAuth
2004
REQUEST
Invalid request
Request has errors. For help, see the documentation for this API.
ACCESS
3001
REQUEST
Request rejected
ROUTING
3002
REQUEST
Malformed request
The request has errors. For help, see the documentation for this API.
ROUTING
HTTP 429: Too Many Requests
Error ID
Error Category
Message
Long Message
Domain
2001
REQUEST
Too many requests
The request limit has been reached for the resource.
ACCESS
2005
REQUEST
Personal data transfer threshold reached
This application has reached the regulatory compliance threshold for personal data transfer.
ACCESS
GraphQL API Errors
4xx and 5xx HTTP Status Codes
These errors occur infrequently and are usually related to authentication/authorization, malformed HTTP requests, or upstream service failures. These errors are less common in GraphQL and are usually related to authentication/authorization, invalid HTTP requests, or unexpected server errors.
Types
- ErrorType
This error type is used by both REST and GraphQL APIs, and defines the details of a specific error or warning.
- ErrorCategory
This enumerated type defines the classification of the error or warning. This can be one of three following values:
Possible Values:Value Description APPLICATION This value indicates an exception or error occurred in the application code or at runtime. BUSINESS This value indicates that your service or a dependent service refused to continue processing due to a business rule violation. REQUEST This value indicates there is something wrong with the request, such as authentication, syntactical errors, or missing headers.
HTTP Status Codes
HTTP 400: Bad Request
Error ID
Error Category
Message
Long Message
Domain
1002
REQUEST
Missing access token
Access token is missing in the Authorization HTTP request header.
OAuth
1003
REQUEST
"Token type in the Authorization header is invalid:" + scheme
"Token type in the Authorization header is invalid:" plus scheme
OAuth
2004
REQUEST
Invalid request
Request has errors. For help, see the documentation for this API.
ACCESS
3001
REQUEST
Request rejected
ROUTING
3002
REQUEST
Malformed request
The request has errors. For help, see the documentation for this API.
ROUTING
HTTP 200 Status Code
Many errors that would typically be represented as 4xx/5xx in REST are returned as HTTP 200 with error details in the GraphQL response body. Always check for errors[], and note that partial data may be returned.
Response shape (HTTP 200):
- message: human-readable error message
- extensions.errorCode: stable machine-readable code (optional)
- locations and path may be present depending on the error type
Types
- ErrorType
This error type defines the response payload of a GraphQL call. If one or more errors have occurred, information about the error(s) will be returned instead.
dataobject | nullConditionalThe payload of the GraphQL response. This object is returned 'null' when one or more error occurs.
errorsarray of GraphQLErrorConditionalThis array returns a list of one or more errors (and associated metadata) returned by the GraphQL call.
- GraphQLError
This error type defines the details of a Graph QL error, such as the error message, location, path, and extension data.
locationsarray of GraphQLSourceLocationConditionalThe source locations in the request that correspond to this error.