ErrorType

These are request errors (as opposed to system errors) that occur due to problems with business-level data (e.g., an invalid combination of arguments) that the application passed in.

Types that use ErrorType:

Calls that use one or more fields of ErrorType:

Fields

ErrorClassification ( ErrorClassificationCodeType )
ErrorCode ( token )
ErrorParameters ( ErrorParameterType )
LongMessage ( string )
SeverityCode ( SeverityCodeType )
ShortMessage ( string )
UserDisplayHint

ErrorClassification ( see ErrorClassificationCodeType for possible values ) [0..1]
API errors are divided between two classes: system errors and request errors.
See the Field Index to learn which calls use ErrorClassification.

ErrorCode ( token ) [0..1]
A unique code that identifies the particular error condition that occurred. Your application can use error codes as identifiers in your customized error-handling algorithms.
See the Field Index to learn which calls use ErrorCode.

ErrorParameters ( ErrorParameterType ) [0..*]
Some warning and error messages return one or more variables that contain contextual information about the error. This is often the field or value that triggered the error. You can usually predict where these will occur by looking at the "replaceable_value" indicators in our Errors by Number page.
See the Field Index to learn which calls use ErrorParameters.

LongMessage ( string ) [0..1]
A more detailed description of the condition that raised the error.
See the Field Index to learn which calls use LongMessage.

SeverityCode ( see SeverityCodeType for possible values ) [0..1]
Indicates whether the error caused the request to fail.

If the request fails and the source of the problem is within the application (such as a missing required element), please change the application before you retry the request. If the problem is due to end-user input data, please alert the end-user to the problem and provide the means for them to correct the data. Once the problem in the application or data is resolved, you can attempt to re-send the request to eBay.

If the source of the problem is on eBay's side, you can retry the request as-is a reasonable number of times (eBay recommends twice). If the error persists, contact Developer Technical Support. Once the problem has been resolved, the request may be resent in its original form.

When a warning occurs, the error is returned in addition to the business data. In this case, you do not need to retry the request (as the original request was successful). However, depending on the cause or nature of the warning, you might need to contact either the end user or eBay to effect a long term solution to the problem to prevent it from reoccurring in the future.
See the Field Index to learn which calls use SeverityCode.

ShortMessage ( string ) [0..1]
A brief description of the condition that raised the error.
See the Field Index to learn which calls use ShortMessage.

UserDisplayHint
Not used by any call.

Copyright © 2007–2012 eBay, Inc. All rights reserved. This documentation and the API may only be used in accordance with the eBay Developer Network and API License Agreement.