Fully-qualified name of an application, as required in the deplyment descriptor. This value must be structured as ApplicationName.PlatformName.TopDomain. AppID, or fully-qualified name of an application as required in the deployment descriptor. This value must be structured as ApplicationName.PlatformName.TopDomain. 128 login Yes Container for token type. Container for specifying whether a token is passed by reference or by value. login No Container for the certId. The certID is generated by eBay and provided to third parties who use Selling Manager Applications. Third parties use the certId to log into eBay through the EIDP service. 128 login Yes Used to specify whether a token is passed by value or by reference. Applications should expect it to be passed by value, and should pass it by value. Later implementations will allow tokens to be passed by reference, to accomodate lengthy assertions in case there is a need to pass encrypted tokens in URLs. The token is passed by reference. The token is passed by value. Container for the EIDP token. The EIDP token identifying the third-party application. Obtained using the login request. 2000 login Always Reserved for future use. Container for the token base type. Base type for tokens. 1000 authenticate Yes login Always Issuing authority for the token. Value is eBay. 128 authenticate Yes login Always The time and date that the EIDP token expires (typically, 24 hours after issuance). authenticate Yes login Always Base request container for all service operations. Base response container for all service operations. Contains error information associated with the request. Always Information for an error or warning that occurred when eBay processed the request. Conditionally Open eBay version. Always The date and time when eBay processed the request. The time zone of this value is GMT and the format is the ISO 8601 date and time format (YYYY-MM- DDTHH:MM:SS.SSSZ). See Time Values in the eBay Web Services guide for information about this time format and converting to and from the GMT time zone. Always Indicates whether the error is a severe error (causing the request to fail) or an informational error (a warning) that should be communicated to the user. The request was processed successfully, but something occurred that may affect your application or the user. The request that triggered the error was not processed successfully. When a serious application-level error occurs, the error is returned instead of the business data. The request that triggered the error was processed successfully but with some warnings. The request that triggered the error was processed successfully but with some warnings. ErrorMessage to indicate any Error/Warning occured as part of service call. Any run time error will not be reported here, but will be reported aspart of soap fault. ActivityProfile about a single error. Conditionally This represents error details. 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. Conditionally Name of the domain in which the error occurred. <dl> <lh> Domains include: </lh> <dt> Marketplace </dt> <dd> A business or validation error occurred for the UserProfile Service. </dd> <dt> SOA </dt> <dd> An exception occurred in the Service Oriented Architecture (SOA) framework. </dd> </dl> Conditionally Indicates whether the error caused the request to fail (Error) or not (Warning). <br><br> 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. <br><br> 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. <br><br> 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. Conditionally There are three categories of errors: request errors, application errors, and system errors. Conditionally A detailed description of the condition that resulted in the error. Conditionally Name of the subdomain in which the error occurred. <dl> <lh> Subdomains include: </lh> <dt> UserProfile </dt> <dd> The error is specific to the UserProfile service. </dd> <dt> MarketplaceCommon </dt> <dd> The error is common to all Marketplace services. </dd> </dl> Conditionally Unique identifier for an exception associated with an error. Conditionally 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. Conditionally Contextual information associated with an error. The name of the parameter in the list of parameter types returned within the error type. Conditionally Indicates whether the error is a severe error (causing the request to fail) or an informational error (a warning) that should be communicated to the user. The request that triggered the error was not processed successfully. When a serious application-level error occurs, the error is returned instead of the business data. The request was processed successfully, but something occurred that may affect your application or the user. For example, eBay may have changed a value the user sent in. In this case, eBay returns a normal, successful response and also returns the warning. There are three categories of error: request errors, application errors, and system errors. Request and application errors are caused primarily by invalid data passed in the request. System errors are caused primarily by application failures and cannot be corrected by changing request values. Indicates that an error has occurred on the eBay system side, such as a database or server down. An application 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. An error occurred due to a problem with the request, such as missing or invalid fields. The problem must be corrected before the request can be made again. If the problem is due to something in the application (such as a missing required field), the application must be changed. Once the problem in the application or data is resolved, resend the corrected request to eBay. An error occurred due to a problem with the request, such as invalid or missing data. The problem must be corrected before the request can be made again. If the problem is a result of end-user data, the application must alert the end-user to the problem and provide the means for the end-user to correct the data. Once the problem in the data is resolved, resend the request to eBay with the corrected data. Requests authentication of an EIDP token sent to your application. In addition to the token to be validated, you include your application identity and token in the HTTP header with this request.

Requests authentication of an EIDP token sent to your application.

The EIDP token to be validated. The EIDP token is included in the HTTP header to validate calls from your application to eBay, such as OEAIS service operations. authenticate Yes Response container for Authenticate operation in the EIDP service. Internal use only. Contains the values of the identity assertions used in the login call. login Yes Contains the values of the identity assertion, usually a DevID, used in the login call. login Yes Specifies which identity assertion is used in the login call. For example, DevID. login Yes Container for the identity assertions used in the login call. login Yes Container for the identity assertions used in the login call. login Yes Requests an EIDP token, which will enable your application to make Selling Manager Application calls and to authenticate incoming calls from the eBay.

Requests an EIDP token.

Specifies the type of credentials offered in the login request. login Yes Specifies whether acceptance will be based on a token passed by value or by reference. login Yes The identity assertions submitted at login include CertID and AppID. login Yes Response container for login operation in the EIDP service. Container for EIDP token, returned in the login response. This token accompanies all subsequent calls made to eBay by Selling Manager applications. login Always 1.0.0