eBay Resolution Case Management APIVersion 1.3.0
 

getUserCases

Note: All methods of the Resolution Case Management API will be decommisioned on June 5, 2023. This API is now out of synch with case management flows on eBay, so all users should make plans to migrate to the REST-based Post-Order API. In the Post-Order API, the Search Cases method can be used as an alternative to the getUserCases call.

This call retrieves all disputes and cases in which the user is involved as a buyer or seller. This includes all cases opened by buyers through the eBay Resolution Center, and Unpaid Item disputes or mutual Cancel Transaction agreements created through the AddDispute call of the Trading API or through the Resolution Center. Currently, the eBay Buyer Protection program and supporting Resolution Center exist only on the US, UK, and DE sites.

Note: Users of this call should start using the GET /post-order/v2/casemanagement/{caseId} call of the Post-Order API instead.

Users of this call have the option of filtering by case status, case type, or date ranges. Users can also input an eBay item ID (and optionally a transaction ID) to return cases related to a specific item listing or order line item. The filter types are described below.

Item Filter

By using the itemFilter field, the user can find cases associated with a particular item listing by passing in the eBay Item ID. In fact, the user can even "drill-down" to a specific order line item by passing in the transactionID as well. If the transactionID field is used, a case associated with a specific order line item is returned.

Date Range Filter

By using the creationDateRangeFilter field, the user can retrieve cases with creation dates within a specified date range. The fromDate and toDate must be dates in the past. The fromDate can be set back to 18 months in the past. The maximum period of time (or time span) that can be specified using the fromDate and toDate fields is 90 days. So, if a user wanted to return all user cases from the last 18 months, it would require six separate calls that specified different 90-day intervals. If the toDate field is omitted, all cases created from the fromDate up to the present (system date) are returned. However, if the time span between the fromDate and the system date is longer than 90 days, all cases created starting from the fromDate to 90 days after the fromDate are returned.

Case Type Filter

By using the caseTypeFilter field, the user can retrieve cases of a specific case type. For example, a user may only want to return only eBay Buyer Protection Item Not Received or Significantly Not As Described cases. Perhaps they know that there is a Significantly Not As Described case against them, but they do not know the system in which the case was filed. In that case, they would want to use EBP_SNAD as arguments in the caseTypeFilter field. The caseTypeFilter uses Boolean OR logic, which means all matching case types specified in caseTypeFilter field are returned.

Case Status Filter

By using the caseStatusFilter field, the user can retrieve cases in a specific state. For example, a user may only want to return opened cases. Or maybe they only want to return closed cases. Perhaps they want to know which cases require an action on their part. In that case, they would want to use MY_RESPONSE_DUE and MY_PAYMENT_DUE as arguments in the caseStatusFilter field. This caseStatusFilter field uses Boolean OR logic, which means all matching case statuses specified in caseStatusFilter field are returned.

Common Errors for getUserCases Call

The following are some common errors that can occur when using filtering with the getUserCases call:

Paginating Search Results

Use paginationInput and its child elements to break the items matching the search criteria down into smaller subsets, or "pages" of data. The paginationInput.entriesPerPage field specifies the maximum number of items to return for any given request. The paginationInput.pageNumber field specifies which "page" of data to return in the current call. An XML snippet is shown below:

<getUserCasesRequest>
  <paginationInput>
    <entriesPerPage>10</entriesPerPage>
    <pageNumber>2</pageNumber>
  </paginationInput>
</getUserCasesRequest>

Sample pagination input (HTTP GET)

...&paginationInput.entriesPerPage=10&paginationInput.pageNumber=2...

There are corresponding fields in the response for paginating data. The paginationOutput.totalEntries field indicates the total number of items matching the input search criteria that could be returned (with one or multiple calls). If the value specified in paginationInput.entriesPerPage is less than that returned in paginationOutput.totalEntries, then it will take more than one call to retrieve all of the matching items. The paginationOutput.totalPages property indicates the total number of calls that would be required to retrieve all of the matching items. The value specified in the paginationInput.pageNumber field of search requests indicates where in the sequence of multiple calls the application is, relative to the number returned in paginationInput.totalPages.

Sample pagination output (XML)

<paginationOutput>
  <pageNumber>2</pageNumber>
  <entriesPerPage>10</entriesPerPage>
  <totalPages>21</totalPages>
  <totalEntries>207</totalEntries>
</paginationOutput>

The paginationOutput.entriesPerPage field indicates the maximum number of items that can be returned in a response. The count attribute for the searchResult field indicates the actual number of items returned in the response. The count value will typically match the entriesPerPage value, except when your search returns fewer results than the value specified in entriesPerPage or when retrieving the last page of results.

Related Information

See also the reference documentation for this call:



Input Output Samples Change History

Input

See also Samples.

The box below lists all fields that could be included in the call request. To learn more about an individual field or its type, click its name in the box (or scroll down to find it in the table below the box).

See also the Deprecated Objects link above. Fields presented in this color are deprecated, and fields presented in this color are (or soon will be) non-operational. 

<?xml version="1.0" encoding="utf-8"?>
<getUserCasesRequest xmlns="http://www.ebay.com/marketplace/resolution/v1/services">
  <!-- Call-specific Input Fields -->
  <caseStatusFilter> CaseStatusFilterType
    <caseStatus> CaseStatusInputType </caseStatus>
    <!-- ... more caseStatus values allowed here ... -->
  </caseStatusFilter>
  <caseTypeFilter> CaseTypeFilterType
    <caseType> CaseType </caseType>
    <!-- ... more caseType values allowed here ... -->
  </caseTypeFilter>
  <creationDateRangeFilter> DateRangeFilterType
    <fromDate> dateTime </fromDate>
    <toDate> dateTime </toDate>
  </creationDateRangeFilter>
  <itemFilter> ItemFilterType
    <itemId> string </itemId>
    <transactionId> string </transactionId>
  </itemFilter>
  <paginationInput> PaginationInput
    <entriesPerPage> int </entriesPerPage>
    <pageNumber> int </pageNumber>
  </paginationInput>
  <sortOrder> CaseSortOrderType </sortOrder>
</getUserCasesRequest>
Argument Type Occurrence Meaning
caseStatusFilter CaseStatusFilterType Optional Container element for case status filters. One or more caseStatus elements may be used. The caseStatusFilter field uses Boolean OR logic, which means all specified and matching case statuses are returned. There are six possible case statuses to retrieve.
caseStatusFilter.caseStatus CaseStatusInputType Conditional,
repeatable: [1..*]		 The case status to search for is specified in this field. At least one caseStatus field must be used if caseStatusFilter is included in the input.

Applicable values: See caseStatus.
caseTypeFilter CaseTypeFilterType Optional Container element for case type filters. One or more caseType elements may be used. The caseTypeFilter field uses Boolean OR logic, which means all specified and matching case types are returned. There are nine possible case types to retrieve.
caseTypeFilter.caseType CaseType Conditional,
repeatable: [1..*]		 The type of case to search for is specified in this field. At least one caseType field must be used if caseTypeFilter is included in the input.

Applicable values:

CANCEL_TRANSACTION
A mutually agreed upon transaction withdrawal case initiated by the seller for an unpaid item, and created through the Resolution Center or with the AddDispute Trading API call.
EBP_INR
An Item Not Received case opened by a buyer in the Resolution Center.
EBP_SNAD
A Significantly Not As Described case opened by a buyer in the Resolution Center.
UPI
An Unpaid Item case created by a seller through the Resolution Center or with the AddDispute Trading API call. Unpaid Item disputes are also created automatically if the seller has the Unpaid Item Assistant mechanism turned on.
creationDateRangeFilter DateRangeFilterType Optional This filter restricts results to cases created within a specified date range. The specified date range is inclusive. The maximum date range that can be specified with this filter is 90 days. Cases with creation dates dating back more than 18 months cannot be returned. If you want to return cases for a period longer than 90 days, you have to make multiple getUserCases calls using this filter and specifying different date ranges in each subsequent call.
creationDateRangeFilter
  .fromDate 		dateTime Conditional The starting date for the date range. The fromDate must be older than the toDate, and it cannot be set back more than 18 months in the past.
creationDateRangeFilter.toDate dateTime Optional The ending date for the date range. The toDate must be more recent than the fromDate. This field is optional. If it is omitted, all cases created from the fromDate up to the present (system date) are returned, unless the range specified by the fromDate and the present date is greater than 90 days, in which case the toDate defaults to 90 days forward from the fromDate.
itemFilter ItemFilterType Optional This filter restricts results to cases filed against a specific item or a specific transaction involving the same item. If the itemFilter.transactionId field is specified, a maximum of one case will be returned since there can only be one case per transaction.
itemFilter.itemId string Conditional The unique identifier for an eBay item listing. All cases filed against this itemId are returned.
Max length: 19.
itemFilter.transactionId string Optional The unique identifier for an eBay transaction. The transactionId must match the specified itemId or an error is returned. If a transactionId is specified, only one case, that matches the itemId and the transactionId, may be returned.
Max length: 19.
paginationInput PaginationInput Optional Controls the pagination of the result set, including the number of cases returned per page and the page number you want returned in the output.
paginationInput.entriesPerPage int Conditional Specifies the number of cases to return in one page of results in the getUserCases response. This value, along with the number of cases that match the input criteria in the getUserCases request, will determine how many result pages are returned.
Min: 1. Max: 200. Default: 200.
paginationInput.pageNumber int Conditional Specifies which page of case results to return in the response. The total number of result pages is determined by the total number of cases matching the input criteria divided by the number of cases to display in each page. The total number of cases is returned in the paginationOutput.totalEntries field of the getUserCases response. The cases to display per page is set with the paginationInput.entriesPerPage field. If there are multiple result pages returned, subsequent calls can be made with all of the same input parameters, except for the pageNumber field, which is incremented by a value of 1 each time so that each subsequent page may be viewed and/or handled.
Min: 1. Max: 100. Default: 1.
sortOrder CaseSortOrderType Optional Sorts the results based on creation date or case status, in ascending or descending order. Results are returned based on case creation date in ascending order if this field is not included in the request.
Default: CREATION_DATE_ASCENDING.

Applicable values:

CASE_STATUS_ASCENDING
Cases are sorted based on the status of the case in ascending order .
CASE_STATUS_DESCENDING
Cases are sorted based on the status of the case in descending order.
CREATION_DATE_ASCENDING
Cases are sorted based on creation date in ascending order.
CREATION_DATE_DESCENDING
Cases are sorted based on creation date in descending order.



Input Output Samples Change History

Output

See also Samples.

The box below lists all fields that might be returned in the response. To learn more about an individual field or its type, click its name in the box (or scroll down to find it in the table below the box).

See also the Deprecated Objects link above. Fields presented in this color are deprecated, and fields presented in this color are not returned (or soon will not be returned) or are not operational (or soon will be non-operational).

<?xml version="1.0" encoding="utf-8"?>
<getUserCasesResponse xmlns="http://www.ebay.com/marketplace/resolution/v1/services">
  <!-- Call-specific Output Fields -->
  <cases> CaseArrayType
    <caseSummary> CaseSummaryType
      <caseAmount> Amount (double) </caseAmount>
      <caseId> CaseIdType
        <id> string </id>
        <type> CaseType </type>
      </caseId>
      <caseQuantity> int </caseQuantity>
      <creationDate> dateTime </creationDate>
      <item> ItemType
        <itemId> string </itemId>
        <itemTitle> string </itemTitle>
        <transactionId> string </transactionId>
      </item>
      <lastModifiedDate> dateTime </lastModifiedDate>
      <otherParty> CaseUserType
        <role> CaseUserRoleType </role>
        <userId> string </userId>
      </otherParty>
      <respondByDate> dateTime </respondByDate>
      <status> CaseStatusType
        <cancelTransactionStatus> CancelTransactionCaseStatusType </cancelTransactionStatus>
        <EBPINRStatus> EBPINRCaseStatusType </EBPINRStatus>
        <EBPSNADStatus> EBPSNADCaseStatusType </EBPSNADStatus>
        <INRStatus> INRCaseStatusType </INRStatus>
        <PaypalINRStatus> PaypalINRCaseStatusType </PaypalINRStatus>
        <returnStatus> ReturnCaseStatusType </returnStatus>
        <SNADStatus> SNADCaseStatusType </SNADStatus>
        <UPIStatus> UPICaseStatusType </UPIStatus>
      </status>
      <user> CaseUserType
        <role> CaseUserRoleType </role>
        <userId> string </userId>
      </user>
    </caseSummary>
    <!-- ... more caseSummary nodes allowed here ... -->
  </cases>
  <paginationOutput> PaginationOutput
    <entriesPerPage> int </entriesPerPage>
    <pageNumber> int </pageNumber>
    <totalEntries> int </totalEntries>
    <totalPages> int </totalPages>
  </paginationOutput>
  <!-- Standard Output Fields -->
  <ack> AckValue </ack>
  <errorMessage> ErrorMessage
    <error> ErrorData
      <category> ErrorCategory </category>
      <domain> string </domain>
      <errorId> long </errorId>
      <exceptionId> token </exceptionId>
      <message> string </message>
      <parameter name="string"> ErrorParameter (string) </parameter>
      <!-- ... more parameter values allowed here ... -->
      <severity> ErrorSeverity </severity>
      <subdomain> string </subdomain>
    </error>
    <!-- ... more error nodes allowed here ... -->
  </errorMessage>
  <timestamp> dateTime </timestamp>
  <version> string </version>
</getUserCasesResponse>
Return Value Type Occurrence Meaning
Call-specific Output Fields [Jump to standard fields]
cases CaseArrayType Always Root container for all cases in which the caller is involved in either as the seller or buyer. There can be one or more caseSummary nodes under the cases container.
cases.caseSummary CaseSummaryType Always,
repeatable: [1..*]		 Container consisting of summary information for a case. One caseSummary container will be returned for each case that matches the input criteria.
cases.caseSummary.caseAmount Amount (double) Always The amount of money involved in the case.
cases.caseSummary.caseId CaseIdType Always This container identifies a dispute case between the buyer and seller.
cases.caseSummary.caseId.id string Always Unique identifier of the case. The caseId.id values are returned in the caseSummary container in the getUserCases and getEBPCaseDetail calls.
Max length: 38.
cases.caseSummary.caseId.type CaseType Always eBay case type. This enumeration value indicates the eBay case type. For all Resolution Case Management calls except getUserCases, only EBP_INR and EBP_SNAD are applicable caseType values.

Applicable values:

CANCEL_TRANSACTION
A mutually agreed upon transaction withdrawal case initiated by the seller for an unpaid item, and created through the Resolution Center or with the AddDispute Trading API call.
EBP_INR
An Item Not Received case opened by a buyer in the Resolution Center.
EBP_SNAD
A Significantly Not As Described case opened by a buyer in the Resolution Center.
UPI
An Unpaid Item case created by a seller through the Resolution Center or with the AddDispute Trading API call. Unpaid Item disputes are also created automatically if the seller has the Unpaid Item Assistant mechanism turned on.

Code so that your app gracefully handles any future changes to this list.
cases.caseSummary.caseQuantity int Always This value indicates the quantity of items in the transaction related to the case. This value is usually '1' unless a buyer bought multiple items at the same time from the same fixed-priced listing.
Min: 1.
cases.caseSummary.creationDate dateTime Always Timestamp indicating the date that the case was opened.
cases.caseSummary.item ItemType Always A container consisting of details on the item associated with the case.
cases.caseSummary.item.itemId string Always The unique identifier for the eBay item listing involved in the case.
Max length: 19.
cases.caseSummary.item
  .itemTitle 		string Always The title of the item listing involved in the case.
Max length: 55.
cases.caseSummary.item
  .transactionId 		string Always The unique identifier for the eBay transaction being disputed in the case.
cases.caseSummary
  .lastModifiedDate 		dateTime Always Timestamp indicating the date on which the case was last modified. A case is considered modified if the status value changes.
cases.caseSummary.otherParty CaseUserType Always The role (e.g. buyer, seller) of the other party involved in the case.
cases.caseSummary.otherParty
  .role 		CaseUserRoleType Always The user's role in the eBay Buyer Protection case.

Applicable values:

BUYER
The user's role in the case is buyer.
EBAY
A representative of eBay involved in mediating the case.
OTHER
The user's role in the case is classified as 'other'.
SELLER
The user's role in the case is seller.

Code so that your app gracefully handles any future changes to this list.
cases.caseSummary.otherParty
  .userId 		string Conditionally The eBay user ID for the user involved in the case.
cases.caseSummary
  .respondByDate 		dateTime Conditionally The date by which the next action in the case must be made either by the user (caller) or other party involved in the case. This field is only returned if a response or payment is due from the user or the other party involved in the case.
cases.caseSummary.status CaseStatusType Always Container holding the status of the case. The field appearing under this container is dependent on the case type. For getEBPCaseDetail, only the EBPINRStatus or EBPSNADStatus fields may be returned under the caseSummary.status field.
cases.caseSummary.status
  .cancelTransactionStatus 		CancelTransactionCaseStatusType Conditionally The current status of a cancelled transaction case opened by the seller in the Resolution Center or with the AddDispute call of the Trading API.

Applicable values: See cancelTransactionStatus.
Code so that your app gracefully handles any future changes to this list.
cases.caseSummary.status
  .EBPINRStatus 		EBPINRCaseStatusType Conditionally The current status of an Item Not Received case opened by the buyer in the Resolution Center.

Applicable values: See EBPINRStatus.
Code so that your app gracefully handles any future changes to this list.
cases.caseSummary.status
  .EBPSNADStatus 		EBPSNADCaseStatusType Conditionally The current status of a Significantly Not As Described case opened by the buyer in the Resolution Center.

Applicable values: See EBPSNADStatus.
Code so that your app gracefully handles any future changes to this list.
cases.caseSummary.status
  .INRStatus 		INRCaseStatusType Conditionally

This field is deprecated. Do not use.



Applicable values: See INRStatus.
Code so that your app gracefully handles any future changes to this list.
cases.caseSummary.status
  .PaypalINRStatus 		PaypalINRCaseStatusType Conditionally Deprecated as of version 1.3.0. No longer functional.

This field is deprecated. Do not use.



Applicable values:

CLOSED
A closed PayPal Item Not Received case.
MY_RESPONSE_DUE
A response from the user in the PayPal Item Not Received case is due.
OPEN
An open PayPal Item Not Received case.
OTHER
The status of the PayPal Item Not Received case is 'other'.
OTHER_PARTY_RESPONSE_DUE
A response from the other party in the PayPal Item Not Received case is due.

Code so that your app gracefully handles any future changes to this list.
Deprecation version: 1.3.0. See also Deprecated Objects.
cases.caseSummary.status
  .returnStatus 		ReturnCaseStatusType Conditionally The current status of a returned item case.

Applicable values: See returnStatus.
Code so that your app gracefully handles any future changes to this list.
cases.caseSummary.status
  .SNADStatus 		SNADCaseStatusType Conditionally Deprecated as of version 1.3.0. No longer functional.

This field is deprecated. Do not use.



Applicable values: See SNADStatus.
Code so that your app gracefully handles any future changes to this list.
Deprecation version: 1.3.0. See also Deprecated Objects.
cases.caseSummary.status
  .UPIStatus 		UPICaseStatusType Conditionally The current status of an Unpaid Item case opened by the seller in the Resolution Center or with the AddDispute call of the Trading API.

Applicable values: See UPIStatus.
Code so that your app gracefully handles any future changes to this list.
cases.caseSummary.user CaseUserType Always The role (e.g. buyer, seller) of the user making the call.
cases.caseSummary.user.role CaseUserRoleType Always The user's role in the eBay Buyer Protection case.

Applicable values:

BUYER
The user's role in the case is buyer.
EBAY
A representative of eBay involved in mediating the case.
OTHER
The user's role in the case is classified as 'other'.
SELLER
The user's role in the case is seller.

Code so that your app gracefully handles any future changes to this list.
cases.caseSummary.user.userId string Conditionally The eBay user ID for the user involved in the case.
paginationOutput PaginationOutput Always Pagination container consisting of fields that indicate the total number of pages and cases that match the input criteria, the number of cases per page, and the current page number being viewed. See the corresponding field descriptions for more information on the child elements of paginationOutput.
paginationOutput
  .entriesPerPage 		int Always The number of cases returned per page. This value is set in the paginationInput.entriesPerPage field in the getUserCases request.
Min: 1. Max: 100. Default: 1.
paginationOutput.pageNumber int Always The page number currently being viewed. The total number of result pages is shown in the totalPages field. If totalPages is more than 1, multiple getUserCases calls must be made to view all case results, with the paginationInput.pageNumber value being incremented by 1 in each subsequent call.
Min: 1. Max: 200. Default: 1.
paginationOutput.totalEntries int Always This value indicates the total number of cases that exist based on the current input criteria. Once this value is known, the caller may want to considering tweaking the paginationInput fields and making another call.
paginationOutput.totalPages int Always This value indicates the total number of result pages that exist based on the current input criteria, including the paginationInput fields. If totalPages is more than 1, multiple getUserCases calls must be made to view all case results, with the paginationInput.pageNumber value being incremented by 1 in each subsequent call.
Standard Output Fields  
ack AckValue Always

Applicable values:

Failure
eBay encountered a fatal error during the processing of the request, causing the request to fail. When a serious application-level error occurs, the error is returned instead of the business data.
PartialFailure
eBay successfully processed the request, but one or more non-fatal errors occurred during the processing. Inspect the message details and resolve any problems before resubmitting the request.
Success
eBay successfully processed the request and the business data is returned in the response. Note that it is possible for a response to return Success, but still not contain the expected data in the result.
Warning
The request that triggered the error was processed successfully but with one or more warnings.

Code so that your app gracefully handles any future changes to this list.
errorMessage ErrorMessage Conditionally Information for an error or warning that occurred when eBay processed the request. This field is not returned if the ack value is Success.
errorMessage.error ErrorData Conditionally,
repeatable: [0..*]		 Details about a single error.
errorMessage.error.category ErrorCategory Conditionally There are three categories of errors: request errors, application errors, and system errors.

Applicable values:

Application
An error occurred due to a problem with the request, with the most likely source being the application sending the request. For example, the request is missing a required data element or it contains an invalid field. The problem must be corrected before the request can be resent. Inspect the error message to find the cause of the problem. If the problem is due to an application error, modify the application and resend the request. If the error is due to invalid data, the source of the data must be corrected before you resend the resend request to eBay.
Request
An error occurred due to a problem with the request, with the most likely source being missing or invalid data in the request. The problem must be corrected before the request can be retried. Inspect the error message to find the cause of the problem. If the problem is a result of end-user data, alert the end-user to the problem and provide the means for them to correct the problem. Once the problem is resolved, resend the request to eBay.
System
Indicates that an error has occurred on the eBay system side. For example, a database or server could be down. Inspect the error message to find the cause of the problem. If the problem is on the eBay side, an application can retry the request 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.

Code so that your app gracefully handles any future changes to this list.
errorMessage.error.domain string Conditionally Name of the domain in which the error occurred.
errorMessage.error.errorId long Conditionally 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.
errorMessage.error.exceptionId token Conditionally Unique identifier for an exception associated with an error.
errorMessage.error.message string Conditionally A detailed description of the condition that caused the error.
errorMessage.error.parameter ErrorParameter (string) Conditionally,
repeatable: [0..*]		 Various 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.
errorMessage.error.parameter
  [ attribute name ]		 string Conditionally Various 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.
errorMessage.error.severity ErrorSeverity Conditionally Indicates whether the reported problem is fatal (an error) or is less- severe (a warning). Review the error message details for information on the cause.

If the request fails and the application is the source of the error (for example, a required element is missing), update the application before you retry the request. If the problem is due to incorrect user data, 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, re-send the request to eBay.

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

If a warning occurs, warning information is returned in addition to the business data. Normally, you do not need to resend the request (as the original request was successful). However, depending on the cause of the warning, you might need to contact the end user, or eBay, to effect a long term solution to the problem.

Applicable values:

Error
eBay encountered a fatal error during the processing of the request, causing the request to fail. When eBay encounters an error, it returns error data instead of the requested business data. Inspect the error details and resolve the problem before resubmitting the request.
Warning
The request was successfully processed, but eBay encountered a non-fatal error during the processing that could affect the data returned. For example, eBay might have changed the value of an input field. In this case, eBay returns a successful response, but it also returns a warning. For best results, requests should return without warnings. Inspect the warning details and resolve the problem before resubmitting the request.

Code so that your app gracefully handles any future changes to this list.
errorMessage.error.subdomain string Conditionally Name of the subdomain in which the error occurred.
timestamp dateTime Always This value represents 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.
version string Always The version of the response payload schema. Indicates the version of the schema that eBay used to process the request.



Input Output Samples Change History

Samples

New to making API calls? Please see Making a Call.

Note: Some item IDs, user IDs, or other data in these samples might no longer be active on eBay. If necessary, you can substitute current eBay data in your requests.

Available samples:

Sample: Basic Call

Retrieves all user cases created in the last 90 days in which the caller is involved.

Description

The default behavior of this basic call is to return all user cases created in the last 90 days. This includes all cases created in the eBP system.

There is a case summary node returned for each case. Each case summary node includes the case ID and case type, the caller's role in the case (Buyer in this sample), the user ID and role of the other party in the case (Seller in this sample), the current status of the case, and the item and transaction IDs. The caller must be authenticated to make the call.

Since this is the basic call with no input parameters, this call will generally only fail if the user is not authenticated or if there are data entry/syntax errors in the call. If the caller is/was not involved in any cases created in the last 90 days, an error message stating No data found is returned.

For Unpaid Item cases (caseId.type=UPI), the corresponding caseId.id value can be passed into the DisputeID field of the Trading API's GetDispute call to get more information on the case.

For the EBP_INR and EBP_SNAD case types, take the caseId.id value and pass it into the caseId.id field of the getEBPCaseDetail call.

Input

A buyer with a user name of m********7 wants to find all cases created in the last 90 days in which he/she is involved, regardless of case type or current status.

SOAP format. Also available is the XML equivalent.

<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:ser="http://www.ebay.com/marketplace/resolution/v1/services">
  <soap:Header/>
   <soap:Body>
      <ser:getUserCasesRequest>  
      </ser:getUserCasesRequest>
   </soap:Body>
</soap:Envelope>

Output

There are six user cases returned in the response, including three UPI cases, two EBP_SNAD cases, and one EBP_INR case. m********7 is in the role of buyer in each case. m********7's payment is due in half of the cases, and a response is due in the other half of the cases. To find out more information about any of the UPI cases, take the caseId.id value and pass it into the DisputeID field of the Trading API's GetDispute call. To find out more information about any of the EBP cases, take the caseId.id value and pass it into the caseId.id field of the getEBPCaseDetail call.

SOAP format. Also available is the XML equivalent.

<?xml version="1.0" encoding="utf-8"?>
<getUserCasesResponse xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:ser="http://www.ebay.com/marketplace/resolution/v1/services">
  <ack>Success</ack>
  <version>1.0.0</version>
  <timestamp>2010-09-07T16:56:42.911Z</timestamp>
  <cases>
    <caseSummary>
      <caseId>
        <id>4********3</id>
        <type>UPI</type>
      </caseId>
      <user>
        <userId>m********7</userId>
        <role>BUYER</role>
      </user>
      <otherParty>
        <userId>m********2</userId>
        <role>SELLER</role>
      </otherParty>
      <status>
        <UPIStatus>MY_PAYMENT_DUE</UPIStatus>
      </status>
      <item>
        <itemId>2********5</itemId>
        <itemTitle>8/3snad</itemTitle>
        <transactionId>7********2</transactionId>
      </item>
      <caseQuantity>1</caseQuantity>
      <caseAmount currencyId="USD">1.01</caseAmount>
      <respondByDate>2010-10-02T00:05:23.000Z</respondByDate>
      <creationDate>2010-08-17T00:05:18.000Z</creationDate>
      <lastModifiedDate>2010-08-17T00:05:18.000Z</lastModifiedDate>
    </caseSummary>
    <caseSummary>
      <caseId>
        <id>4********4</id>
        <type>UPI</type>
      </caseId>
      <user>
        <userId>m********7</userId>
        <role>BUYER</role>
      </user>
      <otherParty>
        <userId>m********2</userId>
        <role>SELLER</role>
      </otherParty>
      <status>
        <UPIStatus>MY_PAYMENT_DUE</UPIStatus>
      </status>
      <item>
        <itemId>2********5</itemId>
        <itemTitle>8/4test checkout</itemTitle>
        <transactionId>7********2</transactionId>
      </item>
      <caseQuantity>1</caseQuantity>
      <caseAmount currencyId="USD">1.01</caseAmount>
      <respondByDate>2010-10-03T22:01:15.000Z</respondByDate>
      <creationDate>2010-08-17T00:06:15.000Z</creationDate>
      <lastModifiedDate>2010-08-17T00:06:15.000Z</lastModifiedDate>
     </caseSummary>
     <caseSummary>
       <caseId>
         <id>4********4</id>
         <type>UPI</type>
       </caseId>
       <user>
         <userId>m********7</userId>
         <role>BUYER</role>
       </user>
       <otherParty>
         <userId>m********2</userId>
         <role>SELLER</role>
       </otherParty>
       <status>
         <UPIStatus>MY_PAYMENT_DUE</UPIStatus>
       </status>
       <item>
         <itemId>2********5</itemId>
         <itemTitle>Laptop</itemTitle>
         <transactionId>7********2</transactionId>
       </item>
       <caseQuantity>1</caseQuantity>
       <caseAmount currencyId="EUR">1.0</caseAmount>
       <respondByDate>2010-10-03T22:32:55.000Z</respondByDate>
       <creationDate>2010-09-05T22:42:16.000Z</creationDate>
       <lastModifiedDate>2010-09-05T22:42:16.000Z</lastModifiedDate>
      </caseSummary>
      <caseSummary>
       <caseId>
         <id>5********2</id>
        <type>EBP_INR</type>
       </caseId>
       <user>
        <userId>m********7</userId>
        <role>BUYER</role>
       </user>
       <otherParty>
        <userId>m********2</userId>
        <role>SELLER</role>
       </otherParty>
       <status>
        <EBPINRStatus>MY_RESPONSE_DUE</EBPINRStatus>
       </status>
       <item>
        <itemId>2********5</itemId>
        <itemTitle>6/28snad</itemTitle>
        <transactionId>7********2</transactionId>
       </item>
       <caseQuantity>1</caseQuantity>
       <caseAmount currencyId="USD">2.01</caseAmount>
       <creationDate>2010-06-28T17:16:52.000Z</creationDate>
       <lastModifiedDate>2010-07-06T12:55:40.000Z</lastModifiedDate>
      </caseSummary>
      <caseSummary>
       <caseId>
         <id>5********8</id>
         <type>EBP_SNAD</type>
       </caseId>
       <user>
         <userId>m********7</userId>
         <role>BUYER</role>
       </user>
       <otherParty>
         <userId>m********2</userId>
         <role>SELLER</role>
       </otherParty>
       <status>
         <EBPSNADStatus>MY_RESPONSE_DUE</EBPSNADStatus>
       </status>
       <item>
         <itemId>2********3</itemId>
         <itemTitle>6/15snad</itemTitle>
         <transactionId>7********2</transactionId>
       </item>
       <caseQuantity>1</caseQuantity>
       <caseAmount currencyId="USD">2.01</caseAmount>
       <creationDate>2010-06-15T23:55:36.000Z</creationDate>
       <lastModifiedDate>2010-06-16T00:01:50.000Z</lastModifiedDate>
      </caseSummary>
      <caseSummary>
       <caseId>
         <id>5********4</id>
         <type>EBP_SNAD</type>
       </caseId>
       <user>
         <userId>m********7</userId>
         <role>BUYER</role>
       </user>
       <otherParty>
         <userId>m********2</userId>
         <role>SELLER</role>
       </otherParty>
       <status>
         <EBPSNADStatus>MY_RESPONSE_DUE</EBPSNADStatus>
       </status>
       <item>
         <itemId>2********5</itemId>
         <itemTitle>Fixed Price Single Quantity</itemTitle>
         <transactionId>7********2</transactionId>
       </item>
       <caseQuantity>1</caseQuantity>
       <caseAmount currencyId="USD">3.0</caseAmount>
       <creationDate>2010-06-14T16:25:21.000Z</creationDate>
       <lastModifiedDate>2010-06-14T16:26:54.000Z</lastModifiedDate>
      </caseSummary>
    </cases>
    <paginationOutput>
      <pageNumber>1</pageNumber>
      <entriesPerPage>200</entriesPerPage>
      <totalPages>1</totalPages>
      <totalEntries>6</totalEntries>
    </paginationOutput>
</getUserCasesResponse>

   Here is the same output in XML format. Note that this does not include standard values.

XML format. Also available is the SOAP equivalent.

<?xml version="1.0" encoding="utf-8"?>
<getUserCasesResponse xmlns:soap="http://www.ebay.com/marketplace/resolution/v1/services">
  <ack>Success</ack>
  <version>1.0.0</version>
  <timestamp>2010-09-07T16:56:42.911Z</timestamp>
  <cases>
    <caseSummary>
      <caseId>
        <id>4********3</id>
        <type>UPI</type>
      </caseId>
      <user>
        <userId>m********7</userId>
        <role>BUYER</role>
      </user>
      <otherParty>
        <userId>m********2</userId>
        <role>SELLER</role>
      </otherParty>
      <status>
        <UPIStatus>MY_PAYMENT_DUE</UPIStatus>
      </status>
      <item>
        <itemId>2********5</itemId>
        <itemTitle>8/3snad</itemTitle>
        <transactionId>7********2</transactionId>
      </item>
      <caseQuantity>1</caseQuantity>
      <caseAmount currencyId="USD">1.01</caseAmount>
      <respondByDate>2010-10-02T00:05:23.000Z</respondByDate>
      <creationDate>2010-08-17T00:05:18.000Z</creationDate>
      <lastModifiedDate>2010-08-17T00:05:18.000Z</lastModifiedDate>
    </caseSummary>
    <caseSummary>
      <caseId>
        <id>4********4</id>
        <type>UPI</type>
      </caseId>
      <user>
        <userId>m********7</userId>
        <role>BUYER</role>
      </user>
      <otherParty>
        <userId>m********2</userId>
        <role>SELLER</role>
      </otherParty>
      <status>
        <UPIStatus>MY_PAYMENT_DUE</UPIStatus>
      </status>
      <item>
        <itemId>2********5</itemId>
        <itemTitle>8/4test checkout</itemTitle>
        <transactionId>7********2</transactionId>
      </item>
      <caseQuantity>1</caseQuantity>
      <caseAmount currencyId="USD">1.01</caseAmount>
      <respondByDate>2010-10-03T22:01:15.000Z</respondByDate>
      <creationDate>2010-08-17T00:06:15.000Z</creationDate>
      <lastModifiedDate>2010-08-17T00:06:15.000Z</lastModifiedDate>
     </caseSummary>
     <caseSummary>
       <caseId>
         <id>4********4</id>
         <type>UPI</type>
       </caseId>
       <user>
         <userId>m********7</userId>
         <role>BUYER</role>
       </user>
       <otherParty>
         <userId>m********2</userId>
         <role>SELLER</role>
       </otherParty>
       <status>
         <UPIStatus>MY_PAYMENT_DUE</UPIStatus>
       </status>
       <item>
         <itemId>2********5</itemId>
         <itemTitle>Laptop</itemTitle>
         <transactionId>7********2</transactionId>
       </item>
       <caseQuantity>1</caseQuantity>
       <caseAmount currencyId="EUR">1.0</caseAmount>
       <respondByDate>2010-10-03T22:32:55.000Z</respondByDate>
       <creationDate>2010-09-05T22:42:16.000Z</creationDate>
       <lastModifiedDate>2010-09-05T22:42:16.000Z</lastModifiedDate>
      </caseSummary>
      <caseSummary>
       <caseId>
         <id>5********2</id>
        <type>EBP_INR</type>
       </caseId>
       <user>
        <userId>m********7</userId>
        <role>BUYER</role>
       </user>
       <otherParty>
        <userId>m********2</userId>
        <role>SELLER</role>
       </otherParty>
       <status>
        <EBPINRStatus>MY_RESPONSE_DUE</EBPINRStatus>
       </status>
       <item>
        <itemId>2********5</itemId>
        <itemTitle>6/28snad</itemTitle>
        <transactionId>7********2</transactionId>
       </item>
       <caseQuantity>1</caseQuantity>
       <caseAmount currencyId="USD">2.01</caseAmount>
       <creationDate>2010-06-28T17:16:52.000Z</creationDate>
       <lastModifiedDate>2010-07-06T12:55:40.000Z</lastModifiedDate>
      </caseSummary>
      <caseSummary>
       <caseId>
         <id>5********8</id>
         <type>EBP_SNAD</type>
       </caseId>
       <user>
         <userId>m********7</userId>
         <role>BUYER</role>
       </user>
       <otherParty>
         <userId>m********2</userId>
         <role>SELLER</role>
       </otherParty>
       <status>
         <EBPSNADStatus>MY_RESPONSE_DUE</EBPSNADStatus>
       </status>
       <item>
         <itemId>2********3</itemId>
         <itemTitle>6/15snad</itemTitle>
         <transactionId>7********2</transactionId>
       </item>
       <caseQuantity>1</caseQuantity>
       <caseAmount currencyId="USD">2.01</caseAmount>
       <creationDate>2010-06-15T23:55:36.000Z</creationDate>
       <lastModifiedDate>2010-06-16T00:01:50.000Z</lastModifiedDate>
      </caseSummary>
      <caseSummary>
       <caseId>
         <id>5********4</id>
         <type>EBP_SNAD</type>
       </caseId>
       <user>
         <userId>m********7</userId>
         <role>BUYER</role>
       </user>
       <otherParty>
         <userId>m********2</userId>
         <role>SELLER</role>
       </otherParty>
       <status>
         <EBPSNADStatus>MY_RESPONSE_DUE</EBPSNADStatus>
       </status>
       <item>
         <itemId>2********5</itemId>
         <itemTitle>Fixed Price Single Quantity</itemTitle>
         <transactionId>7********2</transactionId>
       </item>
       <caseQuantity>1</caseQuantity>
       <caseAmount currencyId="USD">3.0</caseAmount>
       <creationDate>2010-06-14T16:25:21.000Z</creationDate>
       <lastModifiedDate>2010-06-14T16:26:54.000Z</lastModifiedDate>
      </caseSummary>
    </cases>
    <paginationOutput>
      <pageNumber>1</pageNumber>
      <entriesPerPage>200</entriesPerPage>
      <totalPages>1</totalPages>
      <totalEntries>6</totalEntries>
    </paginationOutput>
</getUserCasesResponse>

Back to list of samples

Sample: Retrieving User Cases for a Specific Transaction

A seller wants to retrieve cases created in the last 90 days related to a specific transaction.

Description

This getUserCases call uses the itemFilter field to retrieve user cases related to a specific transaction. The caller uses the itemFilter field to pass in the transactionID of the eBay transaction, as well as the corresponding itemID.

The itemId and transactionId fields must match or an error will be returned. The call may fail if the user is not authenticated or if there are data entry/syntax errors in the call. If no cases match the transactionId, an error message stating No data found is returned.

Input

The caller is a seller named d********1. d********1 wants to retrieve all user cases related to transaction ID 7********9. The itemId and transactionId values are passed in under the itemFilter element.

Output

There is one EBP_SNAD case returned in the response and the status of the EBP_SNAD case is closed. To find out more information about this case, take the caseId.id value and pass it into the caseId.id field of the getEBPCaseDetail call.


Back to list of samples

Sample: Retrieving Closed eBP Cases

A seller wants to retrieve eBP cases created in the last 90 days that have been closed.

Description

This getUserCases call uses the caseTypeFilter and caseStatusFilter fields to retrieve EBP_INR and EBP_SNAD case types that are in the closed state.

The call may fail if the user is not authenticated or if there are data entry/syntax errors in the call. If no cases match the filter criteria, an error message stating No data found is returned.

Input

The caller is a seller named m********1. m********1 wants to retrieve all closed EBP_SNAD and EBP_INR cases from the last 90 days. The caller uses the caseTypeFilter field to pass in the EBP_INR and EBP_SNAD case types and the caseStatusFilter field to pass in the CLOSED status.

Output

There are three closed EBP_INR cases and three closed EBP_SNAD cases that are returned in the response. To find out more information about one of these cases, take the caseId.id value and pass it into the caseId.id field of the getEBPCaseDetail call.


Back to list of samples

Sample: Retrieving Open and Closed EBP_INR Cases

A seller wants to retrieve open and closed EBP_INR cases created in a specified period. The seller wants a maximum of 40 cases returned per call, and wants the cases sorted by creation date in ascending order.

Description

This getUserCases call uses the creationDateRangeFilter, caseTypeFilter and caseStatusFilter fields to retrieve EBP_INR cases created through the eBay system during a specified date range.

The date range specified with the fromDate and toDate cannot be longer than 90 days. The call may fail if the user is not authenticated or if there are data entry/syntax errors in the call. If no cases match the filter criteria, an error message stating No data found is returned.

Input

The caller is a seller named m********r. m********r wants to retrieve all open and closed eBay EBP_INR cases with creation dates between February 18, 2010 and May 18, 2010. The caller uses the creationDateRangeFilter field to specify the date range, the caseTypeFilter field to pass in the EBP_INR case type and the caseStatusFilter field to pass in the CLOSED and OPEN statuses.

The caller also uses the paginationInput field to specify the number of entries per page and the page number to return, as well as the sortOrder field, to sort results by creation date in ascending order.

Output

There were two EBP_INR cases created against the seller during the specified date range, and both are closed. To find out more information about either case, take the caseId.id value and pass it into the DisputeID field of the Trading API's GetDispute call.

The pageNumber and entriesPerPage values in the paginationOutput field reflect the values set in the input, and the two cases are sorted in ascending order according to creation date.


Back to list of samples



Input Output Samples Change History

Change History

Change Date Description
1.0.0
2010-09-17
  • (added) New call.