EndItems
Use this call to explicitly end multiple active item listings before they would ordinarily end (per the listing duration). You can specify up to ten listings to end in a single request.
This call works just like EndItem, the logic and restrictions that apply to EndItem apply equally to EndItems. The only difference is that this call lets you specify an array of EndItemRequestContainer nodes. Each EndItemRequestContainer is like a separate EndItem call, containing ItemID and EndingReason fields.
Normally, item listings end when the specified duration has passed, when a Buy It Now option for a Chinese auction is exercised, or (in the case of multi-item fixed-price listings) when the last item in the listing has been sold. EndItems provides the means for ending multiple listings before any of these natural conditions occur to end the listings.
See Ending Listings Early for details on the effects of ending a listing early, and more on when it is required to specify a reason for ending the listing.
Usage Details
Only the item's seller can use EndItems to end item listings. In the call, specify the item IDs for the active listings you want to end.
For competitive-bid item listings that have bids on them (for example, a bid that meets the minimum reserve price), you must specify an EndingReason value. If you specify SellToHighBidder, the listing ends as a successful auction with winning bidder(s). If you specify a different EndingReason value (such as LostOrBroken), all bids are automatically canceled and the item is terminated as an unsuccessful auction. If a listing has no qualifying bids when you call EndItems, the listing also ends as an unsuccessful auction.
There are two restrictions for ending items early in the last 12 hours of a listing. First, if there is a qualified bid in the last 12 hours of a listing, the seller cannot end the item early. Second, if the seller has canceled a bid during the last 12 hours of the listing, the seller cannot end the item early.
A successfully completed call returns EndTime for each ended listing, which is the official date and time (in GMT) that the listing was ended. Ending an item with EndItems triggers an ItemUnsold notification or Client Alert, if the seller is subscribed to that notification.
Testing EndItems
You can test this call in the Sandbox. You should test ending items using both items that have bids and items that do not have bids. This ensures your application is able to accommodate both use cases. Test EndItems as follows:
- In the Sandbox, use AddItem to list several items that can be ended early with EndItems.
- Call EndItems with the item IDs and review the results.
- Next, add several items to the Sandbox, and have a different users place bids on the items.
- Test setting EndingReason to
SellToHighBidderto successfully sell one item, and then test ending another listing with EndingReason set to another value to cancel bids and end the item as an unsuccessful auction.
Related Information
See End a listing early.
See also the reference documentation for these calls:
- EndItem - Ends the specified item listing before the date and time at which it would normally end per the listing duration.
- EndFixedPriceItem - Ends the specified fixed-price listing before the date and time at which it would normally end (per the listing duration).
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.
The XML prototype does not include requester credentials. This is a documentation limitation only (see Standard Requester Credentials for Making Calls).
<?xml version="1.0" encoding="utf-8"?> <EndItemsRequest xmlns="urn:ebay:apis:eBLBaseComponents"> <!-- Call-specific Input Fields --> <EndItemRequestContainer> EndItemRequestContainerType <EndingReason> EndReasonCodeType </EndingReason> <ItemID> ItemIDType (string) </ItemID> <MessageID> string </MessageID> </EndItemRequestContainer> <!-- ... more EndItemRequestContainer nodes allowed here ... --> <!-- Standard Input Fields --> <ErrorLanguage> string </ErrorLanguage> <MessageID> string </MessageID> <Version> string </Version> <WarningLevel> WarningLevelCodeType </WarningLevel> </EndItemsRequest>
| Argument | Type | Occurrence | Meaning |
|---|
repeatable: [1..10] An EndItemRequestContainer container is required for each eBay listing that the seller plans to end through the EndItems call. Up to 10 eBay listings can be ended with one EndItems call.
.EndingReason EndReasonCodeType Required The seller's reason for ending the listing early is input into this required field. The seller is not allowed to use the
ProductDeleted value, as this ending reason can only be used internally by eBay to administratively end a listing due to the associated Catalog product being removed from the eBay Catalog.
Applicable values: See EndingReason.
.MessageID string Optional Most Trading API calls support a MessageID element in the request and a CorrelationID element in the response. With EndItems, the seller can pass in a different MessageID value for each EndItemRequestContainer container that is used in the request. The CorrelationID value returned under each EndItemResponseContainer container is used to correlate each End Item request container with its corresponding End Item response container. The same MessageID value that you pass into a request will be returned in the CorrelationID field in the response.
If you do not pass in a MessageID value in the request, CorrelationID is not returned.
| ErrorLanguage | string | Optional |
Use ErrorLanguage to return error strings for the call in a different language from the language commonly associated with the site that the requesting user is registered with. Below are some examples from different countries.
|
||||||||||||||||||||||||||||||||||||||||
| MessageID | string | Optional |
Most Trading API calls support a MessageID element in the request and a CorrelationID element in the response. If you pass in a MessageID in a request, the same value will be returned in the CorrelationID field in the response. Pairing these values can help you track and confirm that a response is returned for every request and to match specific responses to specific requests. If you do not pass a MessageID value in the request, CorrelationID is not returned. Note: GetCategories is designed to retrieve very large sets of metadata that change once a day or less often. To improve performance, these calls return cached responses when you request all available data (with no filters). When this occurs, the MessageID and CorrelationID fields aren't applicable. However, if you specify an input filter to reduce the amount of data returned, the calls retrieve the latest data (not cached). When this occurs, MessageID and CorrelationID are applicable. |
||||||||||||||||||||||||||||||||||||||||
| Version | string | Conditional |
The version number of the API code that you are programming against (e.g., 1149). The version you specify for a call has these basic effects:
For the SOAP API: If you are using the SOAP API, this field is required. Specify the version of the WSDL your application is using. For the XML API: If you are using the XML API, this field has no effect. Instead, specify the version in the X-EBAY-API-COMPATIBILITY-LEVEL HTTP header. (If you specify Version in the body of an XML API request and it is different from the value in the HTTP header, eBay returns an informational warning that the value in the HTTP header was used instead.) See:
|
||||||||||||||||||||||||||||||||||||||||
| WarningLevel | WarningLevelCodeType | Optional |
Controls whether or not to return warnings when the application passes unrecognized or deprecated elements in a request. An unrecognized element is one that is not defined in any supported version of the schema. Schema element names are case-sensitive, so using WarningLevel can also help you remove any potential hidden bugs within your application due to incorrect case or spelling in field names before you put your application into the Production environment. WarningLevel only validates elements; it doesn't validate XML attributes. It also doesn't control warnings related to user-entered strings or numbers, or warnings for logical errors. We recommend that you only use this during development and debugging. Do not use this in requests performed in the Production environment. Applicable values: High if the user wishes to receive warnings when the application passes unrecognized or deprecated elements in an API call request. Setting the WarningLevel value to High is not recommended in a production environment. Instead, it should only be used during the development/debugging stage.Low if the user does not wish to receive warnings when the application passes unrecognized or deprecated elements in an API call request. This is the default value if WarningLevel is not specified in the call request.See Warning Level. |
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"?> <EndItemsResponse xmlns="urn:ebay:apis:eBLBaseComponents"> <!-- Call-specific Output Fields --> <EndItemResponseContainer> EndItemResponseContainerType <CorrelationID> string </CorrelationID> <EndTime> dateTime </EndTime> <Errors> ErrorType <ErrorClassification> ErrorClassificationCodeType </ErrorClassification> <ErrorCode> token </ErrorCode> <ErrorParameters ParamID="string"> ErrorParameterType <Value> string </Value> </ErrorParameters> <!-- ... more ErrorParameters nodes allowed here ... --> <LongMessage> string </LongMessage> <SeverityCode> SeverityCodeType </SeverityCode> <ShortMessage> string </ShortMessage> </Errors> <!-- ... more Errors nodes allowed here ... --> </EndItemResponseContainer> <!-- ... more EndItemResponseContainer nodes allowed here ... --> <!-- Standard Output Fields --> <Ack> AckCodeType </Ack> <Build> string </Build> <CorrelationID> string </CorrelationID> <Errors> ErrorType <ErrorClassification> ErrorClassificationCodeType </ErrorClassification> <ErrorCode> token </ErrorCode> <ErrorParameters ParamID="string"> ErrorParameterType <Value> string </Value> </ErrorParameters> <!-- ... more ErrorParameters nodes allowed here ... --> <LongMessage> string </LongMessage> <SeverityCode> SeverityCodeType </SeverityCode> <ShortMessage> string </ShortMessage> </Errors> <!-- ... more Errors nodes allowed here ... --> <HardExpirationWarning> string </HardExpirationWarning> <Timestamp> dateTime </Timestamp> <Version> string </Version> </EndItemsResponse>
| Return Value | Type | Occurrence | Meaning |
|---|
repeatable: [1..*] Returns a response for an individually ended item. Mutiple containers will be listed if multiple items are ended.
.CorrelationID string Conditionally Most Trading API calls support a MessageID element in the request and a CorrelationID element in the response. With EndItems, the seller can pass in a different MessageID value for each EndItemRequestContainer container that is used in the request. The CorrelationID value returned under each EndItemResponseContainer container is used to correlate each End Item request container with its corresponding End Item response container. The same MessageID value that you pass into a request will be returned in the CorrelationID field in the response.
If you do not pass in a MessageID value in the request, CorrelationID is not returned.
.EndTime dateTime Always This timestamp indicates the date and time (returned in GMT) when the specified eBay listing was ended.
.Errors ErrorType Conditionally,
repeatable: [0..*] A list of application-level errors or warnings (if any) that were raised when eBay processed the request.
Application-level errors occur due to problems with business-level data on the client side or on the eBay server side. For example, an error would occur if the request contains an invalid combination of fields, or it is missing a required field, or the value of the field is not recognized. An error could also occur if eBay encountered a problem in our internal business logic while processing the request.
Only returned if there were warnings or errors.
.Errors.ErrorClassification ErrorClassificationCodeType Conditionally API errors are divided between two classes: system errors and request errors.
Applicable values:
Code so that your app gracefully handles any future changes to this list.
.Errors.ErrorCode token 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.
See Errors By Number.
.Errors.ErrorParameters ErrorParameterType Conditionally,
repeatable: [0..*] This optional element carries a list of context-specific error variables that indicate details about the error condition. These are useful when multiple instances of ErrorType are returned.
.Errors.ErrorParameters
[ attribute ParamID ] string Conditionally This optional element carries a list of context-specific error variables that indicate details about the error condition. These are useful when multiple instances of ErrorType are returned.
.Errors.ErrorParameters.Value string Conditionally This is the value of the request parameter noted in the ParamID attribute. So, if the ParamID value was ItemID, the value in this field would be the actual value of that ItemID.
.Errors.LongMessage string Conditionally A more detailed description of the condition that raised the error.
.Errors.SeverityCode SeverityCodeType 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.
Applicable values:
If the source of the problem is within the application (such as a missing required element), 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, 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.
See the Error handling section of the Making a Trading API call guide for more information.
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.
Code so that your app gracefully handles any future changes to this list.
.Errors.ShortMessage string Conditionally A brief description of the condition that raised the error.
Applicable values:
(Not all values in AckCodeType apply to this field.)
Code so that your app gracefully handles any future changes to this list.
Note: GetCategories is designed to retrieve very large sets of metadata that change once a day or less often. To improve performance, these calls return cached responses when you request all available data (with no filters). When this occurs, the MessageID and CorrelationID fields aren't applicable. However, if you specify an input filter to reduce the amount of data returned, the calls retrieve the latest data (not cached). When this occurs, MessageID and CorrelationID are applicable.
repeatable: [0..*] A list of application-level errors (if any) that occurred when eBay processed the request.
Applicable values:
Code so that your app gracefully handles any future changes to this list.
See Errors By Number.
repeatable: [0..*] This optional element carries a list of context-specific error variables that indicate details about the error condition. These are useful when multiple instances of ErrorType are returned.
[ attribute ParamID ] string Conditionally This optional element carries a list of context-specific error variables that indicate details about the error condition. These are useful when multiple instances of ErrorType are returned.
Applicable values:
If the source of the problem is within the application (such as a missing required element), 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, 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.
See the Error handling section of the Making a Trading API call guide for more information.
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.
Code so that your app gracefully handles any future changes to this list.
Note: GetCategories and other Trading API calls are designed to retrieve very large sets of metadata that change once a day or less often. To improve performance, these calls return cached responses when you request all available data (with no filters). When this occurs, this time value reflects the time the cached response was created. Thus, this value is not necessarily when the request was processed. However, if you specify an input filter to reduce the amount of data returned, the calls retrieve the latest data (not cached). When this occurs, this time value does reflect when the request was processed.
Detail Controls
DetailLevel
This call does not support varying Detail Levels. You do not need to pass DetailLevel in the request.
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.
Defines and ends multiple items listed on the eBay site.
Description
User m***************r just spilled water all over her inventory of Harry Potter books. In a sincere effort to not mislead buyers she needs to end several listings. Using EndItems she is able to quickly end multiple listings, save time, and prevent a potential catastrophe with her buyers.
Input
All fields in the following EndItems request sample are the basic input to end a batch listing for m***************r's Harry Potter books.
XML format.
<?xml version="1.0" encoding="utf-8" ?>
<EndItemsRequest xmlns="urn:ebay:apis:eBLBaseComponents">
<RequesterCredentials>
<eBayAuthToken>A*******3</eBayAuthToken>
</RequesterCredentials>
<EndItemRequestContainer>
<MessageID>***1</MessageID>
<EndingReason>LostOrBroken</EndingReason>
<ItemID>1**********5</ItemID>
</EndItemRequestContainer>
<EndItemRequestContainer>
<MessageID>***2</MessageID>
<EndingReason>LostOrBroken</EndingReason>
<ItemID>1**********6</ItemID>
</EndItemRequestContainer>
</EndItemsRequest>
Output
The response includes the EndTime and the CorrelationID used in the end items request.
XML format.
<?xml version="1.0" encoding="utf-8"?>
<EndItemsResponse xmlns="urn:ebay:apis:eBLBaseComponents">
<Timestamp>2019年11月04日T17:33:35.145Z</Timestamp>
<Ack>Success</Ack>
<Version>1131</Version>
<Build>E1131_UNI_API5_19098188_R1</Build>
<EndItemResponseContainer>
<EndTime>2019年11月04日T17:33:35.145Z</EndTime>
<CorrelationID>*1</CorrelationID>
</EndItemResponseContainer>
<EndItemResponseContainer>
<EndTime>2019年11月04日T17:33:35.145Z</EndTime>
<CorrelationID>*2</CorrelationID>
</EndItemResponseContainer>
</EndItemsResponse>
Change History
| Change Date | Description |
|---|---|
| 1077 2018年08月31日 |
|
| 1027 2017年08月04日 |
|
| 0687 2010年09月10日 |
|
| 0595 2008年12月10日 |
|
| 0585 2008年10月01日 |
|