eBay Trading API Release Notes Support     Knowledge Base     Forums     All Tutorials     All Code Samples Trading API Guide Call Reference Making an API Call Tutorials Release Notes

The latest version of the Trading API has rolled out to all the API machines and is now available! Be sure to check out all the new features and known issues.

If you are getting started with the API, the following locations have information about joining the eBay Developers Program, creating test users, and other steps to getting your application certified to go live against the eBay production servers:

• eBay Developer Documentation Center
• eBay Web Services - Quick Start

These release notes go back four quarters. For older release notes, see the Release Notes archive.

The lowest supported version is 681.
To learn how versioning works in the Trading API, see eBay's Schema Versioning Strategy.

Back to top

Version 773

Index of Changed Calls - 773

Schema Changes - 773

Announcements - 773

New Features - 773

Changed Functionality - 773

Documentation Changes and Errata - 773

For a current list of known issues, see Site Status and the Knowledge Base.

Index of Changed Calls - 773

These calls were added, modified, deprecated, or affected by documentation changes in this release. The changes are described below as well as in each call's Change History.

New Calls

No new calls in this release.

Changed Calls

• ReviseFixedPriceItem
• ReviseItem

Schema Changes - 773

Announcements - 773

Business Policies Go Live to Production in Version 775

The Business Policies API and related Trading API fields become available in production for a limited number of sellers with Version 775. 100 percent of sellers will be ramped up to use Business Polcies in July 2012.

Business Policies are currently available for testing in the Sandbox environment.

Change Requests

See the Site Status for bug fixes related to this release. For documentation-related issues, see the Documentation System Announcements.

New Features - 773

This section describes new features that have been added as of this release. New features can involve new calls, new capabilities, and/or new fields added to existing calls.

For logical or functional changes to existing features and calls, including code list changes, see Changed Functionality - 773.

None for this release.

Changed Functionality - 773

This section describes logical or functional changes that have been made to existing functionality, including new code list values and/or changes in validation rules.

Some Return Policy Values Deprecated

For sellers that accept returns, the following values will no longer be allowed:

• 3-day and 7-day returns: the three available options are 14, 30, or 60 days (in the API, the seller will set the Item.ReturnPolicy.ReturnsWithin field to Days_14, Days_30, or Days_60)
• "Merchandise credit" and "Exchange" refund options: the two available options are "Money Back" or "Money Back or Exchange" (in the API, the seller will set the Item.ReturnPolicy.RefundOption field to MoneyBack or MoneyBackOrExchange)

Documentation Changes and Errata - 773

This section lists additional documentation changes and corrections that were made with this release and that are not already mentioned in New Features - 773 and Changed Functionality - 773.

None for this release.

Back to top

Version 771

Index of Changed Calls - 771

Schema Changes - 771

Announcements - 771

New Features - 771

Changed Functionality - 771

Documentation Changes and Errata - 771

For a current list of known issues, see Site Status and the Knowledge Base.

Index of Changed Calls - 771

These calls were added, modified, deprecated, or affected by documentation changes in this release. The changes are described below as well as in each call's Change History.

New Calls

No new calls in this release.

Changed Calls

• GetAccount
• GetItemTransactions
• GetMyeBaySelling
• GetItemTransactions
• GetNotificationPreferences
• GetNotificationUsage
• GetOrders
• GetOrderTransactions
• GetSellerTransactions
• GetSellingManagerSaleRecord
• GetSellingManagerSoldListings
• SetNotificationPreferences

Schema Changes - 771

Announcements - 771

Business Policies Go Live to Production in Version 775

The Business Policies API and related Trading API fields become available in production for a limited number of sellers with Version 775. 100 percent of sellers will be ramped up to use Business Polcies in July 2012.

Business Policies allow sellers to create and manage multiple shipping, return, and payment policies and apply these policies to listings just by referencing the policy ID at listing time. By enabling sellers to manage/update shipping, return, and payment policies in one central location, Business Policies will help sellers save time and reduce errors in listings.

Business Policies are currently available for testing in the Sandbox environment.

New Requirements for Top-Rated Sellers

Starting in June, Top-rated Sellers must upload shipment tracking information for at least 90% of their order line items (purchased by U.S. buyers) to keep their status as Top-Rated Sellers. The annual sales requirement for a Top-rated seller is now $1,000.

To earn the 20% final value fee discount on a listing, and to get the highest average boost in Best Match, sellers must:

• Offer a 1-day handling time (Item.DispatchTimeMax=1 in the APIs)
• Offer a return policy that accepts returns from the buyer at least 14 days after purchase (In the APIs, Item.ReturnPolicy.ReturnsAcceptedOption=ReturnsAccepted and Item.ReturnPolicy.ReturnsWithinOption=Days_14|Days_30|Days_60)
• Offer Money Back or Exchange options (Item.ReturnPolicy.RefundOption=MoneyBack|MoneyBackOrExchange in the APIs)

See the Top-rated seller program Spring 2012 update for more information.

Bonus 5% Discount Program for Top-Rated Sellers

From March 1 through May 31, Top-rated sellers can receive an additional 5% discount (on top of 20% discount) for all listings that meet the new Top-rated Seller requirements of 1-day handling time, 14-day (or greater) return window, and money-back option.

USPS First-Class Service No Longer an Expedited Shipping Service

Starting the first week of May, USPS First-Class will be reclassified on eBay from an Expedited to a Standard shipping service. Expedited shipping services have an estimated delivery time of 2-3 business days and Standard shipping services have an estimated delivery time of 2-5 business days, and since USPS First-Class did not always meet the Expedited delivery time requirement, it is being reclassified. The shipping service name changes from First-Class Mail to First-Class Package.

See the Shipping Spring 2012 update for more information.

Some Return Policy Values Deprecated

For sellers that accept returns, the following values will no longer be allowed starting the first week of May:

• 3-day and 7-day returns: the three available options are 14, 30, or 60 days (in the API, the seller will set the Item.ReturnPolicy.ReturnsWithin field to Days_14, Days_30, or Days_60)
• "Merchandise credit" and "Exchange" refund options: the two available options are "Money Back" or "Money Back or Exchange" (in the API, the seller will set the Item.ReturnPolicy.RefundOption field to MoneyBack or MoneyBackOrExchange)

Change Requests

See the Site Status for bug fixes related to this release. For documentation-related issues, see the Documentation System Announcements.

New Features - 771

This section describes new features that have been added as of this release. New features can involve new calls, new capabilities, and/or new fields added to existing calls.

For logical or functional changes to existing features and calls, including code list changes, see Changed Functionality - 771.

DE/AT Order Refund Fields Returned in More Trading Calls

The refund amount and refund status of DE/AT orders going through the new eBay payment process are now returned in GetMyeBaySelling, GetSellingManagerSaleRecord, and GetSellingManagerSoldListings. The RefundAmount and RefundStatus fields are only returned if a refund has been issued to the buyer.

New Platform Notifications For DE/AT Orders

There are three new platform notifications applicable for DE/AT sellers for orders going through the new eBay payment process. RefundSuccess and RefundFailure indicate the result of an attempted refund to the buyer, and UnmatchedPaymentReceived is sent to the seller when a buyer's EFT payment does not match the total amount of the order. For unmatched EFT payments, the seller has to decide whether to accept or reject the over- or under-payment.

New Platform Notifications For Returns

There are eight new platform notifications applicable for eBay returns. These notifications alert the subscribed seller and buyer about status changes in an eBay return flow. Note: These notifications will not be applicable until eBay returns go live.

Changed Functionality - 771

This section describes logical or functional changes that have been made to existing functionality, including new code list values and/or changes in validation rules.

None for this release.

Documentation Changes and Errata - 771

This section lists additional documentation changes and corrections that were made with this release and that are not already mentioned in New Features - 771 and Changed Functionality - 771.

None for this release.

Back to top

Version 767

Index of Changed Calls - 767

Schema Changes - 767

Announcements - 767

New Features - 767

Changed Functionality - 767

Documentation Changes and Errata - 767

For a current list of known issues, see Site Status and the Knowledge Base.

Index of Changed Calls - 767

These calls were added, modified, deprecated, or affected by documentation changes in this release. The changes are described below as well as in each call's Change History.

New Calls

No new calls in this release.

Changed Calls

No changed calls in this release.

Schema Changes - 767

None for this release.

Announcements - 767

Change Requests

See the Site Status for bug fixes related to this release. For documentation-related issues, see the Documentation System Announcements.

New Features - 767

This section describes new features that have been added as of this release. New features can involve new calls, new capabilities, and/or new fields added to existing calls.

For logical or functional changes to existing features and calls, including code list changes, see Changed Functionality - 767.

None for this release.

Changed Functionality - 767

This section describes logical or functional changes that have been made to existing functionality, including new code list values and/or changes in validation rules.

None for this release.

Documentation Changes and Errata - 767

This section lists additional documentation changes and corrections that were made with this release and that are not already mentioned in New Features - 767 and Changed Functionality - 767.

None for this release.

Back to top

Version 765

Index of Changed Calls - 765

Schema Changes - 765

Announcements - 765

New Features - 765

Changed Functionality - 765

Documentation Changes and Errata - 765

For a current list of known issues, see System Announcements and the Knowledge Base.

Index of Changed Calls - 765

These calls were added, modified, deprecated, or affected by documentation changes in this release. The changes are described below as well as in each call's Change History.

New Calls

No new calls in this release.

Changed Calls

• GetBidderList
• GetCategoryFeatures
• GetItem
• GetItemTransactions
• GetOrders
• GetOrderTransactions
• GetSellerList
• GetSellerTransactions
• GetSellingManagerTemplates
• GetUser

Schema Changes - 765

Announcements - 765

New Refund Functionality in eBay's New Payment Process for DE/AT Sellers

When German and Austrian sellers issue a refund through eBay's new payment process, a RefundArray container consisting of details about the refund will be returned by GetItemTransactions, GetOrders, GetOrderTransactions and GetSellerTransactions.

The information returned in the RefundArray.Refund container includes:

• The refund amount.
• The refund request time and completion or estimated completion time.
• Details about the order line item against which the refund was issued.
• Details about the funding source of the refund.
• The status of the refund operation.
• Details about any failure of the refund operation.

Over/Under Buyer Payments Reported to DE/AT Sellers

If the buyer's payment does not match the total cost of the DE or AT order, a flag to indicate the over or under payment value and an action date is returned by GetItemTransactions, GetOrders, GetOrderTransactions and GetSellerTransactions.

The eBayPaymentMismatchDetails container will only be returned if the following conditions are satisfied:

• The item was listed on the DE or AT sites.
• The item's category is not exempt from the new eBay payment process.
• The seller's account is fully ramped up in the new eBay payment process.
• The buyer's payment did not match (over or under payment) the total cost of the order.

The ActionRequiredBy date in the eBayPaymentMismatchDetails container is the date by which the seller needs to accept or reject the overpayment/underpayment. If the seller doesn't take action by this date, eBay returns the payment to the buyer and essentially voids the sale. The seller can accept or reject the buyer's payment through the site or by using the Order Adjustment API (see below).

New eBay Payment Process User Agreement Information and Payout Preferences Returned for DE/AT Sellers

All DE and AT sellers are required to sign a supplemental user agreement for the new eBay payment process, as well as set their payout preferences. The SellereBayPaymentProcessConsent container and SellereBayPaymentProcessStatus field will contain this information and will be returned in the following Trading API calls:

• GetItem
• GetUser
• GetSellerList
• GetBidderList
• GetItemTransactions
• GetSellerTransactions
• GetSellingManagerTemplates

For sellers that list on both the DE and AT sites, a UserAgreementInfo container will be returned for both sites. The supplemental user agreement URL will be returned for all sellers who have not opted into the new eBay payment process.

Reminder: Global Deprecation of ID-Based Attributes

As previously announced, eBay will complete the deprecation of ID-based attributes worldwide in 2012. All categories that previously supported ID-based attributes have now been migrated to support custom item specifics in the sandbox and production. (eBay Motors will support custom item specifics in production by the end of March.) The new VIN, VINLink, VRM, VRMLink, SellerProvidedTitle, DepositType, and DepositAmount fields are now available in production, and replace the corresponding ID-based attributes for motors vehicles on the US eBay Motors, CA, CAFR, UK, and AU sites.

Also see this KB article: Listing items with product information using eBay catalog for tips on listing with product details.

Reminder: Lowest Supported Trading API Version is 681

As of February 2012, the lowest supported version is now 681. To learn how versioning works in the Trading API, see eBay's Schema Versioning Strategy.

Change Requests

See the Site Status for bug fixes related to this release. For documentation-related issues, see the Documentation System Announcements.

New Features - 765

This section describes new features that have been added as of this release. New features can involve new calls, new capabilities, and/or new fields added to existing calls.

For logical or functional changes to existing features and calls, including code list changes, see Changed Functionality - 765.

Parts Compatiblity Updates

Changes have been made to improve the support for specifying parts compatibility by application. Previously, sellers have typically been allowed to provide a maximum of 300 parts compatibilities parts compatiblities at any level of granularity, as indicated by Category.MaxItemCompatibility in the GetCategoryFeatures resonse. Now, depending on the level of granularity, sellers can specify a maximum of either:

• 300 (or whatever value is returned by Category.MaxItemCompatibility) parts compatibilities at the coarsest granularity (e.g., specifying only Year, Make, and Model)
• 1000 (or whatever value is returned by Category.MaxGranularFitmentCount) parts compatibilities at the lowest level of granularity (i.e., by specifying a value for all supported compatiblity search names, such as Year, Make, Model, Trim, and Engine)

In addition to the fitment count change, parts compatibility has been expanded to support more vehicle types. Previously, parts compatibility was limited to Cars and Trucks only. Now, as indicated by Category.CompatibleVehicleType in the GetCategoryFeatures resonse, some categories support fitment for motorcycles, as well.

Changed Functionality - 765

This section describes logical or functional changes that have been made to existing functionality, including new code list values and/or changes in validation rules.

None for this release.

Documentation Changes and Errata - 765

This section lists additional documentation changes and corrections that were made with this release and that are not already mentioned in New Features - 765 and Changed Functionality - 765.

None for this release.

Back to top

Version 763

Index of Changed Calls - 763

Schema Changes - 763

Announcements - 763

New Features - 763

Changed Functionality - 763

Documentation Changes and Errata - 763

For a current list of known issues, see System Announcements and the Knowledge Base.

Index of Changed Calls - 763

These calls were added, modified, deprecated, or affected by documentation changes in this release. The changes are described below as well as in each call's Change History.

New Calls

No new calls in this release.

Changed Calls

• AddFixedPriceItem
• AddItem
• AddItems
• GetItem
• GetMyeBayBuying
• GetMyeBaySelling
• GetSellerEvents
• GetSellerList
• GetSellingManagerTemplates
• GetUserPreferences
• RelistFixedPriceItem
• RelistItem
• ReviseFixedPriceItem
• ReviseItem
• VerifyAddFixedPriceItem
• VerifyAddItem
• VerifyRelistItem

Schema Changes - 763

Announcements - 763

Change Requests

See the Site Status for bug fixes related to this release. For documentation-related issues, see the Documentation System Announcements.

New Features - 763

This section describes new features that have been added as of this release. New features can involve new calls, new capabilities, and/or new fields added to existing calls.

For logical or functional changes to existing features and calls, including code list changes, see Changed Functionality - 763.

Using Pictures in Multi-Variation Listings

For sites that support a free gallery picture: When you use VariationSpecificPictureSet.PictureURL, if you specify a picture that is hosted outside of eBay Picture Services (EPS), eBay copies the picture to EPS.

GetItem returns the EPS-hosted picture in VariationSpecificPictureSet.PictureURL, and returns the original (self-hosted) picture in VariationSpecificPictureSet.ExternalPictureURL.

Regardless of whether you are using an EPS-hosted picture or a self-hosted picture in variations, continue to use VariationSpecificPictureSet.PictureURL in AddFixedPriceItem and related calls.

Business Policies Available for Testing in Sandbox

The new Business Policies Management API and related Trading API containers/fields are now available for testing in the Sandbox environment. The Business Policies Management API will allow sellers to create (and manage) multiple payment, shipping, and return policy profiles. Once these policy profiles are created, then sellers can just reference these profiles (using unique IDs and/or names for the profile) in the Trading API's Add/Revise/Relist family of calls, instead of passing this policy information each time they create, revise, or relist an item. By adopting and using the new Business Policy API, sellers can reduce the time they spend managing listings and can react quickly to eBay policy changes.

For more information on Business Policies, see the 761 Announcements.

GetMyeBayBuying Updates

When products have been added to a buyer's Wish List, the product information is now returned in ItemArray.Item.ProductListingDetails within the UserDefinedList node. Products can be added to a buyer's Wish List only. This change does not apply to any other user-defined list.

New fields have been added to display favorite seller and item counts for user-defined lists. The IncludeFavoriteSellerCount and IncludeItemCount input fields control the display of the FavoriteSellerCount and ItemCount fields in the UserDefinedList node in the GetMyeBayBuying response.

Changed Functionality - 763

This section describes logical or functional changes that have been made to existing functionality, including new code list values and/or changes in validation rules.

None for this release.

Documentation Changes and Errata - 763

This section lists additional documentation changes and corrections that were made with this release and that are not already mentioned in New Features - 763 and Changed Functionality - 763.

None for this release.

Back to top

Version 761

Index of Changed Calls - 761

Schema Changes - 761

Announcements - 761

New Features - 761

Changed Functionality - 761

Documentation Changes and Errata - 761

For a current list of known issues, see System Announcements and the Knowledge Base.

Index of Changed Calls - 761

These calls were added, modified, deprecated, or affected by documentation changes in this release. The changes are described below as well as in each call's Change History.

New Calls

No new calls in this release.

Changed Calls

No changed calls in this release.

Schema Changes - 761

None for this release.

Announcements - 761

Coming Soon: New Business Policies Management API and a New Way To Specify Payment, Shipping, and Return Policy Values

Beginning with Version 763, the new Business Policies Management API and related Trading API containers/fields become available for testing in the Sandbox environment. The Business Policies Management API will allow sellers to create (and manage) multiple payment, shipping, and return policy profiles. Once these policy profiles are created, then sellers can just reference these profiles (using unique IDs and/or names for the profile) in the Trading API's Add/Revise/Relist family of calls, instead of passing this policy information each time they create, revise, or relist an item. By adopting and using the new Business Policy API, sellers can reduce the time they spend managing listings and can react quickly to eBay policy changes.

To opt in and begin using Business Policies in the Sandbox environment, go to the following link: https://ebay.custhelp.com/app/answers/detail/a_id/2021.

Overview of Business Policies Management API

There are four operations available to sellers in the Business Policies Management API: one operation to create one or more business policy profiles (addSellerProfile); one operation to modify one or more business policy profiles (setSellerProfile); one operation to retrieve one or more business policy profiles (getSellerProfiles); and one operation to delete one business policy profile (removeProfile).

For more information on the Business Policies API, see Business Policies API Users Guide

Changes to Trading API Listing Calls

In the Add/Revise/Relist family of Trading API calls, the following containers can now be used in call requests to reference and use the values of existing business policy profiles:

• SellerProfiles.SellerPaymentProfile: in this container, the seller supplies the unique identifier and/or name of a payment policies profile. If the seller uses this container to reference a payment policies profile, the following Trading API fields will be overwritten by their Business Policies API equivalents, as shown below:
  • PaymentMethods (Trading) will be replaced by paymentInfo.acceptedPaymentMethod (Business Policies)
  • AutoPay (Trading) will be replaced by paymentInfo.immediatePay (Business Policies)
  • ShippingDetails.PaymentInstructions (Trading) will be replaced by paymentInfo.paymentInstructions (Business Policies)
  • PayPalEmailAddress (Trading) will be replaced by paymentInfo.paypalEmailAddress (Business Policies)
  • PaymentDetails container values (Trading) will be replaced by DepositDetails container values (Business Policies)
• SellerProfiles.SellerReturnProfile: in this container, the seller supplies the unique identifier and/or name of a return policies profile. If the seller uses this container to reference a return policies profile, the following Trading API fields will be replaced by their Business Policies API equivalents, as shown below:
  • ReturnPolicy.ReturnsAcceptedOption (Trading) will be replaced by returnPolicyInfo.returnsAcceptedOption (Business Policies)
  • ReturnPolicy.Description (Trading) will be replaced by returnPolicyInfo.description (Business Policies)
  • ReturnPolicy.ReturnsWithinOption (Trading) will be replaced by returnPolicyInfo.returnsWithinOption (Business Policies)
  • ReturnPolicy.RefundOption (Trading) will be replaced by returnPolicyInfo.refundOption (Business Policies)
  • ReturnPolicy.ShippingCostPaidByOption (Trading) will be replaced by returnPolicyInfo.shippingCostPaidByOption container values (Business Policies)
  • ReturnPolicy.WarrantyDurationOption (Trading) will be replaced by returnPolicyInfo.warrantyDurationOption container values (Business Policies)
  • ReturnPolicy.WarrantyOfferedOption (Trading) will be replaced by returnPolicyInfo.warrantyOfferedOption container values (Business Policies)
  • ReturnPolicy.WarrantyTypeOption (Trading) will be replaced by returnPolicyInfo.warrantyTypeOption container values (Business Policies)
• SellerProfiles.SellerShippingProfile: in this container, the seller supplies the unique identifier and/or name of a shipping policies profile. If the seller uses this container to reference a shipping policies profile, the following Trading API fields will be replaced by their Business Policies API equivalents, as shown below:
  • DispatchTimeMax (Trading) will be replaced by shippingPolicyInfo.dispatchTimeMax (Business Policies)
  • ShippingDetails.ExcludeShipToLocation (Trading) will be replaced by shippingPolicyInfo.excludeShipToLocation (Business Policies)
  • ShipToLocations (Trading) will be replaced by shippingPolicyInfo.shipToLocations (Business Policies)
  • ShippingDetails.RateTableDetails.DomesticRateTable (Trading) will be replaced by shippingPolicyInfo.domesticRateTable (Business Policies)
  • ShippingDetails.RateTableDetails.InternationalRateTable (Trading) will be replaced by shippingPolicyInfo.intlRateTable (Business Policies)
  • ShippingDetails.CalculatedShippingRate.PackagingHandlingCosts (Trading) will be replaced by shippingPolicyInfo.packagingHandlingCosts (Business Policies)
  • ShippingDetails.CalculatedShippingRate.InternationalPackagingHandlingCosts (Trading) will be replaced by shippingPolicyInfo.internationalPackagingHandlingCosts (Business Policies)
  • ShippingDetails.CODCost (Trading) will be replaced by codFee (Business Policies)
  • ShippingDetails.ShippingDiscountProfileID (Trading) will be replaced by shippingPolicyInfo.shippingProfileDiscountInfo.domesticFlatCalcDiscountProfileId (Business Policies)
  • ShippingDetails.PromotionalShippingDiscount (Trading) will be replaced by shippingPolicyInfo.shippingProfileDiscountInfo.domesticPromoShippingProfileId (Business Policies)
  • ShippingDetails.InternationalPromotionalShippingDiscount (Trading) will be replaced by shippingPolicyInfo.shippingProfileDiscountInfo.intlFlatCalcDiscountProfileId (Business Policies)
  • ShippingDetails.PaymentInstructions (Trading) will be replaced by shippingPolicyInfo.shippingProfileDiscountInfo.intlPromoShippingProfileId (Business Policies)
  • GetItFast (Trading) will be replaced by FastShipping (Business Policies)
  • BuyerResponsibleForShipping (Trading) will be replaced by buyerResponsibleForShipping (Business Policies)
  • ShippingServiceOptions container values (Trading) will be replaced by domesticShippingPolicyInfoService container values (Business Policies)
  • InternationalShippingServiceOption container values (Trading) will be replaced by intlShippingPolicyInfoService container values (Business Policies)

As part of Business Policies project, the ShippingPackageDetails container is also being introduced with Version 763. The ShippingPackageDetails container is only applicable if calculated shipping is used by the seller, however, field values are saved if this container (and its child fields) are included in a call request.

The Business Policies Management API and related Trading API containers/fields will go live to production in May 2012. At that time, the 18-month process of deprecating existing legacy Trading API containers/fields will begin. The containers/fields of the Trading API listing calls scheduled to begin this deprecation are shown below:

• Item.PaymentDetails (container)
• Item.ReturnPolicy (container)
• Item.ShippingDetails (container)
• Item.PaymentMethods (repeatable field)
• Item.PayPalEmailAddress (field)
• Item.AutoPay (field)
• Item.DispatchTimeMax (field)
• Item.ShipToLocations (repeatable field)
• Item.GetItFast (field)
• Item.BuyerResponsibleForShipping (field)

As of Version 763, Item.ShippingDetails.CalculatedShippingRate.OriginatingPostalCode is being hard deprecated. Sellers should use Item.PostalCode instead.

See the AddItem Call Reference (and other Add/Revise/Relist calls) for documentation on the new containers related to business policy profiles.

Retrieving Business Policy Profile Information

The business policy profiles set up for a seller's account can be retrieved by calling GetUserPreferences. In the call request, the seller includes and sets the ShowSellerProfilePreferences flag to 'true'. The SellerProfilePreferences container returned in the response will contain a SellerProfileOptedIn flag that indicates whether or not the seller has opted into Business Policies, as well as a separate SupportedSellerProfile node (containing profile ID, profile name, profile type, etc.) for each business policy profile set up for the seller's account. This call is done at the eBay site level, so if a user sells on multiple eBay sites, that seller would have to make a separate call to return business policy profiles for each site (specified in the SITEID header).

The folowing Trading "Get" calls will return any payment, shipping, or return policy profiles set for the item listing:

• GetItem
• GetItems
• GetMyeBaySelling
• GetSellerEvents
• GetSellerList
• GetSellingManagerTemplates

Future Business Profiles Enhancements

The following two enhancements are scheduled for a future release of Business Policies:

• The ability to override shipping service costs (associated with a shipping policy profile) when creating or revising a listing
• GetCategoryFeatures enhanced to return the Business Profile category groups that can be used with the specified eBay categories.

New Payment Process Warning Messages for DE/AT Sellers

All German and Austrian sellers will receive a warning message (ID: 21919038) when creating, revising, or relisting items if they have not accepted the new payment process user agreement. The warning message will contain a link to the new user agreement. As soon as the seller accepts the user agreement, he/she will be directed to set up eBay Payout preferences. In these preferences, the seller decides if he/she wants eBay to distribute funds to a PayPal or bank account.

Beginning in June 2012, all German and Austrian sellers will receive an error message (ID: 21919039) and be blocked from creating, revising, or relisting items if they have not accepted the new payment process user agreement. Similarly, scheduled listings will not become active when the scheduled date is reached, nor will GTC (Good 'Til Cancelled) fixed-price listings be relisted if this user agreement has not been accepted by the seller.

Change Requests

See the Site Status for bug fixes related to this release. For documentation-related issues, see the Documentation System Announcements.

New Features - 761

For logical or functional changes to existing features and calls, including code list changes, see Changed Functionality - 761.

Changed Functionality - 761

This section describes logical or functional changes that have been made to existing functionality, including new code list values and/or changes in validation rules.

None for this release.

Documentation Changes and Errata - 761

This section lists additional documentation changes and corrections that were made with this release and that are not already mentioned in New Features - 761 and Changed Functionality - 761.

None for this release.

Back to top

Version 759

Index of Changed Calls - 759

Schema Changes - 759

Announcements - 759

New Features - 759

Changed Functionality - 759

Documentation Changes and Errata - 759

For a current list of known issues, see System Announcements and the Knowledge Base.

Index of Changed Calls - 759

These calls were added, modified, deprecated, or affected by documentation changes in this release. The changes are described below as well as in each call's Change History.

New Calls

No new calls in this release.

Changed Calls

• GetCharities

Schema Changes - 759

Announcements - 759

Change Requests

See the Site Status for bug fixes related to this release. For documentation-related issues, see the Documentation System Announcements.

New Features - 759

This section describes new features that have been added as of this release. New features can involve new calls, new capabilities, and/or new fields added to existing calls.

For logical or functional changes to existing features and calls, including code list changes, see Changed Functionality - 759.

New Fields Returned in GetCharities

New fields are returned in the GetCharities response, including the address of the charity organization, any social networking sites associated with the organization, the Popularity Index rating of the charity, and the EIN (Employment Identification Number).

Changed Functionality - 759

This section describes logical or functional changes that have been made to existing functionality, including new code list values and/or changes in validation rules.

Global Deprecation of ID-Based Attributes

As previously announced, eBay will complete the deprecation of ID-based attributes worldwide in 2012. Last October, we stopped supporting ID-based attributes in a number of categories that already supported custom item specifics.

We will deprecate the remaining ID-based attributes in the API according to the following schedule. (Use the newer custom item specifics format instead.)

Warnings to be Returned for Return Policy Values Set to be Deprecated

Beginning with Version 759, a warning message will be returned if a listing is created or revised in Sandbox (using Add/Revise/Relist family of API calls) with RefundOption and/or ReturnsWithinOption values that are being deprecated in 2012. And starting with the Spring Seller Release in early May 2012, listings created with these same values will be blocked.

For RefundOption, the values being deprecated are MerchandiseCredit and Exchange. GeteBayDetails already stopped returning these options in Sandbox, and these values will stop being returned in Production in May 2012. Instead of these deprecated values, the seller must offer a MoneyBack or a MoneyBackOrExchange refund option. Consider using the MoneyBackOrExchange option when you have the depth of inventory to support an exchange for a different size, color, or undamaged unit. Otherwise, use the MoneyBack option if you have limited inventory.

For ReturnsWithinOption, the values being deprecated are Days_3 and Days_7. GeteBayDetails already stopped returning these options in Sandbox, and these values will stop being returned in Production in May 2012. Instead of these deprecated values, the seller must offer a 10-day, 14-day, 30-day, or 60-day return window.

We'll continue to support ReturnsNotAccepted as a policy. However, even if you specify ReturnsNotAccepted, buyers may still return an item if the item is significantly not as described (SNAD) in the listing. Buyers in the US, UK, and Germany can open an eBay Buyer Protection case for SNAD items.

Here is the current timeline for warning messages and blocked listings:

Documentation Changes and Errata - 759

This section lists additional documentation changes and corrections that were made with this release and that are not already mentioned in New Features - 759 and Changed Functionality - 759.

Updated ReviseCheckoutStatus Documentation with DE New Sellers Limitations

Added a note about new DE and AT sellers not being able to use ReviseCheckoutStatus to change the status of orders subject to the new payment process.

GetBestOffers Correction

Previously, the GetBestOffers documentation stated that you only needed the BestOfferID to retrieve details about a Best Offer, but you actually need the BestOfferID and the ItemID.

Back to top

Version 757

Index of Changed Calls - 757

Schema Changes - 757

Announcements - 757

New Features - 757

Changed Functionality - 757

Documentation Changes and Errata - 757

For a current list of known issues, see System Announcements and the Knowledge Base.

Index of Changed Calls - 757

These calls were added, modified, deprecated, or affected by documentation changes in this release. The changes are described below as well as in each call's Change History.

New Calls

No new calls in this release.

Changed Calls

• AddFixedPriceItem
• AddItem
• AddItems
• AddSellingManagerTemplate
• GetItem
• GetItemRecommendations
• RelistFixedPriceItem
• RelistItem
• ReviseFixedPriceItem
• ReviseItem
• ReviseSellingManagerTemplate
• VerifyAddFixedPriceItem
• VerifyAddItem
• VerifyRelistItem

Schema Changes - 757

Announcements - 757

Coming Soon: Warning Returned for Return Policy Values Set to be Deprecated

Beginning with version 759, a warning message will be returned if a listing is created or revised (using Add/Revise/Relist family of API calls) with RefundOption and/or ReturnsWithinOption values that are being deprecated in 2012. And starting with the Spring Seller Release in early May 2012, listings created or revised with these same values will be blocked. Later in 2012, if any GTC listings still have non-compliant options, eBay will convert them during auto-renewal to use the default options (e.g., 14 days).

For RefundOption, the values being deprecated are MerchandiseCredit and Exchange. GeteBayDetails already stopped returning these options in Sandbox, and these values will stop being returned in Production in February. Instead of these deprecated values, the seller must offer a MoneyBack or a MoneyBackOrExchange refund option. Consider using the MoneyBackOrExchange option when you have the depth of inventory to support an exchange for a different size, color, or undamaged unit. Otherwise, use the MoneyBack option if you have limited inventory.

For ReturnsWithinOption, the values being deprecated are Days_3 and Days_7. GeteBayDetails already stopped returning these options in Sandbox, and these values will stop being returned in Production in February. Instead of these deprecated values, the seller must offer a 10-day, 14-day, 30-day, or 60-day return window.

We'll continue to support ReturnsNotAccepted as a policy. However, even if you specify ReturnsNotAccepted, buyers may still return an item if the item is significantly not as described (SNAD) in the listing. Buyers in the US, UK, and Germany can open an eBay Buyer Protection case for SNAD items.

Here is the current timeline for warning messages and blocked listings:

Change Requests

See the Site Status for bug fixes related to this release. For documentation-related issues, see the Documentation System Announcements.

New Features - 757

This section describes new features that have been added as of this release. New features can involve new calls, new capabilities, and/or new fields added to existing calls.

For logical or functional changes to existing features and calls, including code list changes, see Changed Functionality - 757.

Coming Soon: Motors VIN and VRM Replacing Attributes

eBay has added four new fields (VIN, VINLink, VRM, and VRMLink) to AddItem and related calls. These fields will soon replace the corresponding ID-based attributes for motor vehicle categories on the US eBay Motors site, and the CA, CAFR, UK, and AU sites.

Once these new fields become functional, you should begin migrating your vehicle listing templates to use these fields instead of the attributes. For a short period, eBay will convert VIN and VRM attribute values (along with the vehicle subtitle, deposit type, and deposity amount attribute values) to the corresponding first-class fields in AddItem and related requests, After the migration period, these attributes will be ignored. If you are still only passing in the attributes at that time, some of your vehicle listing requests will fail (depending on the model year) if your request is missing the new VIN field.

Once the migration has occurred for a given listing, GetItem will only return the new fields (not the attributes).

Keep an eye on these release notes for an update on when the new fields become functional and the duration of the migration period.

Changed Functionality - 757

This section describes logical or functional changes that have been made to existing functionality, including new code list values and/or changes in validation rules.

Maximum Allowed Compatible Applications Increased

The maximum number of parts compatibilities that may be specified by application (i.e., Item.ItemCompatibilityList.Compatibility) in an AddItem or related call has been increased for the eBay Motors US site (site ID 100). Use GetCategoryFeatures with the feature ID set to CompatibilityEnabled to determine the parts compatibility settings supported for the given site and category.

Store URL Returned in GetUser Call Now Based on Site ID

The domain of the StoreURL URL returned in GetUser is now based on the SITEID header passed in the request and not the seller's registration site. So, the eBay Stores URL for a UK seller will be returned as stores.ebay.fr if 71 (France) is passed in as the SITEID value.

Documentation Changes and Errata - 757

This section lists additional documentation changes and corrections that were made with this release and that are not already mentioned in New Features - 757 and Changed Functionality - 757.

Updated Documentation for the Item.PrivateListing Field

Updated the description for the Item.PrivateListing boolean field. This field can be set with Add/Revise/Relist calls, and it is returned by GetItem and other API calls that return the Item object. If this field is set to 'true', the item title, item ID, and item price is obscured in all post-order Feedback comments left by buyers.

Back to top

Version 753

Index of Changed Calls - 753

Schema Changes - 753

Announcements - 753

New Features - 753

Changed Functionality - 753

Documentation Changes and Errata - 753

For a current list of known issues, see System Announcements and the Knowledge Base.

Index of Changed Calls - 753

These calls were added, modified, deprecated, or affected by documentation changes in this release. The changes are described below as well as in each call's Change History.

New Calls

No new calls in this release.

Changed Calls

• GetSellingManagerSoldListings

Schema Changes - 753

Announcements - 753

Change Requests

See the Site Status for bug fixes related to this release. For documentation-related issues, see the Documentation System Announcements.

New Features - 753

This section describes new features that have been added as of this release. New features can involve new calls, new capabilities, and/or new fields added to existing calls.

For logical or functional changes to existing features and calls, including code list changes, see Changed Functionality - 753.

None for this release.

Changed Functionality - 753

This section describes logical or functional changes that have been made to existing functionality, including new code list values and/or changes in validation rules.

None for this release.

Documentation Changes and Errata - 753

This section lists additional documentation changes and corrections that were made with this release and that are not already mentioned in New Features - 753 and Changed Functionality - 753.

None for this release.

Back to top

Version 747

Index of Changed Calls - 747

Schema Changes - 747

Announcements - 747

New Features - 747

Changed Functionality - 747

Documentation Changes and Errata - 747

For a current list of known issues, see System Announcements and the Knowledge Base.

Index of Changed Calls - 747

These calls were added, modified, deprecated, or affected by documentation changes in this release. The changes are described below as well as in each call's Change History.

New Calls

No new calls in this release.

Changed Calls

• GetMyeBayBuying
• GetMyeBaySelling
• ReviseFixedPriceItem
• ReviseInventoryStatus
• ReviseItem

Schema Changes - 747

Announcements - 747

Change Requests

See the Site Status for bug fixes related to this release. For documentation-related issues, see the Documentation System Announcements.

New Features - 747

This section describes new features that have been added as of this release. New features can involve new calls, new capabilities, and/or new fields added to existing calls.

For logical or functional changes to existing features and calls, including code list changes, see Changed Functionality - 747.

New LocalPickup Flag for GetMyEbayBuying and GetMyEbaySelling Calls

The LocalPickup flag indicates whether the buyer has selected local pickup as the shipping option or the seller has made local pickup available as a shipping option.

Changed Functionality - 747

This section describes logical or functional changes that have been made to existing functionality, including new code list values and/or changes in validation rules.

Limit for Item Revisions Set at 2,000 Per Month

The maximum number of times that an item can be revised per month is 2,000. This affects the ReviseItem, ReviseFixedPriceItem, and ReviseInventoryStatus calls.

Documentation Changes and Errata - 747

This section lists additional documentation changes and corrections that were made with this release and that are not already mentioned in New Features - 747 and Changed Functionality - 747.

Including Original Fields when Revising Shipping Details

Added a note about the best practice of including all original shipping details fields when using the ReviseItem and ReviseFixedPriceItem calls.

Back to top

Version 745

Index of Changed Calls - 745

Schema Changes - 745

Announcements - 745

New Features - 745

Changed Functionality - 745

Documentation Changes and Errata - 745

For a current list of known issues, see System Announcements and the Knowledge Base.

Index of Changed Calls - 745

These calls were added, modified, deprecated, or affected by documentation changes in this release. The changes are described below as well as in each call's Change History.

New Calls

No new calls in this release.

Changed Calls

• GetItem
• GetUserPreferences
• SetUserPreferences

Schema Changes - 745

Announcements - 745

Change Requests

See the Site Status for bug fixes related to this release. For documentation-related issues, see the Documentation System Announcements.

New Features - 745

This section describes new features that have been added as of this release. New features can involve new calls, new capabilities, and/or new fields added to existing calls.

For logical or functional changes to existing features and calls, including code list changes, see Changed Functionality - 745.

New SoldAsBin Flag in GetItem

New SoldAsBin flag in GetItem call indicates when an auction listing has ended before the stated auction end time due to a buyer using the Buy It Now option to purchase the item.

New Charity Refund Request Preference

New AutoOptDonationRefund flag in SetUserPreferences call allows a seller to request that eBay automatically request eBay Giving Works donation refunds after Unpaid Item cases are opened and closed through the Unpaid Item Assistant mechanism without payment. This preference is only applicable to charity listings.

Changed Functionality - 745

This section describes logical or functional changes that have been made to existing functionality, including new code list values and/or changes in validation rules.

None for this release.

Documentation Changes and Errata - 745

This section lists additional documentation changes and corrections that were made with this release and that are not already mentioned in New Features - 745 and Changed Functionality - 745.

Added Tip About Using GetOrders

Added a note in GetOrders documentation about using and setting the CreateTimeTo filter back two minutes from current time. It is possible that GetOrders will return incomplete/inaccurate data for a multiple line item order if that order is created within a minute or so of that GetOrders call.

More Detailed Information About Shipping Categories

Added more detailed information about shipping categories in the GeteBayDetails documentation. Specifically, updates were made to the ShippingServiceDetails and ShippingCategoryDetails containers.

Back to top

Version 743

Index of Changed Calls - 743

Schema Changes - 743

Announcements - 743

New Features - 743

Changed Functionality - 743

Documentation Changes and Errata - 743

For a current list of known issues, see System Announcements and the Knowledge Base.

Index of Changed Calls - 743

These calls were added, modified, deprecated, or affected by documentation changes in this release. The changes are described below as well as in each call's Change History.

New Calls

No new calls in this release.

Changed Calls

• AddFixedPriceItem
• AddItem
• AddItems
• GetMemberMessages
• GetMyMessages
• RelistFixedPriceItem
• RelistItem
• ReviseFixedPriceItem
• ReviseItem
• VerifyAddFixedPriceItem
• VerifyAddItem
• VerifyRelistItem

Schema Changes - 743

Announcements - 743

Preview of Upcoming Shipping APIs

Samuel Au, a Manager of Software Development in eBay's Shipping team, gave a great demo at Innovate that previewed a new, unified shipping solution on eBay. See Fun and Commerce with eBay's Shipping Platform for information about what's coming! There's a link to a video of the full presentation there, too!

Tips on Apps Sellers Need for Managing Resolutions

When something goes wrong with an order, sellers need apps that offer efficient and effective processes to turn the customer experience back around and make it right. At Innovate, Bijal Shah, an eBay product manager, walked us through the kinds of apps that sellers need, and the APIs that are available to help developers help sellers manage their cases effectively. See Help Sellers Protect Their ROI with Proactive Claims Management for tips from Bijal (including a link to the video).

Help Sellers Add Products to eBay's Catalog

eBay offers an extensive library of well-known products, which you can use to include product details in your listings. But sometimes the catalog doesn't contain the product you're looking for. So, eBay recently opened up the ability to add products to the eBay catalog. See APIs for eBay Catalogs for a summary of these APIs from Bala Parthasarathy, Sr. Product Manager, eBay Catalogs. You'll find a link to the presentation video at the end.

Getting Started with eBay's APIs

If you're a new eBay developer, check out these two intro sessions from Innovate 2011 to learn more about how to get started with our APIs, and your options for selling! Read the summaries here, and go to the end of the summaries for links to the presentation videos!

• In API 101 - Getting Down to Business on eBay, Rekha Patel from eBay's DTS team and Neil Mansilla from Mashery (who is also an eBay Star Developer award winner and the creator of ah!TEXT Mobile Messenger) describe the basics of eBay's APIs.
• In Selling on eBay: An Overview of the APIs, Dilip Varadarajan, a Senior Manager of Software Development at eBay, gave an overview of using eBay's selling APIs and related functionality.

Change Requests

See the Site Status for bug fixes related to this release. For documentation-related issues, see the Documentation System Announcements.

New Features - 743

This section describes new features that have been added as of this release. New features can involve new calls, new capabilities, and/or new fields added to existing calls.

For logical or functional changes to existing features and calls, including code list changes, see Changed Functionality - 743.

Coming Soon: Motors Subtitle and Deposit Fields Replacing Attributes

eBay has added three new fields (SellerProvidedTitle, DepositAmount, and DepositType) to AddItem and related calls. These fields will soon replace the US and Canada eBay Motors Subtitle attribute (10246), and the US eBay Motors deposit amount and type attributes (10733 and 10734). The attributes will continue to work for a period of time to give developers time to migrate to the new fields. Keep an eye on these release notes for information about when the new fields will be functional.

Two New Member Message Types Added for Classified Ad Listings

ClassifiedsContactSeller and ClassifiedsBestOffer added as new message types. ClassifiedsContactSeller indicates that an inquiry has been sent to the seller regarding the corresponding classified ad listing. ClassifiedsBestOffer indicates that a best offer has been made on the seller's corresponding classified ad listing.

Changed Functionality - 743

This section describes logical or functional changes that have been made to existing functionality, including new code list values and/or changes in validation rules.

None for this release.

Documentation Changes and Errata - 743

This section lists additional documentation changes and corrections that were made with this release and that are not already mentioned in New Features - 743 and Changed Functionality - 743.

None for this release.

Back to top

Version 741

Index of Changed Calls - 741

Schema Changes - 741

Announcements - 741

New Features - 741

Changed Functionality - 741

Documentation Changes and Errata - 741

For a current list of known issues, see System Announcements and the Knowledge Base.

Index of Changed Calls - 741

These calls were added, modified, deprecated, or affected by documentation changes in this release. The changes are described below as well as in each call's Change History.

New Calls

No new calls in this release.

Changed Calls

• AddDispute
• GetDispute
• GetItemTransactions
• GetMyeBayBuying
• GetMyeBaySelling
• GetOrders
• GetOrderTransactions
• GetSellerTransactions
• GetSellingManagerSaleRecord
• GetUserDisputes

Schema Changes - 741

Announcements - 741

Change Requests

See the Site Status for bug fixes related to this release. For documentation-related issues, see the Documentation System Announcements.

New Features - 741

This section describes new features that have been added as of this release. New features can involve new calls, new capabilities, and/or new fields added to existing calls.

For logical or functional changes to existing features and calls, including code list changes, see Changed Functionality - 741.

New Payment Status Value Added

A new value of "Paid" can now be returned in GetOrders (and other order retrieval calls) when checkout is complete and order has been paid for by the buyer. This value is returned in the CheckoutStatus.eBayPaymentStatus field. This value may also be returned in the MyeBaySelling and MyeBayBuying calls.

New Dispute Explanation Added

A new dispute explanation was added and available to use through the AddDispute call. The value is "SellerRanOutOfStock", and this value can be used by the seller when cancelling an order due to an item being out of stock.

Changed Functionality - 741

This section describes logical or functional changes that have been made to existing functionality, including new code list values and/or changes in validation rules.

None for this release.

Documentation Changes and Errata - 741

This section lists additional documentation changes and corrections that were made with this release and that are not already mentioned in New Features - 741 and Changed Functionality - 741.

Set InventoryTrackingMethod in RelistFixedPriceItem

The docs will soon be updated to clarify that even if you previously set InventoryTrackingMethod to SKU in AddFixedPriceItem, you need to reset InventoryTrackingMethod to SKU if you relist the item. Otherwise, the listing will only use ItemID as the tracking method.

IncludeConfidence Requires CategoryID in GetCategorySpecifics

The docs will soon be updated to clarify that CategoryID is required when you use IncludeConfidence in GetCategorySpecifics. In effect, this means that IncludeConfidence cannot be used with CategorySpecificsFileInfo (assuming you are using CategorySpecificsFileInfo to download item specifics data for all categories).

Back to top

Version 739

Index of Changed Calls - 739

Schema Changes - 739

Announcements - 739

New Features - 739

Changed Functionality - 739

Documentation Changes and Errata - 739

For a current list of known issues, see System Announcements and the Knowledge Base.

Index of Changed Calls - 739

These calls were added, modified, deprecated, or affected by documentation changes in this release. The changes are described below as well as in each call's Change History.

New Calls

No new calls in this release.

Changed Calls

• GetItemTransactions
• GetOrders
• GetOrderTransactions
• GetSellerTransactions

Schema Changes - 739

Announcements - 739

Change Requests

See the Site Status for bug fixes related to this release. For documentation-related issues, see the Documentation System Announcements.

New Features - 739

This section describes new features that have been added as of this release. New features can involve new calls, new capabilities, and/or new fields added to existing calls.

For logical or functional changes to existing features and calls, including code list changes, see Changed Functionality - 739.

GetOrders Now Retrieves Seller's Item and Shipping Discounts

Information on one or more item or shipping discounts can now be retrieved using GetOrders and other order retrieval calls.

Changed Functionality - 739

This section describes logical or functional changes that have been made to existing functionality, including new code list values and/or changes in validation rules.

None for this release.

Documentation Changes and Errata - 739

This section lists additional documentation changes and corrections that were made with this release and that are not already mentioned in New Features - 739 and Changed Functionality - 739.

None for this release.

Back to top

Version 737

Index of Changed Calls - 737

Schema Changes - 737

Announcements - 737

New Features - 737

Changed Functionality - 737

Documentation Changes and Errata - 737

For a current list of known issues, see System Announcements and the Knowledge Base.

Index of Changed Calls - 737

These calls were added, modified, deprecated, or affected by documentation changes in this release. The changes are described below as well as in each call's Change History.

New Calls

No new calls in this release.

Changed Calls

• GetCategoryFeatures

Schema Changes - 737

Announcements - 737

Change Requests

See the Site Status for bug fixes related to this release. For documentation-related issues, see the Documentation System Announcements.

New Features - 737

This section describes new features that have been added as of this release. New features can involve new calls, new capabilities, and/or new fields added to existing calls.

For logical or functional changes to existing features and calls, including code list changes, see Changed Functionality - 737.

Product Identifier Features Now Returned in GetCategoryFeautures

Call GetCategoryFeatures to see if a site or category supports the ability to pass in Brand/MPN, EAN, ISBN, or UPC values in an Add/Revise/Relist call.

Changed Functionality - 737

This section describes logical or functional changes that have been made to existing functionality, including new code list values and/or changes in validation rules.

None for this release.

Documentation Changes and Errata - 737

This section lists additional documentation changes and corrections that were made with this release and that are not already mentioned in New Features - 737 and Changed Functionality - 737.

None for this release.

Back to top

Version 735

Index of Changed Calls - 735

Schema Changes - 735

Announcements - 735

New Features - 735

Changed Functionality - 735

Documentation Changes and Errata - 735

For a current list of known issues, see System Announcements and the Knowledge Base.

Index of Changed Calls - 735

These calls were added, modified, deprecated, or affected by documentation changes in this release. The changes are described below as well as in each call's Change History.

New Calls

No new calls in this release.

Changed Calls

• AddFixedPriceItem
• AddItem
• AddItems
• GetBidderList
• GeteBayDetails
• GetItem
• GetItemRecommendations
• GetItemTransactions
• GetOrders
• GetOrderTransactions
• GetSellerList
• GetSellerTransactions
• GetSellingManagerSaleRecord
• GetSellingManagerSoldListings
• RelistFixedPriceItem
• RelistItem
• ReviseFixedPriceItem
• ReviseItem
• VerifyAddFixedPriceItem
• VerifyAddItem
• VerifyRelistItem

Schema Changes - 735

Announcements - 735

Change Requests

See the Site Status for bug fixes related to this release. For documentation-related issues, see the Documentation System Announcements.

New Features - 735

This section describes new features that have been added as of this release. New features can involve new calls, new capabilities, and/or new fields added to existing calls.

For logical or functional changes to existing features and calls, including code list changes, see Changed Functionality - 735.

New US/CA Ticket Catalog, and Conversion of Tickets to Custom item Specifics

As previously announced, eBay's new tickets catalog helps US and CA sellers specify key details about tickets and the event, including required custom item specifics (Number of Tickets and Venue State/Province).

To support these changes, eBay has made changes to the US and CA Tickets category structure. eBay will perform a one-time migration to move existing listings from the Event Tickets (16122) category into one of four new categories based on the Event Type item specific in the listing: Sports (173633), Concerts (173634), Theater (173635), or Other (1306). Listings in Experiences (16071) will be merged into Other (1306). After that, new listings need to use the new categories.

Sellers can now begin listing against the new tickets catalog. eBay will perform a one-time migration to convert old product details in existing listings to use the new catalog's product details instead.

Along with the above changes, eBay also now supports custom item specifics for US and CA ticket categories.

For more details about these changes and how they affect the API, see Ticket Listings in the Trading API Guide.

The following example shows how to add ticket details in AddItem with product details and custom item specifics:

<ProductListingDetails>
  <TicketListingDetails>
    <EventTitle>Toronto Argonauts vs Saskatchewan Roughriders</EventTitle>
    <PrintedDate>20110818</PrintedDate>
    <PrintedTime>7:30 PM</PrintedTime>
    <Venue>Rogers Centre</Venue>
  </TicketListingDetails>
  <IncludeStockPhotoURL>true</IncludeStockPhotoURL>
  <IncludePrefilledItemInformation>true</IncludePrefilledItemInformation>
  <UseStockPhotoURLAsGallery>true</UseStockPhotoURLAsGallery>
</ProductListingDetails>
<ItemSpecifics>
  <NameValueList>
    <Name>Number of Tickets</Name>
    <Value>4</Value>
  </NameValueList>
  <NameValueList>
    <Name>Section</Name>
    <Value>200</Value>
  </NameValueList>
  <NameValueList>
    <Name>Row</Name>
    <Value>12</Value>
  </NameValueList>
  <NameValueList>
    <Name>Venue State/Province</Name>
    <Value>ON</Value>
  </NameValueList>
</ItemSpecifics>

New Payout Process Begins for New Seller Accounts on DE/AT Sites

As previously announced, the new payment process on DE/AT sites starts August 22. Beginning August 22, GetOrders and other order retrieval API calls will return relevant information to DE and AT sellers subject to the new payment process. Additionally, two new eBay notifications, ReadyToShip and ReadyForPayout have been created.

There is also a new Payout Details API available. The Payout Details API has two calls: getOrderPayoutDetails (available now) and getPayoutDetails (available in 737). Both of these calls can be tested in the Sandbox beginning September 1. The documentation for the Payout Details API can be found at: http://developer.ebay.com/DevZone/payout-details/CallRef/index.html

Changed Functionality - 735

This section describes logical or functional changes that have been made to existing functionality, including new code list values and/or changes in validation rules.

GeteBayDetails Updates for Return Policies

GeteBayDetails returns MoneyBackOrExchange in RefundOption, and you can pass it in the AddItem family of calls.

See New Guidelines and Options for Return Policies) in the 729 release notes for additional information about changes that will go into effect in production in 2012.

Documentation Changes and Errata - 735

This section lists additional documentation changes and corrections that were made with this release and that are not already mentioned in New Features - 735 and Changed Functionality - 735.

None for this release.

Back to top

Version 733

Index of Changed Calls - 733

Schema Changes - 733

Announcements - 733

New Features - 733

Changed Functionality - 733

Documentation Changes and Errata - 733

For a current list of known issues, see System Announcements and the Knowledge Base.

Index of Changed Calls - 733

These calls were added, modified, deprecated, or affected by documentation changes in this release. The changes are described below as well as in each call's Change History.

New Calls

No new calls in this release.

Changed Calls

• AddFixedPriceItem
• AddItem
• RelistFixedPriceItem
• RelistItem
• ReviseFixedPriceItem
• ReviseItem
• VerifyAddItem
• VerifyRelistItem

Schema Changes - 733

Announcements - 733

Change Requests

See the Site Status for bug fixes related to this release. For documentation-related issues, see the Documentation System Announcements.

New Features - 733

This section describes new features that have been added as of this release. New features can involve new calls, new capabilities, and/or new fields added to existing calls.

For logical or functional changes to existing features and calls, including code list changes, see Changed Functionality - 733.

Product Suggestions When Listing

Note: This feature is available to a small subset of eBay-selected sellers.

To facilitate the use of eBay catalogs for listing items, the AddItem family of calls will return product suggestions (ProductSuggestiion) in the response to indicate there is an item in the catalog that matches the item details in the request.

Sellers can set UseRecommendedProduct to true to allow eBay to list their item using a product from the eBay catalog when the product is a match for the seller's item. This is like using ProductListingDetails to list an item. Applies only to catalog-enabled categories.

Coming Soon: New Payment Process Begins for New Sellers on DE/AT Sites

Starting August 22, a new payment process begins for new sellers listing on the German and Austrian sites.

Changed Functionality - 733

This section describes logical or functional changes that have been made to existing functionality, including new code list values and/or changes in validation rules.

Parts Compatibility Supported in Production by eBay Germany Site

Parts compatibility APIs are now fully supported on the eBay Germany site (site ID 77), in addition to the eBay US Motors Site (site ID 100). Parts Compatibility is supported in both the Sandbox and in the Production environments for these sites.

To identify categories in which you can list items with parts compatibility, submit a GetCategoryFeatures request to the given eBay site with the parts compatibility feature IDs (CompatibilityEnabled, MinCompatibleApplications, MaxCompatibleApplications) and ViewAllNodes set to true. See Listing Items with Parts Compatibility for more information.

When items are listed with parts compatibility by application on the eBay Germany site, users can use K type vehicle specification numbers to specify a compatibility:

<Compatibility>
  <NameValueList>
    <Name>KType</Name>
    <Value>10006</Value>
  </NameValueList>
  <CompatibilityNotes>Passt alle ordnungen.</CompatibilityNotes>
</Compatibility>

K type is a vehicle specification numbering system provided by TecDoc Informations Systems. For more information about TecDoc and the K type numbering system, see the TecDoc Portal.

Note: One notable difference for Parts Compatibility on the eBay Germany site is the use of Production Period (a range of years in which the given vehicle was produced)instead of Year as a compatibility property. If the production period covers 4 years (see following examples), then the compatibility counts as 4 of the maximum allowed item compatibilities.

Example of Production Period values that describe a range of 4 years:

• <Value>2008/07-</Value>: Vehicles produced from July of 2008 to the present
• <Value>2003/04-2006/10</Value>: Vehicles produced from April of 2003 to October of 2006

Although the maximum allowed number of item compatibilities has been increased to 1,000 for the eBay Germany site, it is important to implement a counter into your application to prevent sellers from specifying more than the maximum number of compatibilities for an item. An AddItem request will fail if the number of compatibilities specified exceeds the maximum allowed. GetItem returns ItemCompatibilityCount, which can help you monitor the number of compatibilities specified for an item.

Documentation Changes and Errata - 733

This section lists additional documentation changes and corrections that were made with this release and that are not already mentioned in New Features - 733 and Changed Functionality - 733.

None for this release.

Back to top

Version 731

Index of Changed Calls - 731

Schema Changes - 731

Announcements - 731

New Features - 731

Changed Functionality - 731

Documentation Changes and Errata - 731

For a current list of known issues, see System Announcements and the Knowledge Base.

Index of Changed Calls - 731

These calls were added, modified, deprecated, or affected by documentation changes in this release. The changes are described below as well as in each call's Change History.

New Calls

No new calls in this release.

Changed Calls

No changed calls in this release.

Schema Changes - 731

Announcements - 731

Coming Soon: New Payment Process Begins for New Sellers on DE/AT Sites

Starting August 22, a new payment process begins for new sellers listing on the German and Austrian sites.

Change Requests

See the Site Status for bug fixes related to this release. For documentation-related issues, see the Documentation System Announcements.

New Features - 731

This section describes new features that have been added as of this release. New features can involve new calls, new capabilities, and/or new fields added to existing calls.

For logical or functional changes to existing features and calls, including code list changes, see Changed Functionality - 731.

Required Item Specifics for Fashion are Now Live

As described in Item Specifics Required for Fashion; No ID-Based Attributes, listings in many Clothing, Shoes & Accessories categories (also known as Fashion categories) on the US and CA sites need to include custom item specifics for Style, Brand, Size Type, and Size. Although Color and Shade are not required, they are strongly recommended. Similarly, Brand and Size are required on EU sites. As stated before, these names can vary by category. For example, in Women's Tops on the US site, "Size" is called "Size (Women's)".

Changed Functionality - 731

This section describes logical or functional changes that have been made to existing functionality, including new code list values and/or changes in validation rules.

None for this release.

Documentation Changes and Errata - 731

This section lists additional documentation changes and corrections that were made with this release and that are not already mentioned in New Features - 731 and Changed Functionality - 731.

None for this release.

Back to top

Version 729

Index of Changed Calls - 729

Schema Changes - 729

Announcements - 729

New Features - 729

Changed Functionality - 729

Documentation Changes and Errata - 729

For a current list of known issues, see System Announcements and the Knowledge Base.

Index of Changed Calls - 729

These calls were added, modified, deprecated, or affected by documentation changes in this release. The changes are described below as well as in each call's Change History.

New Calls

No new calls in this release.

Changed Calls

• AddFixedPriceItem
• AddItem
• AddItems
• AddSellingManagerTemplate
• GetCategorySpecifics
• GetItemRecommendations
• RelistItem
• ReviseItem
• VerifyAddItem
• VerifyRelistItem

Schema Changes - 729

Announcements - 729

Reminder: Required Item Specifics for Fashion Starting July 20

See Item Specifics Required for Fashion; No ID-Based Attributes in the 727 release notes below for details.

Coming Soon: New Guidelines and Options for Return Policies

New guidelines for returns are coming soon. eBay's 2011 Fall Seller Update describes how these guidelines will affect sellers:

Return Policy Update
http://pages.ebay.com/sellerinformation/news/returnsupdate.html

Starting in late August, GeteBayDetails and the AddItem family of calls will be changed in the following ways to support the new guidelines.

RefundOption: A money back refund choice will be required for all returns. To support this:

• In early 2012, the MerchandiseCredit and Exchange options will be deprecated as separate options, and GeteBayDetails will stop returning these options in production. To help you with early testing, GeteBayDetails will stop returning them in the sandbox in late August 2011.
• In late August 2011, GeteBayDetails will start returning a new "Money Back or Exchange" option in production and the sandbox. This option indicates that the buyer will have the choice to ask for either money back or exchange for the item they wish to return. Consider using this option when you have the depth of inventory to support an exchange for a different size, color, or undamaged unit. Otherwise, use the existing MoneyBack option if you have limited inventory.

ReturnsWithinOption: In early 2012, the 3-day and 7-day choices will be deprecated, and GeteBayDetails will stop returning these options in production. To help you with early testing, GeteBayDetails will stop returning them in the sandbox in late August 2011.

Of course, we'll continue to support ReturnsNotAccepted as a policy. As always, even if you specify ReturnsNotAccepted, buyers may still return items if they don't match the item description and the buyer files an eBay Buyer Protection (dispute resolution) case.

In early 2012, we will block all AddItem, AddFixedPriceItem, RelistItem, and RelistFixedPriceItem calls for listings with deprecated refund and returns within options. Later in 2012, if any GTC listings still have non-compliant options, eBay will convert them during auto-renewal to use the default options (e.g., 14 days). To help you with early testing, these calls will be blocked in the sandbox before they're blocked in production. (Keep an eye on the developer blog for the timing.)

Here is a summary of the timeline for the API changes eBay will make:

Coming Soon: New US/CA Ticket Catalog, and Conversion of Tickets to Custom item Specifics

Starting August 22, a new tickets catalog will help US and CA sellers specify key details about tickets and the event, including required item specifics (Number of Tickets and Venue State/Province).

To support these changes, eBay will make changes to the US and CA Tickets category structure. eBay will perform a one-time migration to move existing listings from the Event Tickets (16122) category into one of four new categories based on the Event Type item specific in the listing: Sports (173633), Concerts (173634), Theater (173635), or Other (1306). Listings in Experiences (16071) will be merged into Other (1306). After that, new listings need to use the new categories.

On August 22, sellers will also begin listing against a new tickets catalog. eBay will perform a one-time migration to convert old product details in existing listings to use the new catalog's product details instead.

Along with the above changes, eBay will also support custom item specifics for US and CA ticket categories.

For more details about these changes and how they will affect the API, see Ticket Listings in the Trading API Guide.

Coming Soon: Maximum Length of Item Title Increasing to 80 Characters

Starting the first week of September, the number of characters available for item titles will increase from 55 to 80.

For details about these changes, see our 2011 Fall Seller Update:

Longer Listing Titles
http://pages.ebay.com/sellerinformation/news/titlexpansion.html

Coming Soon: New Payment Process Begins for New Sellers on DE/AT Sites

Starting August 22, a new payment process begins for new sellers listing on the German and Austrian sites.

Reminder: Third-Party Checkout No Longer Supported

As of July 1, 2011, Third-Party Checkout is no longer supported. Sellers can no longer list items with the ThirdParyCheckout flag set to true. However, if this field was set to True at listing time (prior to July 1), the user must include this field and set it to False when relisting or revising the item.

Change Requests

See the Site Status for bug fixes related to this release. For documentation-related issues, see the Documentation System Announcements.

New Features - 729

This section describes new features that have been added as of this release. New features can involve new calls, new capabilities, and/or new fields added to existing calls.

For logical or functional changes to existing features and calls, including code list changes, see Changed Functionality - 729.

Notifications and Client Alerts Now Support Up to 25 Simultaneous Delivery URLs

List delivery URLs using instances of ApplicationDeliveryPreferences.DeliveryURLDetails.DeliveryURLName, and then enable them by including up to 25 of them in comma-separated format in DeliveryURLName in your SetNotificationPreferences request. Formerly, you could only include a single delivery URL name, which overwrote delivery URL names from previous requests.

New Value Data Type and Formats in Item Specifics Recommendations

ValueType now supports Date as a data type for custom item specifics. The recommended date format (e.g., YYYYMMDD) is returned in a new ValueFormat field. GetCategorySpecifics and GetItemRecommendations will begin returning these values when ticket, real estate, and other categories are converted from ID-based attributes to custom item specifics in the future.

Changed Functionality - 729

This section describes logical or functional changes that have been made to existing functionality, including new code list values and/or changes in validation rules.

No other changes in this release.

Documentation Changes and Errata - 729

This section lists additional documentation changes and corrections that were made with this release and that are not already mentioned in New Features - 729 and Changed Functionality - 729.

None for this release.

User-Contributed Notes

This documentation and the API may only be used in accordance with the eBay Developers Program and API License Agreement.

© 2005–2011 eBay Inc. All rights reserved.
eBay and the eBay logo are registered trademarks of eBay Inc.
All other brands are the property of their respective owners.