AddSecondChanceItem
Use this call to create a Second Chance Offer (that is, an offer for an unsold item) for one of that item's non-winning bidders.
AddSecondChanceItem creates a special type of listing in which only the specified Second Chance Offer recipient may purchase the item. The recipient who is chosen by the seller must be one of the non-winning bidders from the ended listing. The listing must have ended with a winning bidder, but the item did not sell for some reason. For example, the winning bidder, for whatever reason, did not purchase the item. Alternately, the seller may offer an item that is similar to the one previously listed as a Second Chance Offer item. In this case, the specified recipient may be either one of the non-winning bidders, or the winning bidder in the ended listing.
Use GetAllBidders to retrieve a list of bidders from the item that ended. The seller needs to select the recipient for the Second Chance Offer from this list.
For general information on Second Chance Offers and more detailed information on using AddSecondChanceItem, see Making Second Chance Offers for Items.
Usage Details
To call AddSecondChanceItem, the requestor must be the one who listed the original item and the item must meet the Second Chance Offer eligibility requirements (see Determining Item Eligibility for a Second Chance Offer).
AddSecondChanceItem takes as input the following values:
- ItemID - The original listing's item ID.
- RecipientBidderUserID - The eBay user ID for the recipient of the offer.
- Duration - The length of time the offer is valid.
- SellerMessage - Optionally, a message to the buyer.
If the call is successful, it returns the following information:
- ItemID - The new listing's item ID.
- StartTime - The start date and time for the listing.
- EndTime - The date and time the listing ends.
When you create a Second Chance Offer, eBay sends the recipient a message letting them know that the offer has been made. The price of the offer is normally set to the highest bid the recipient made on the original item.
Note that sending a Second Chance Offer, a new listing is not created on the eBay site. Instead, a special item is created for the targeted buyer. If you want to relist an item, use RelistItem, this can help to save on relisting fees.
Use VerifyAddSecondChanceItem to test an item's definition before calling AddSecondChanceItem. This can reduce the number of item listing errors the application needs to handle.
Testing AddSecondChanceItem
You can test AddSecondChanceItem in the Sandbox environment. To test the call, you need three or more test users. One test user is needed to act as the seller, the others act as bidders.
- List an auction item using a test user account.
- Have two or more other test users submit bids on the item. This can be done in the Sandbox UI (
http://sandbox.ebay.com). - Have the seller end the item early using EndItem with EndingReason set to
SellToHighBidder, which results in the listing ending as a successfully concluded auction with a winning bidder. - Call AddSecondChanceItem to extend a Second Chance Offer to one of the non-winning test users that bid on the item.
- Use an item data retrieval call (like GetSellerList or GetItem) to retrieve the data for the Second Chance Offer you just created. Verify that the listing has all of the desired values, including the value in the Item.ListingDetails.SecondChanceOriginalItemID property: it should contain the item ID for the original listing.
Optionally perform a search using findItemsAdvanced (Finding API). This search should use criteria that would definitely find the item.
Related Information
See Second chance offers.
See also the reference documentation for this call:
- VerifyAddSecondChanceItem - Simulates the creation of a new Second Chance Offer listing of an item without actually creating a listing.
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"?> <AddSecondChanceItemRequest xmlns="urn:ebay:apis:eBLBaseComponents"> <!-- Call-specific Input Fields --> <BuyItNowPrice> AmountType (double) </BuyItNowPrice> <Duration> SecondChanceOfferDurationCodeType </Duration> <ItemID> ItemIDType (string) </ItemID> <RecipientBidderUserID> UserIDType (string) </RecipientBidderUserID> <SellerMessage> string </SellerMessage> <!-- Standard Input Fields --> <ErrorLanguage> string </ErrorLanguage> <MessageID> string </MessageID> <Version> string </Version> <WarningLevel> WarningLevelCodeType </WarningLevel> </AddSecondChanceItemRequest>
| Argument | Type | Occurrence | Meaning |
|---|
Applicable values:
Note: Effective September 26, 2025, both usernames and public user IDs will be accepted in this field. For more information, please refer to Data Handling Compliance.
Max length: 1000.
| 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"?> <AddSecondChanceItemResponse xmlns="urn:ebay:apis:eBLBaseComponents"> <!-- Call-specific Output Fields --> <EndTime> dateTime </EndTime> <ItemID> ItemIDType (string) </ItemID> <StartTime> dateTime </StartTime> <!-- Standard Output Fields --> <Ack> AckCodeType </Ack> <Build> string </Build> <CorrelationID> string </CorrelationID> <DuplicateInvocationDetails> DuplicateInvocationDetailsType <DuplicateInvocationID> UUIDType (string) </DuplicateInvocationID> <InvocationTrackingID> string </InvocationTrackingID> <Status> InvocationStatusType </Status> </DuplicateInvocationDetails> <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> </AddSecondChanceItemResponse>
| Return Value | Type | Occurrence | Meaning |
|---|
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.
.DuplicateInvocationID UUIDType (string) Conditionally This value represents the duplicate InvocationID or InvocationTrackingID that was used in the call request.
.InvocationTrackingID string Conditionally This unique identifier identifies the business item the previous API invocation created. For example, the Item ID of the item created by an AddItem call.
.Status InvocationStatusType Conditionally This enumeration value indicates the status of the previous call that used the InvocationID or InvocationTrackingID specified in the DuplicateInvocationID.
Applicable values:
Code so that your app gracefully handles any future changes to this list.
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.
Extends a Second Chance Offer to a bidder that did not win the auction.
Description
The prospective buyer (b************r) bid on a book, but did not win the auction. The seller (M*****l B********r) came across another copy of the book in the same condition and decided to offer the second copy to the second-highest bidder, b************r.
When a Second Chance Offer is created, the recipient is given a chance to purchase the item at the highest price that they bid on the original item. eBay sends the buyer a message stating that the Second Chance Offer has been made, along with any message the seller included in the offer.
Input
XML format.
<?xml version="1.0" encoding="utf-8"?>
<AddSecondChanceItemRequest xmlns="urn:ebay:apis:eBLBaseComponents">
<RequesterCredentials>
<eBayAuthToken>A*******3</eBayAuthToken>
</RequesterCredentials>
<!-- The user ID of an user who made a bid on the auction item. The GetAllBidders call can be used to get bidders on a listing -->
<RecipientBidderUserID>b************r</RecipientBidderUserID>
<!-- The offer duration must be one of the values defined in SecondChanceOfferDurationCodeType -->
<Duration>Days_3</Duration>
<ItemID>1**********1</ItemID>
<SellerMessage>
I just got another copy of the book in stock, would
you be interested in purchasing the copy?
</SellerMessage>
</AddSecondChanceItemRequest>
Output
XML format.
<AddSecondChanceItemResponse xmlns="urn:ebay:apis:eBLBaseComponents">
<Timestamp>2015年12月22日T17:45:31.032Z</Timestamp>
<Ack>Success</Ack>
<Version>967</Version>
<Build>E967_CORE_BUNDLED_10284414_R1</Build>
<ItemID>1**********4</ItemID>
<StartTime>2015年12月22日T17:45:30.000Z</StartTime>
<EndTime>2015年12月25日T17:45:30.000Z</EndTime>
</AddSecondChanceItemResponse>
Change History
| Change Date | Description |
|---|---|
| 529 2007年09月05日 |
|
| 499 2007年02月07日 |
|
| 479 2006年09月20日 |
|
| 457 2006年04月19日 |
|
| 449 2006年02月22日 |
|
| 409 2005年5月18日 |
|