ErrorData
This represents error details.

Types that use ErrorData:

Calls that use one or more fields of ErrorData:

Fields

category ( ErrorCategory )
domain ( string )
errorId ( long )
exceptionId ( token )
message ( string )
parameter ( ErrorParameter (string) )
severity ( ErrorSeverity )
subdomain ( string )

category ( see ErrorCategory for possible values ) [1]
There are three categories of errors: request errors, application errors, and system errors.
See the Field Index to learn which calls use category.

domain ( string ) [1]
Name of the domain upon which the error occurred.
Domains include:
Marketplace
A business or validation error occurred for the UserProfile Service.
SOA
An exception occurred in the Service Oriented Architecture (SOA) framework.
See the Field Index to learn which calls use domain.

errorId ( long ) [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 errorId.

exceptionId ( token ) [0..1]
Unique identifier for an exception associated with an error.
See the Field Index to learn which calls use exceptionId.

message ( string ) [1]
A detailed description of the condition that resulted in the error.
See the Field Index to learn which calls use message.

parameter ( ErrorParameter (string) ) [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.
See the Field Index to learn which calls use parameter.

severity ( see ErrorSeverity for possible values ) [1]
Indicates whether the error caused the request to fail (Error) or not (Warning).

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 severity.

subdomain ( string ) [0..1]
Name of the subdomain upon which the error occurred. Subdomains include the following: UserProfile (in which the error is specific to the UserProfile service) and MarketplaceCommon (in which the error is common to all Marketplace services).
See the Field Index to learn which calls use subdomain.

© 2010 eBay, Inc. All rights reserved. This documentation and the API may only be used in accordance with the eBay Developers Program and API License Agreement.