Component 
SUMMARY: XML REP | DERIVED | USE
DETAIL: DESC | XML SRC | TYPE | ATTR | CHILD
eBay Trading API

complexType "ns:ItemType"
Namespace:
Content:
complex, 140 elements, elem. wildcard
Defined:
globally in Schema in ebaySvc.wsdl; see XML source
Includes:
definitions of 140 elements, elem. wildcard
Used:
at 23 locations
Component Diagram
XML Representation Summary
<...>
   
Content: 
ns:ApplicationData?, ns:AttributeSetArray?, ns:AttributeArray?, ns:LookupAttributeArray?, ns:AutoPay?, ns:BiddingDetails?, ns:BuyerProtection?, ns:BuyItNowPrice?, ns:CategoryMappingAllowed?, ns:Charity?, ns:Country?, ns:CrossPromotion?, ns:Currency?, ns:Description?, ns:DescriptionReviseMode?, ns:Distance?, ns:HitCounter?, ns:ItemID?, ns:ListingDetails?, ns:ListingDuration?, ns:ListingEnhancement*, ns:ListingType?, ns:Location?, ns:LotSize?, ns:PartnerCode?, ns:PartnerName?, ns:PaymentDetails?, ns:PaymentMethods*, ns:PayPalEmailAddress?, ns:PrimaryCategory?, ns:PrivateListing?, ns:ProductListingDetails?, ns:Quantity?, ns:PrivateNotes?, ns:RegionID?, ns:RelistLink?, ns:ReservePrice?, ns:ReviseStatus?, ns:ScheduleTime?, ns:SecondaryCategory?, ns:FreeAddedCategory?, ns:Seller?, ns:SellingStatus?, ns:ShippingDetails?, ns:ShipToLocations*, ns:Site?, ns:StartPrice?, ns:Storefront?, ns:SubTitle?, ns:TimeLeft?, ns:Title?, ns:UUID?, ns:VATDetails?, ns:SellerVacationNote?, ns:WatchCount?, ns:HitCount?, ns:DisableBuyerRequirements?, ns:BestOfferDetails?, ns:LocationDefaulted?, ns:UseTaxTable?, ns:GetItFast?, ns:BuyerResponsibleForShipping?, ns:LimitedWarrantyEligible?, ns:eBayNotes?, ns:QuestionCount?, ns:Relisted?, ns:QuantityAvailable?, ns:SKU?, ns:SearchDetails?, ns:PostalCode?, ns:PictureDetails?, ns:VideoDetails?, ns:DispatchTimeMax?, ns:BestOfferEnabled?, ns:LocalListing?, ns:SellerContactDetails?, ns:TotalQuestionCount?, ns:ProxyItem?, ns:ExtendedSellerContactDetails?, ns:LeadCount?, ns:NewLeadCount?, ns:ItemSpecifics?, ns:GroupCategoryID?, ns:ClassifiedAdPayPerLeadFee?, ns:BidGroupItem?, ns:ApplyBuyerProtection?, ns:ListingSubtype2?, ns:MechanicalCheckAccepted?, ns:UpdateSellerInfo?, ns:UpdateReturnPolicy?, ns:ItemPolicyViolation?, ns:CrossBorderTrade*, ns:BusinessSellerDetails?, ns:BuyerGuaranteePrice?, ns:BuyerRequirementDetails?, ns:ReturnPolicy?, ns:PaymentAllowedSite*, ns:InventoryTrackingMethod?, ns:IntegratedMerchantCreditCardEnabled?, ns:Variations?, ns:ItemCompatibilityList?, ns:ItemCompatibilityCount?, ns:ConditionID?, ns:ConditionDescription?, ns:ConditionDisplayName?, ns:TaxCategory?, ns:QuantityAvailableHint?, ns:QuantityThreshold?, ns:DiscountPriceInfo?, ns:SellerProvidedTitle?, ns:VIN?, ns:VINLink?, ns:VRM?, ns:VRMLink?, ns:QuantityInfo?, ns:SellerProfiles?, ns:ShippingServiceCostOverrideList?, ns:ShippingOverride?, ns:ShippingPackageDetails?, ns:TopRatedListing?, ns:QuantityRestrictionPerBuyer?, ns:FloorPrice?, ns:CeilingPrice?, ns:IsIntermediatedShippingEligible?, ns:UnitInfo?, ns:RelistParentID?, ns:ConditionDefinition?, ns:HideFromSearch?, ns:ReasonHideFromSearch?, ns:PickupInStoreDetails?, ns:SiteId?, ns:IgnoreQuantity?, ns:AvailableForPickupDropOff?, ns:EligibleForPickupDropOff?, ns:LiveAuction?, ns:DigitalGoodInfo?, ns:eBayPlus?, ns:eBayPlusEligible?, ns:eMailDeliveryAvailable?, ns:IsSecureDescription?, {any}*
</...>
All Direct / Indirect Based Elements (23):
ns:Item (defined in ns:CartItemType complexType),
ns:Item (defined in ns:DisputeType complexType),
ns:Item (defined in ns:ItemArrayType complexType),
ns:Item (defined in ns:TransactionType complexType),
Known Usage Locations
Annotation
Contains the data defining one item. A seller populates an object of this type at listing time with the definition of a new item. A seller also uses an object of this type to relist or revise an item. Calls that retrieve item data (such as the GetSellerList call) return an object of this type, filled with the item's data.
XML Source (w/o annotations (141); see within schema source)
<xs:complexType name="ItemType">
<xs:sequence>
<xs:element minOccurs="0" name="ApplicationData" type="xs:string"/>
<xs:element minOccurs="0" name="AttributeSetArray" type="ns:AttributeSetArrayType"/>
<xs:element minOccurs="0" name="AttributeArray" type="ns:AttributeArrayType"/>
<xs:element minOccurs="0" name="LookupAttributeArray" type="ns:LookupAttributeArrayType"/>
<xs:element minOccurs="0" name="AutoPay" type="xs:boolean"/>
<xs:element minOccurs="0" name="BiddingDetails" type="ns:BiddingDetailsType"/>
<xs:element minOccurs="0" name="BuyerProtection" type="ns:BuyerProtectionCodeType"/>
<xs:element minOccurs="0" name="BuyItNowPrice" type="ns:AmountType"/>
<xs:element default="false" minOccurs="0" name="CategoryMappingAllowed" type="xs:boolean"/>
<xs:element minOccurs="0" name="Charity" type="ns:CharityType"/>
<xs:element minOccurs="0" name="Country" type="ns:CountryCodeType"/>
<xs:element minOccurs="0" name="CrossPromotion" type="ns:CrossPromotionsType"/>
<xs:element minOccurs="0" name="Currency" type="ns:CurrencyCodeType"/>
<xs:element minOccurs="0" name="Description" type="xs:string"/>
<xs:element minOccurs="0" name="DescriptionReviseMode" type="ns:DescriptionReviseModeCodeType"/>
<xs:element minOccurs="0" name="Distance" type="ns:DistanceType"/>
<xs:element minOccurs="0" name="HitCounter" type="ns:HitCounterCodeType"/>
<xs:element minOccurs="0" name="ItemID" type="ns:ItemIDType"/>
<xs:element minOccurs="0" name="ListingDetails" type="ns:ListingDetailsType"/>
<xs:element minOccurs="0" name="ListingDuration" type="xs:token"/>
<xs:element maxOccurs="unbounded" minOccurs="0" name="ListingEnhancement" type="ns:ListingEnhancementsCodeType"/>
<xs:element minOccurs="0" name="ListingType" type="ns:ListingTypeCodeType"/>
<xs:element minOccurs="0" name="Location" type="xs:string"/>
<xs:element minOccurs="0" name="LotSize" type="xs:int"/>
<xs:element minOccurs="0" name="PartnerCode" type="xs:string"/>
<xs:element minOccurs="0" name="PartnerName" type="xs:string"/>
<xs:element minOccurs="0" name="PaymentDetails" type="ns:PaymentDetailsType"/>
<xs:element maxOccurs="unbounded" minOccurs="0" name="PaymentMethods" type="ns:BuyerPaymentMethodCodeType"/>
<xs:element minOccurs="0" name="PayPalEmailAddress" type="xs:string"/>
<xs:element minOccurs="0" name="PrimaryCategory" type="ns:CategoryType"/>
<xs:element minOccurs="0" name="PrivateListing" type="xs:boolean"/>
<xs:element minOccurs="0" name="ProductListingDetails" type="ns:ProductListingDetailsType"/>
<xs:element minOccurs="0" name="Quantity" type="xs:int"/>
<xs:element minOccurs="0" name="PrivateNotes" type="xs:string"/>
<xs:element minOccurs="0" name="RegionID" type="xs:string"/>
<xs:element minOccurs="0" name="RelistLink" type="xs:boolean"/>
<xs:element minOccurs="0" name="ReservePrice" type="ns:AmountType"/>
<xs:element minOccurs="0" name="ReviseStatus" type="ns:ReviseStatusType"/>
<xs:element minOccurs="0" name="ScheduleTime" type="xs:dateTime"/>
<xs:element minOccurs="0" name="SecondaryCategory" type="ns:CategoryType"/>
<xs:element minOccurs="0" name="FreeAddedCategory" type="ns:CategoryType"/>
<xs:element minOccurs="0" name="Seller" type="ns:UserType"/>
<xs:element minOccurs="0" name="SellingStatus" type="ns:SellingStatusType"/>
<xs:element minOccurs="0" name="ShippingDetails" type="ns:ShippingDetailsType"/>
<xs:element maxOccurs="unbounded" minOccurs="0" name="ShipToLocations" type="xs:string"/>
<xs:element minOccurs="0" name="Site" type="ns:SiteCodeType"/>
<xs:element minOccurs="0" name="StartPrice" type="ns:AmountType"/>
<xs:element minOccurs="0" name="Storefront" type="ns:StorefrontType"/>
<xs:element minOccurs="0" name="SubTitle" type="xs:string"/>
<xs:element minOccurs="0" name="TimeLeft" type="xs:duration"/>
<xs:element minOccurs="0" name="Title" type="xs:string"/>
<xs:element minOccurs="0" name="UUID" type="ns:UUIDType"/>
<xs:element minOccurs="0" name="VATDetails" type="ns:VATDetailsType"/>
<xs:element minOccurs="0" name="SellerVacationNote" type="xs:string"/>
<xs:element minOccurs="0" name="WatchCount" type="xs:long"/>
<xs:element minOccurs="0" name="HitCount" type="xs:long"/>
<xs:element minOccurs="0" name="DisableBuyerRequirements" type="xs:boolean"/>
<xs:element minOccurs="0" name="BestOfferDetails" type="ns:BestOfferDetailsType"/>
<xs:element minOccurs="0" name="LocationDefaulted" type="xs:boolean"/>
<xs:element minOccurs="0" name="UseTaxTable" type="xs:boolean"/>
<xs:element minOccurs="0" name="GetItFast" type="xs:boolean"/>
<xs:element minOccurs="0" name="BuyerResponsibleForShipping" type="xs:boolean"/>
<xs:element minOccurs="0" name="LimitedWarrantyEligible" type="xs:boolean"/>
<xs:element minOccurs="0" name="eBayNotes" type="xs:string"/>
<xs:element minOccurs="0" name="QuestionCount" type="xs:long"/>
<xs:element minOccurs="0" name="Relisted" type="xs:boolean"/>
<xs:element minOccurs="0" name="QuantityAvailable" type="xs:int"/>
<xs:element minOccurs="0" name="SKU" type="ns:SKUType"/>
<xs:element minOccurs="0" name="SearchDetails" type="ns:SearchDetailsType"/>
<xs:element minOccurs="0" name="PostalCode" type="xs:string"/>
<xs:element minOccurs="0" name="PictureDetails" type="ns:PictureDetailsType"/>
<xs:element minOccurs="0" name="VideoDetails" type="ns:VideoDetailsType"/>
<xs:element minOccurs="0" name="DispatchTimeMax" type="xs:int"/>
<xs:element minOccurs="0" name="BestOfferEnabled" type="xs:boolean"/>
<xs:element minOccurs="0" name="LocalListing" type="xs:boolean"/>
<xs:element minOccurs="0" name="SellerContactDetails" type="ns:AddressType"/>
<xs:element minOccurs="0" name="TotalQuestionCount" type="xs:long"/>
<xs:element minOccurs="0" name="ProxyItem" type="xs:boolean"/>
<xs:element minOccurs="0" name="ExtendedSellerContactDetails" type="ns:ExtendedContactDetailsType"/>
<xs:element minOccurs="0" name="LeadCount" type="xs:int"/>
<xs:element minOccurs="0" name="NewLeadCount" type="xs:int"/>
<xs:element minOccurs="0" name="ItemSpecifics" type="ns:NameValueListArrayType"/>
<xs:element minOccurs="0" name="GroupCategoryID" type="xs:string"/>
<xs:element minOccurs="0" name="ClassifiedAdPayPerLeadFee" type="ns:AmountType"/>
<xs:element minOccurs="0" name="BidGroupItem" type="xs:boolean"/>
<xs:element minOccurs="0" name="ApplyBuyerProtection" type="ns:BuyerProtectionDetailsType"/>
<xs:element minOccurs="0" name="ListingSubtype2" type="ns:ListingSubtypeCodeType"/>
<xs:element minOccurs="0" name="MechanicalCheckAccepted" type="xs:boolean"/>
<xs:element minOccurs="0" name="UpdateSellerInfo" type="xs:boolean"/>
<xs:element minOccurs="0" name="UpdateReturnPolicy" type="xs:boolean"/>
<xs:element minOccurs="0" name="ItemPolicyViolation" type="ns:ItemPolicyViolationType"/>
<xs:element maxOccurs="unbounded" minOccurs="0" name="CrossBorderTrade" type="xs:string"/>
<xs:element minOccurs="0" name="BusinessSellerDetails" type="ns:BusinessSellerDetailsType"/>
<xs:element minOccurs="0" name="BuyerGuaranteePrice" type="ns:AmountType"/>
<xs:element minOccurs="0" name="BuyerRequirementDetails" type="ns:BuyerRequirementDetailsType"/>
<xs:element minOccurs="0" name="ReturnPolicy" type="ns:ReturnPolicyType"/>
<xs:element maxOccurs="unbounded" minOccurs="0" name="PaymentAllowedSite" type="ns:SiteCodeType"/>
<xs:element minOccurs="0" name="InventoryTrackingMethod" type="ns:InventoryTrackingMethodCodeType"/>
<xs:element minOccurs="0" name="IntegratedMerchantCreditCardEnabled" type="xs:boolean"/>
<xs:element minOccurs="0" name="Variations" type="ns:VariationsType"/>
<xs:element minOccurs="0" name="ItemCompatibilityList" type="ns:ItemCompatibilityListType"/>
<xs:element minOccurs="0" name="ItemCompatibilityCount" type="xs:int"/>
<xs:element minOccurs="0" name="ConditionID" type="xs:int"/>
<xs:element minOccurs="0" name="ConditionDescription" type="xs:string"/>
<xs:element minOccurs="0" name="ConditionDisplayName" type="xs:string"/>
<xs:element minOccurs="0" name="TaxCategory" type="xs:string"/>
<xs:element minOccurs="0" name="QuantityAvailableHint" type="ns:QuantityAvailableHintCodeType"/>
<xs:element minOccurs="0" name="QuantityThreshold" type="xs:int"/>
<xs:element minOccurs="0" name="DiscountPriceInfo" type="ns:DiscountPriceInfoType"/>
<xs:element minOccurs="0" name="SellerProvidedTitle" type="xs:string"/>
<xs:element minOccurs="0" name="VIN" type="xs:string"/>
<xs:element minOccurs="0" name="VINLink" type="xs:string"/>
<xs:element minOccurs="0" name="VRM" type="xs:string"/>
<xs:element minOccurs="0" name="VRMLink" type="xs:string"/>
<xs:element minOccurs="0" name="QuantityInfo" type="ns:QuantityInfoType"/>
<xs:element minOccurs="0" name="SellerProfiles" type="ns:SellerProfilesType"/>
<xs:element minOccurs="0" name="ShippingOverride" type="ns:ShippingOverrideType"/>
<xs:element minOccurs="0" name="ShippingPackageDetails" type="ns:ShipPackageDetailsType"/>
<xs:element minOccurs="0" name="TopRatedListing" type="xs:boolean"/>
<xs:element minOccurs="0" name="FloorPrice" type="ns:AmountType"/>
<xs:element minOccurs="0" name="CeilingPrice" type="ns:AmountType"/>
<xs:element minOccurs="0" name="IsIntermediatedShippingEligible" type="xs:boolean"/>
<xs:element minOccurs="0" name="UnitInfo" type="ns:UnitInfoType"/>
<xs:element minOccurs="0" name="RelistParentID" type="xs:long"/>
<xs:element minOccurs="0" name="ConditionDefinition" type="xs:string"/>
<xs:element minOccurs="0" name="HideFromSearch" type="xs:boolean"/>
<xs:element minOccurs="0" name="ReasonHideFromSearch" type="ns:ReasonHideFromSearchCodeType"/>
<xs:element minOccurs="0" name="PickupInStoreDetails" type="ns:PickupInStoreDetailsType"/>
<xs:element minOccurs="0" name="SiteId" type="xs:int"/>
<xs:element minOccurs="0" name="IgnoreQuantity" type="xs:boolean"/>
<xs:element minOccurs="0" name="AvailableForPickupDropOff" type="xs:boolean"/>
<xs:element minOccurs="0" name="EligibleForPickupDropOff" type="xs:boolean"/>
<xs:element minOccurs="0" name="LiveAuction" type="xs:boolean"/>
<xs:element minOccurs="0" name="DigitalGoodInfo" type="ns:DigitalGoodInfoType"/>
<xs:element minOccurs="0" name="eBayPlus" type="xs:boolean"/>
<xs:element minOccurs="0" name="eBayPlusEligible" type="xs:boolean"/>
<xs:element minOccurs="0" name="eMailDeliveryAvailable" type="xs:boolean"/>
<xs:element minOccurs="0" name="IsSecureDescription" type="xs:boolean"/>
<xs:any maxOccurs="unbounded" minOccurs="0" processContents="lax"/>
</xs:sequence>
</xs:complexType>
Content Element Detail (all declarations defined in this component; 141/141)
ns:ApplicationData
Type:
xs:string, predefined, simple content
Return custom, application-specific data associated with the item. The data you specify is stored by eBay with the item for your own reference, but it is not used by eBay in any way. Use ApplicationData to store special information for yourself, such as a part number. For a SKU in an eBay.com listing, use the SKU element instead. To remove this value when revising or relisting an item, use DeletedField.
XML Representation Summary
<ns:ApplicationData>
   
Content: 
{ xs:string }
</ns:ApplicationData>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="ApplicationData" type="xs:string"/>

ns:ApplyBuyerProtection
Type:
Different Buyer protection schemes and the various status associated with each one of them.
Component Diagram
XML Representation Summary
<ns:ApplyBuyerProtection>
   
Content: 
</ns:ApplyBuyerProtection>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="ApplyBuyerProtection" type="ns:BuyerProtectionDetailsType"/>

ns:AttributeArray
Type:
ns:AttributeArrayType, complex content
This field has been deprecated, and should no longer be used.
Component Diagram
XML Representation Summary
<ns:AttributeArray>
   
Content: 
</ns:AttributeArray>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="AttributeArray" type="ns:AttributeArrayType"/>

ns:AttributeSetArray
Type:
ns:AttributeSetArrayType, complex content
This field has been deprecated, and should no longer be used.
Component Diagram
XML Representation Summary
<ns:AttributeSetArray>
   
Content: 
</ns:AttributeSetArray>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="AttributeSetArray" type="ns:AttributeSetArrayType"/>

ns:AutoPay
Type:
xs:boolean, predefined, simple content
If true, the seller requests immediate payment for a fixed-price item or an auction item that is purchased with the 'Buy it Now' feature. If false or not specified, immediate payment is not requested. (In responses, does not indicate whether the item is actually still a candidate for purchase via immediate payment.)

For sellers not opted in to eBay managed payments: immediate payment is only available if the eBay marketplace supports PayPal as a payment method, and the listing category supports immediate payment (the AutoPayEnabled should be returned as true in the GetCategories response). To enable the listing with the immediated payment requirement, AutoPay must be true, the PayPalEmailAddress field must be included and must have a valid PayPal email address for the seller, and the only specified PaymentMethods value must be PayPal.

For sellers opted in to eBay managed payments: the only requirement is that the listing category supports immediate payments. With managed payments, eBay handles the payment methods available to the buyer, so the seller will not have to specify any payment methods, and will not have include the PayPalEmailAddress field. The seller only has to include the AutoPay field and set it to true to create an Immediate Payment listing.

If a seller does not wish to require immediate payment, the AutoPay flag is not required since it defaults to false.
XML Representation Summary
<ns:AutoPay>
   
Content: 
{ xs:boolean }
</ns:AutoPay>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="AutoPay" type="xs:boolean"/>

ns:AvailableForPickupDropOff
Type:
xs:boolean, predefined, simple content
This field is only returned if true, and indicates that the 'Click and Collect' feature is available for this item. With Click and Collect, buyers are able to purchase from thousands of sellers on the eBay UK, Australia, and Germany sites, and then pick up their order from the nearest 'eBay Collection Point'. Note that an item may be eligible for Click and Collect, but this logistics option will only surface if the prospective buyer is within the vicinity of an 'eBay Collection Point'.

The Click and Collect feature is only available on the eBay UK, Australia, and Germany sites. For more information about Click and Collect, see the Click and Collect home page on the eBay UK site, the Click and Collect home page on the eBay Australia site, or the Click and Collect home page on the eBay Germany site.

Not all categories on the UK, Australia, and Germany sites support Click and Collect listings. To verify if a specific category on these eBay sites support Click and Collect listings, use the GetCategoryFeatures call, passing in one or more CategoryID values and a PickupDropOffEnabled value in the FeatureID field.

Look for a true value in the PickupDropOffEnabled field of the corresponding Category node (match up the CategoryID values if more than one Category IDs were passed in the request).

Note: For Click and Collect eligible sellers, the Click and Collect feature can only be enabled at the account level, and then each of the seller's listings will be automatically evaluated for Click and Collect eligibility.
XML Representation Summary
<ns:AvailableForPickupDropOff>
   
Content: 
{ xs:boolean }
</ns:AvailableForPickupDropOff>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="AvailableForPickupDropOff" type="xs:boolean"/>

ns:BestOfferDetails
Type:
ns:BestOfferDetailsType, complex content
For Add/Revise/Relist/Verify calls: This container is used to enable the Best Offer feature on a listing. Note that the Best Offer feature can be set for auction listings on the US, Canada, UK, Germany, Australia, France, Italy, and Spain marketplaces, but a seller can only use Best Offer or Buy It Now, but not both. Once an auction listing receives a qualifying bid, the Best Offer feature will be turned off and any pending Best Offers or Counteroffers will no longer be valid.

For GetItem and other calls that retrieve item data, this container will include the status (GetMyeBayBuying only) and dollar amount of the latest Best Offer on a fixed-price listing, and the number of Best Offers received for the fixed-price listing.
Component Diagram
XML Representation Summary
<ns:BestOfferDetails>
   
Content: 
</ns:BestOfferDetails>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="BestOfferDetails" type="ns:BestOfferDetailsType"/>

ns:BestOfferEnabled
Type:
xs:boolean, predefined, simple content
This field is deprecated. This information is returned in BestOfferDetails.
XML Representation Summary
<ns:BestOfferEnabled>
   
Content: 
{ xs:boolean }
</ns:BestOfferEnabled>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="BestOfferEnabled" type="xs:boolean"/>

ns:BiddingDetails
Type:
ns:BiddingDetailsType, complex content
Detailed information about a bid. For GetMyeBayBuying, returned as a self-closed element if no bids meet the request criteria.
Component Diagram
XML Representation Summary
<ns:BiddingDetails>
   
Content: 
</ns:BiddingDetails>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="BiddingDetails" type="ns:BiddingDetailsType"/>

ns:BidGroupItem
Type:
xs:boolean, predefined, simple content
This field is deprecated.
XML Representation Summary
<ns:BidGroupItem>
   
Content: 
{ xs:boolean }
</ns:BidGroupItem>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="BidGroupItem" type="xs:boolean"/>

ns:BusinessSellerDetails
Type:
Returns the seller's information (in a business card format) if the seller's SellerBusinessCodeType is set to Commercial. This is only applicable for sites where Business Seller options are supported.
Component Diagram
XML Representation Summary
<ns:BusinessSellerDetails>
   
Content: 
</ns:BusinessSellerDetails>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="BusinessSellerDetails" type="ns:BusinessSellerDetailsType"/>

ns:BuyerGuaranteePrice
Type:
ns:AmountType, simple content
For the Australia site, BuyerGuaranteePrice is the PayPal Buyer Protection coverage, offered for the item at the time of purchase. Details of coverage are in the following sections of the View Item page: the Buy Safely section and the Payment Details section.
Component Diagram
XML Representation Summary
<ns:BuyerGuaranteePrice
   
 = 
("AFA" | "ALL" | "DZD" | "ADP" | "AOA" | "ARS" | "AMD" | "AWG" | "AZM" | "BSD" | "BHD" | "BDT" | "BBD" | "BYR" | "BZD" | "BMD" | "BTN" | "INR" | "BOV" | "BOB" | "BAM" | "BWP" | "BRL" | "BND" | "BGL" | "BGN" | "BIF" | "KHR" | "CAD" | "CVE" | "KYD" | "XAF" | "CLF" | "CLP" | "CNY" | "COP" | "KMF" | "CDF" | "CRC" | "HRK" | "CUP" | "CYP" | "CZK" | "DKK" | "DJF" | "DOP" | "TPE" | "ECV" | "ECS" | "EGP" | "SVC" | "ERN" | "EEK" | "ETB" | "FKP" | "FJD" | "GMD" | "GEL" | "GHC" | "GIP" | "GTQ" | "GNF" | "GWP" | "GYD" | "HTG" | "HNL" | "HKD" | "HUF" | "ISK" | "IDR" | "IRR" | "IQD" | "ILS" | "JMD" | "JPY" | "JOD" | "KZT" | "KES" | "AUD" | "KPW" | "KRW" | "KWD" | "KGS" | "LAK" | "LVL" | "LBP" | "LSL" | "LRD" | "LYD" | "CHF" | "LTL" | "MOP" | "MKD" | "MGF" | "MWK" | "MYR" | "MVR" | "MTL" | "EUR" | "MRO" | "MUR" | "MXN" | "MXV" | "MDL" | "MNT" | "XCD" | "MZM" | "MMK" | "ZAR" | "NAD" | "NPR" | "ANG" | "XPF" | "NZD" | "NIO" | "NGN" | "NOK" | "OMR" | "PKR" | "PAB" | "PGK" | "PYG" | "PEN" | "PHP" | "PLN" | "USD" | "QAR" | "ROL" | "RUB" | "RUR" | "RWF" | "SHP" | "WST" | "STD" | "SAR" | "SCR" | "SLL" | "SGD" | "SKK" | "SIT" | "SBD" | "SOS" | "LKR" | "SDD" | "SRG" | "SZL" | "SEK" | "SYP" | "TWD" | "TJS" | "TZS" | "THB" | "XOF" | "TOP" | "TTD" | "TND" | "TRL" | "TMM" | "UGX" | "UAH" | "AED" | "GBP" | "USS" | "USN" | "UYU" | "UZS" | "VUV" | "VEB" | "VND" | "MAD" | "YER" | "YUM" | "ZMK" | "ZWD" | "ATS" | "CustomCode")
   
>
   
Content: 
{ xs:double }
</ns:BuyerGuaranteePrice>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="BuyerGuaranteePrice" type="ns:AmountType"/>

ns:BuyerProtection
Type:
Flag to indicate an item's eligibility for the PayPal Buyer Protection program. This field is only returned if true. If this field is not returned, the item is not eligible for PayPal Buyer Protection. For more information on items that are eligible for PayPal Buyer Protection, see the PayPal Buyer Protection help page.
XML Representation Summary
<ns:BuyerProtection>
   
Content: 
{ enumeration of xs:token }
</ns:BuyerProtection>
Simple Content
Enumeration:
"ItemIneligible"
 - 
This value indicates that the item is ineligible for buyer protection. In many cases, the item is ineligible for buyer protection due to the listing category.
"ItemEligible"
 - 
This value indicates that the item is eligible for buyer protection.
"ItemMarkedIneligible"
 - 
This value indicates that customer support has marked the item as ineligible per special criteria (e.g., seller's account closed).
"ItemMarkedEligible"
 - 
This value indicates that customer support has marked the item as eligible per special criteria.
"NoCoverage"
 - 
This value indicates that the item is ineligible for coverage under any buyer protection program.
"CustomCode"
 - 
Reserved for internal or future use.
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="BuyerProtection" type="ns:BuyerProtectionCodeType"/>

ns:BuyerRequirementDetails
Type:
When this container is present in an AddItem or AddFixedPriceItem call, all buyer requirements for the resulting listing are set by this container. Furthermore, individual buyer requirements cannot be modified or added when including this container in a ReviseItem call. The ReviseItem call needs to provide the entire set of buyer requirements to modify or add any of the requirements.

Unless otherwise specified, most buyer requirements are only returned if the caller is the seller. Any and all My eBay account-level Buyer Requirements are overridden by the contents of this container. This means that buyer requirements set in My eBay cannot be combined with buyer requirements included in this container.
Component Diagram
XML Representation Summary
<ns:BuyerRequirementDetails>
   
Content: 
</ns:BuyerRequirementDetails>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="BuyerRequirementDetails" type="ns:BuyerRequirementDetailsType"/>

ns:BuyerResponsibleForShipping
Type:
xs:boolean, predefined, simple content
Applicable for listings in vehicle categories on the US eBay Motors site and eBay Canada site. (No business effect if specified for other categories or sites, as the Web site will not display the information to buyers.)
  • If true, the buyer is responsible for vehicle pickup or shipping.
  • If false, specify vehicle shipping arrangements in the item description. (The description can also include vehicle shipping arrangements when this value is true.)
If the item has bids or ends within 12 hours, you cannot modify this flag. Do not specify ShippingDetails.ShippingServiceOptions for vehicle listings.

If true and the listing is on the US eBay Motors site, and you want the listing to be visible on the eBay Canada site, set Item.ShipToLocations to CA.

If true and the listing is on the eBay Canada site, and you want your listing to be visible on the US eBay Motors site, set Item.ShipToLocations to US.
XML Representation Summary
<ns:BuyerResponsibleForShipping>
   
Content: 
{ xs:boolean }
</ns:BuyerResponsibleForShipping>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="BuyerResponsibleForShipping" type="xs:boolean"/>

ns:BuyItNowPrice
Type:
ns:AmountType, simple content
This field is only applicable for auction listings. By specifying a 'Buy It Now' price, a seller is allowing prospective buyers the opportunity to purchase the item in the auction listing at this price immediately. When a buyer uses the 'Buy It Now' option to purchase the item, the auction listing will end immediately.

By including this field and specifying a 'Buy It Now' price, the seller is enabling the 'Buy It Now' feature on the auction listing. If the seller includes this field for any other listing type other than an auction, this field and its price will just be ignored.

The price in this field must be at least 30 percent higher than the starting bid price (which is specified in an Add call through the Item.StartPrice field). Once a bid is made on an auction listing, and the bid meets or exceeds the Item.ReservePrice value (if set), the 'Buy It Now' option becomes unavailable, and this field will no longer be applicable. If there is no Reserve Price, the first bid will nullify the 'Buy It Now' option.

Keep in mind that GetItem (and other 'Get' calls that retrieve the Item details) may still return the BuyItNowPrice field for an auction item even if the 'Buy It Now' option is no longer available. Instead, a user should look for the ListingDetails.BuyItNowAvailable boolean field in the GetItem response to determine if the 'Buy It Now' option is still available for the auction item.

Note: For the US site, new eBay sellers are subject to Seller Limits, which limit the quantity of items that may be listed and/or the total cumulative value of these listings. While subject to these selling limits, an eBay seller can use the GetMyeBaySelling call to retrieve both the remaining number of listings they can create and the remaining cumulative value of these listings. These values are shown in the Summary.QuantityLimitRemaining and Summary.AmountLimitRemaining fields in the GetMyeBaySelling response. If a call to add an item or revise an item would result in the exceeding of these limits, the add item or revise item call will fail. These fields will only be returned if the seller is subject to seller limits.
Component Diagram
XML Representation Summary
<ns:BuyItNowPrice
   
 = 
("AFA" | "ALL" | "DZD" | "ADP" | "AOA" | "ARS" | "AMD" | "AWG" | "AZM" | "BSD" | "BHD" | "BDT" | "BBD" | "BYR" | "BZD" | "BMD" | "BTN" | "INR" | "BOV" | "BOB" | "BAM" | "BWP" | "BRL" | "BND" | "BGL" | "BGN" | "BIF" | "KHR" | "CAD" | "CVE" | "KYD" | "XAF" | "CLF" | "CLP" | "CNY" | "COP" | "KMF" | "CDF" | "CRC" | "HRK" | "CUP" | "CYP" | "CZK" | "DKK" | "DJF" | "DOP" | "TPE" | "ECV" | "ECS" | "EGP" | "SVC" | "ERN" | "EEK" | "ETB" | "FKP" | "FJD" | "GMD" | "GEL" | "GHC" | "GIP" | "GTQ" | "GNF" | "GWP" | "GYD" | "HTG" | "HNL" | "HKD" | "HUF" | "ISK" | "IDR" | "IRR" | "IQD" | "ILS" | "JMD" | "JPY" | "JOD" | "KZT" | "KES" | "AUD" | "KPW" | "KRW" | "KWD" | "KGS" | "LAK" | "LVL" | "LBP" | "LSL" | "LRD" | "LYD" | "CHF" | "LTL" | "MOP" | "MKD" | "MGF" | "MWK" | "MYR" | "MVR" | "MTL" | "EUR" | "MRO" | "MUR" | "MXN" | "MXV" | "MDL" | "MNT" | "XCD" | "MZM" | "MMK" | "ZAR" | "NAD" | "NPR" | "ANG" | "XPF" | "NZD" | "NIO" | "NGN" | "NOK" | "OMR" | "PKR" | "PAB" | "PGK" | "PYG" | "PEN" | "PHP" | "PLN" | "USD" | "QAR" | "ROL" | "RUB" | "RUR" | "RWF" | "SHP" | "WST" | "STD" | "SAR" | "SCR" | "SLL" | "SGD" | "SKK" | "SIT" | "SBD" | "SOS" | "LKR" | "SDD" | "SRG" | "SZL" | "SEK" | "SYP" | "TWD" | "TJS" | "TZS" | "THB" | "XOF" | "TOP" | "TTD" | "TND" | "TRL" | "TMM" | "UGX" | "UAH" | "AED" | "GBP" | "USS" | "USN" | "UYU" | "UZS" | "VUV" | "VEB" | "VND" | "MAD" | "YER" | "YUM" | "ZMK" | "ZWD" | "ATS" | "CustomCode")
   
>
   
Content: 
{ xs:double }
</ns:BuyItNowPrice>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="BuyItNowPrice" type="ns:AmountType"/>

ns:CategoryMappingAllowed
Type:
xs:boolean, predefined, simple content
Note: This field's value now defaults to true if this field is omitted. Previously, the default value was false, so a user had to include this field and set it to true in order for eBay to map an outdated Primary or Secondary Category ID to the updated Category ID. This boolean field controls whether or not eBay automatically maps outdated Category ID(s) specified in a PrimaryCategory and/or SecondaryCategory container(s) to the updatd Category ID(s) no longer exists in the current category structure: If you pass a value of true in CategoryMappingAllowed or just omit the field, eBay will look up the current Category ID(s) that have replaced the specified Category ID(s). If you pass a value of false, eBay will not do any mapping, and the call may fail if specified Category ID(s) are no longer valid IDs for a eBay leaf category. The new Category ID(s) will be returned in the CategoryID and Category2ID fields (if secondary category is used) of the Add/Revise/Relist call response.

XML Representation Summary
<ns:CategoryMappingAllowed>
   
Content: 
{ xs:boolean }
</ns:CategoryMappingAllowed>
Simple Content
Default:
"false"
XML Source (w/o annotations (1); see within schema source)
<xs:element default="false" minOccurs="0" name="CategoryMappingAllowed" type="xs:boolean"/>

ns:CeilingPrice
Type:
ns:AmountType, simple content
This value sets the maximum price threshold for a seller's product price in a fixed-price listing. Regardless of the product price on Amazon or eBay Value Box, the seller's product price will not be raised higher than this dollar value.

This value is only applicable to sellers enabled to use the Dynamic Pricing API, and if a dynamic pricing rule is assigned to the listing's product. If this field is not specified through the Dynamic Pricing API, an eBay system-level threshold is used to avoid any undesirable results.
Component Diagram
XML Representation Summary
<ns:CeilingPrice
   
 = 
("AFA" | "ALL" | "DZD" | "ADP" | "AOA" | "ARS" | "AMD" | "AWG" | "AZM" | "BSD" | "BHD" | "BDT" | "BBD" | "BYR" | "BZD" | "BMD" | "BTN" | "INR" | "BOV" | "BOB" | "BAM" | "BWP" | "BRL" | "BND" | "BGL" | "BGN" | "BIF" | "KHR" | "CAD" | "CVE" | "KYD" | "XAF" | "CLF" | "CLP" | "CNY" | "COP" | "KMF" | "CDF" | "CRC" | "HRK" | "CUP" | "CYP" | "CZK" | "DKK" | "DJF" | "DOP" | "TPE" | "ECV" | "ECS" | "EGP" | "SVC" | "ERN" | "EEK" | "ETB" | "FKP" | "FJD" | "GMD" | "GEL" | "GHC" | "GIP" | "GTQ" | "GNF" | "GWP" | "GYD" | "HTG" | "HNL" | "HKD" | "HUF" | "ISK" | "IDR" | "IRR" | "IQD" | "ILS" | "JMD" | "JPY" | "JOD" | "KZT" | "KES" | "AUD" | "KPW" | "KRW" | "KWD" | "KGS" | "LAK" | "LVL" | "LBP" | "LSL" | "LRD" | "LYD" | "CHF" | "LTL" | "MOP" | "MKD" | "MGF" | "MWK" | "MYR" | "MVR" | "MTL" | "EUR" | "MRO" | "MUR" | "MXN" | "MXV" | "MDL" | "MNT" | "XCD" | "MZM" | "MMK" | "ZAR" | "NAD" | "NPR" | "ANG" | "XPF" | "NZD" | "NIO" | "NGN" | "NOK" | "OMR" | "PKR" | "PAB" | "PGK" | "PYG" | "PEN" | "PHP" | "PLN" | "USD" | "QAR" | "ROL" | "RUB" | "RUR" | "RWF" | "SHP" | "WST" | "STD" | "SAR" | "SCR" | "SLL" | "SGD" | "SKK" | "SIT" | "SBD" | "SOS" | "LKR" | "SDD" | "SRG" | "SZL" | "SEK" | "SYP" | "TWD" | "TJS" | "TZS" | "THB" | "XOF" | "TOP" | "TTD" | "TND" | "TRL" | "TMM" | "UGX" | "UAH" | "AED" | "GBP" | "USS" | "USN" | "UYU" | "UZS" | "VUV" | "VEB" | "VND" | "MAD" | "YER" | "YUM" | "ZMK" | "ZWD" | "ATS" | "CustomCode")
   
>
   
Content: 
{ xs:double }
</ns:CeilingPrice>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="CeilingPrice" type="ns:AmountType"/>

ns:Charity
Type:
ns:CharityType, complex content
This container identifies the nonprofit organization that will benefit with a percentage of the proceeds from each sale of an item through an auction or fixed-price listing. Charity names and IDs can be found by going to eBay for Charity page and doing a search, or by doing a search with the GetCharities call. The donation percentage can be set in 5 percent increments from 10 percent to 100 percent. For all charitable listings, PayPal must be an accepted payment method(see Item.PaymentMethods).

When it comes to revising an auction or fixed-price listing, you can add a benefitting charity (as long as there is at least 12 hours left before end of listing/close of auction), but you cannot remove or change a nonprofit company once one is already established in the original listing.

For Revise calls: The non-profit organization and donation percentage can now be modified in a Revise call as long as there are no active bids on an auction listing, or no pending Best Offers/Counter Offers on a listing.

This container will only be returned in Get calls for charitable listings. Charitable listings are only supported in the US and UK marketplaces.
Component Diagram
XML Representation Summary
<ns:Charity>
   
Content: 
</ns:Charity>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="Charity" type="ns:CharityType"/>

ns:ClassifiedAdPayPerLeadFee
Type:
ns:AmountType, simple content
The email and phone lead fee for a pay-per-lead item.
Component Diagram
XML Representation Summary
<ns:ClassifiedAdPayPerLeadFee
   
 = 
("AFA" | "ALL" | "DZD" | "ADP" | "AOA" | "ARS" | "AMD" | "AWG" | "AZM" | "BSD" | "BHD" | "BDT" | "BBD" | "BYR" | "BZD" | "BMD" | "BTN" | "INR" | "BOV" | "BOB" | "BAM" | "BWP" | "BRL" | "BND" | "BGL" | "BGN" | "BIF" | "KHR" | "CAD" | "CVE" | "KYD" | "XAF" | "CLF" | "CLP" | "CNY" | "COP" | "KMF" | "CDF" | "CRC" | "HRK" | "CUP" | "CYP" | "CZK" | "DKK" | "DJF" | "DOP" | "TPE" | "ECV" | "ECS" | "EGP" | "SVC" | "ERN" | "EEK" | "ETB" | "FKP" | "FJD" | "GMD" | "GEL" | "GHC" | "GIP" | "GTQ" | "GNF" | "GWP" | "GYD" | "HTG" | "HNL" | "HKD" | "HUF" | "ISK" | "IDR" | "IRR" | "IQD" | "ILS" | "JMD" | "JPY" | "JOD" | "KZT" | "KES" | "AUD" | "KPW" | "KRW" | "KWD" | "KGS" | "LAK" | "LVL" | "LBP" | "LSL" | "LRD" | "LYD" | "CHF" | "LTL" | "MOP" | "MKD" | "MGF" | "MWK" | "MYR" | "MVR" | "MTL" | "EUR" | "MRO" | "MUR" | "MXN" | "MXV" | "MDL" | "MNT" | "XCD" | "MZM" | "MMK" | "ZAR" | "NAD" | "NPR" | "ANG" | "XPF" | "NZD" | "NIO" | "NGN" | "NOK" | "OMR" | "PKR" | "PAB" | "PGK" | "PYG" | "PEN" | "PHP" | "PLN" | "USD" | "QAR" | "ROL" | "RUB" | "RUR" | "RWF" | "SHP" | "WST" | "STD" | "SAR" | "SCR" | "SLL" | "SGD" | "SKK" | "SIT" | "SBD" | "SOS" | "LKR" | "SDD" | "SRG" | "SZL" | "SEK" | "SYP" | "TWD" | "TJS" | "TZS" | "THB" | "XOF" | "TOP" | "TTD" | "TND" | "TRL" | "TMM" | "UGX" | "UAH" | "AED" | "GBP" | "USS" | "USN" | "UYU" | "UZS" | "VUV" | "VEB" | "VND" | "MAD" | "YER" | "YUM" | "ZMK" | "ZWD" | "ATS" | "CustomCode")
   
>
   
Content: 
{ xs:double }
</ns:ClassifiedAdPayPerLeadFee>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="ClassifiedAdPayPerLeadFee" type="ns:AmountType"/>

ns:ConditionDefinition
Type:
xs:string, predefined, simple content
This string value provides more details about the item's condition.
XML Representation Summary
<ns:ConditionDefinition>
   
Content: 
{ xs:string }
</ns:ConditionDefinition>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="ConditionDefinition" type="xs:string"/>

ns:ConditionDescription
Type:
xs:string, predefined, simple content
This string field is used by the seller to more clearly describe the condition of items that are not brand new.

The ConditionDescription field is available for all categories, including categories where the condition type is not applicable (e.g., Antiques). This field is applicable for all item conditions except 'New', 'Brand New', 'New with tags', and 'New in box'. If ConditionDescription is used with these conditions (Condition IDs 1000-1499), eBay will simply ignore this field if included, and eBay will return a warning message to the user.

This field should only be used to further clarify the condition of the used item. For example, "The right leg of the chair has a small scratch, and on the seat back there is a light blue stain about the shape and size of a coin." It should not be used for branding, promotions, shipping, returns, payment or other information unrelated to the condition of the item. Make sure that the condition type (Item.ConditionID), condition description, item description (Item.Description), and the listing's pictures do not contradict one another.

Note: The ConditionDescription field is optional For Add/Revise/Relist API calls. ConditionDescription is currently supported on the eBay US and US eBay Motors (0), UK (3), CA (2), CAFR (210), AU (15), AT (16), BEFR (23), BENL (123), FR (71), DE (77), IT (101), NL (146), ES (186), CH (193), IE (205) and PL (212) sites.
The ConditionDescription field is returned by GetItem (and other related calls that return the Item object) if a condition description is specified in the listing.
XML Representation Summary
<ns:ConditionDescription>
   
Content: 
{ xs:string }
</ns:ConditionDescription>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="ConditionDescription" type="xs:string"/>

ns:ConditionDisplayName
Type:
xs:string, predefined, simple content
The human-readable label for the item condition. Display names are localized for the site on which they're listed (not necessarily the site on which they're viewed).

Most categories use the same display name for the same condition ID. Some categories may override the display name based on buyer expectations for items in the category. For example, condition ID 1000 could be called "New" in one category and "New with tags" in another.

Behind the scenes, eBay's search engine uses the ID (not the display name) to determine whether items are new, used, or refurbished.

Only returned when the seller specified ConditionID in their listing.
XML Representation Summary
<ns:ConditionDisplayName>
   
Content: 
{ xs:string }
</ns:ConditionDisplayName>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="ConditionDisplayName" type="xs:string"/>

ns:ConditionID
Type:
xs:int, predefined, simple content
This is a numeric identifier for an item's condition. All numeric Condition ID values map to an item condition string value. For example, numeric identifer 1000 maps to New condition.

Most eBay listing categories require an item condition, but a few eBay categories do not (such as Digital Gift Cards or Antiques categories). To verify if the listing category requires an item condition, and if so, what are the supported item condition and ConditionID values, you can call GetCategoryFeatures. In this GetCategoryFeatures call, you'd pass in the listing CategoryID value and two FeatureID fields - one of these fields set to ConditionEnabled, and the other field set to ConditionValues.

In the GetCategoryFeatures response, look at the Category.ConditionEnabled to see if item condition is required for the category. Then look at the Category.ConditionValues container in the response for the full list of Condition IDs that you can pass in through the ConditionID field of an Add/Revise/Relist/Verify call. Note that the Condition.DisplayName value in the response is the actual condition value that will appear in the actual eBay listing.

If you pass in a ConditionID value that is not valid for the category, or if you don't pass in a ConditionID value at all for a category that requires it, the listing request fails.

If you are listing in two categories (using a secondary category), it is the primary listing category that determines which ConditionID values are supported.

For Revise/Relist calls: In most cases, you can change the ConditionID value (if applicable/warranted), with the exception being an auction listing that has one or more bids, or any listing that is scheduled to end in 12 hours or less.

For GetItem: The ConditionID value is always returned if set for the listing. GetItem also returns the item condition string value in the ConditionDisplayName field.

Note: In all eBay marketplaces, Condition ID 2000 now maps to an item condition of 'Certified Refurbished', and not 'Manufacturer Refurbished'. To list an item as 'Certified Refurbished', a seller must be pre-qualified by eBay for this feature. Any seller who is not eligible for this feature will be blocked if they try to create a new listing or revise an existing listing with this item condition. Any active listings on any eBay marketplace that had 'Manufacturer Refurbished' as the item condition should have been automatically updated by eBay to the 'Seller Refurbished' item condition (Condition ID 2500).

Any seller that is interested in eligibility requirements to list with 'Certified Refurbished' should see the Certified refurbished program page in Seller Center.
XML Representation Summary
<ns:ConditionID>
   
Content: 
{ xs:int }
</ns:ConditionID>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="ConditionID" type="xs:int"/>

ns:Country
Type:
ns:CountryCodeType, simple content
This two-digit enumeration value indicates the country of the seller's registration address. CountryCodeType defines the supported values. The GeteBayDetails call can also be used (include the DetailName field and set its value to CountryDetails) to see the full list of supported country codes.

In an Add/Revise/Relist/Verify call, this field is required.
XML Representation Summary
<ns:Country>
   
Content: 
{ enumeration of xs:token }
</ns:Country>
Simple Content
Enumeration:
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="Country" type="ns:CountryCodeType"/>

ns:CrossBorderTrade
Type:
xs:string, predefined, simple content
This field is used by sellers who want their listing to be returned in the search results for other eBay sites. This feature is currently only supported by the US, UK, eBay Canada, and eBay Ireland sites. See Getting exposure on international sites for full requirements on using this feature. There is a small listing fee for each country specified as a Cross Border Trade country.

US listings that offer shipping to Canada, North America, or worldwide are automatically returned on eBay.ca at no extra charge, so US listings that offer shipping to these locations do not need to specify Canada as a Cross Border Trade country.
XML Representation Summary
<ns:CrossBorderTrade>
   
Content: 
{ xs:string }
</ns:CrossBorderTrade>
XML Source (w/o annotations (1); see within schema source)
<xs:element maxOccurs="unbounded" minOccurs="0" name="CrossBorderTrade" type="xs:string"/>

ns:CrossPromotion
Type:
ns:CrossPromotionsType, complex content
This field is deprecated, and should not longer be used.
Component Diagram
XML Representation Summary
<ns:CrossPromotion>
   
Content: 
</ns:CrossPromotion>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="CrossPromotion" type="ns:CrossPromotionsType"/>

ns:Currency
Type:
ns:CurrencyCodeType, simple content
In an Add/Revise/Relist/Verify call, this required three-digit enumeration value defines the currency associated with the listing site. The item price and all costs passed in the call request will be using this currency. Similarly, the listing fees and other cost-related data will be using this currency. Since the Trading API can only be used for a select number of eBay sites, only a subset of values are supporting when adding/revising/relisting an item. These supported values are discussed in the top section of CurrencyCodeType.

In 'Get' calls, it is possible that any of the values in CurrencyCodeType may appear, as some cost-related fields will show the buyer's currency type.
XML Representation Summary
<ns:Currency>
   
Content: 
{ enumeration of xs:token }
</ns:Currency>
Simple Content
Enumeration:
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="Currency" type="ns:CurrencyCodeType"/>

ns:Description
Type:
xs:string, predefined, simple content
The seller's description of the item. In listing requests, you can submit your description using CDATA if you want to use HTML or XML-reserved characters in the description. However, a seller can not use any active content in their listing description. Active content includes animation or video via JavaScript, Flash, plug-ins, or form actions. All active content will be blocked/removed from a listing. Removing/blocking active content will lead to faster load times of listings, make listings more mobile-friendly, improve SEO performance, and lead to a more secure eBay Marketplace.

Note: To ensure that their listing description is optimized when viewed on mobile devices, sellers should strongly consider using eBay's View Item description summary feature when listing their item. Using HTML div and span tag attributes, this feature allows sellers to customize and fully control the listing description that is displayed for prospective buyers when viewing the item on a mobile device. The listing description on mobile devices is limited to 800 characters, and whenever the listing description exceeds this limit, eBay uses a special algorithm to derive the best possible description within the 800-character limit. However, due to some description content being removed, it is definitely not ideal for the seller, and could possibly lead to a bad buyer experience and a Significantly not as described (SNAD) case, since the buyer may not get complete details on the item. See the eBay help page for more details on using the HTML div and span tags, and for more tips on creating listings that are mobile-friendly, see this Best practices document.
In the listing description, sellers are only allowed to provide links to product videos, freight shipping services, or other legally required information, and when providing these links in the listing description, the secure 'https' protocol must be used instead of 'http'. In addition, any valid links to sites outside of eBay should use the target="_blank" attribute in the a href tag so a new browser window will be loaded when the link is clicked instead of buyers being redirected off of eBay. For more information on using links in the listing description, see eBay's Links policy. For more information about the stronger security standards that eBay is using, see the Use secure HTTPS for enhanced browser security topic in the 2018 Fall Seller Update. The getListingViolations method of the Compliance API can be used to see if any of the seller's active listings are not 'HTTPS' compliant.

If you embed pictures in the description (by using IMG tags) instead of using PictureURL, but you want a camera icon to appear in search and listing pages, specify the following null-image URL in the PictureURL field: https://pics.ebay.com/aw/pics/dot_clear.gif. See Working with Pictures in an Item Listing in the eBay Features Guide.

This field is conditionally required for all listings. The exception is when the seller specifies a product identifier, such as a GTIN or ePID, through the ProductListingDetails container and a product match is found in the eBay product catalog. If a matching product is found in the eBay product catalog, the item description will be created automatically (as long as the ProductListingDetails.IncludeeBayProductDetails value is true).
XML Representation Summary
<ns:Description>
   
Content: 
{ xs:string }
</ns:Description>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="Description" type="xs:string"/>

ns:DescriptionReviseMode
Type:
This field is conditionally required if the listing is being revised through a Revise call, and the Item.Description field is one of the fields being changed. The enumeration value passed in this field specifies whether the text provided in the Item.Description field will prepend, append, or replace the existing text in the current Item.Description field.
XML Representation Summary
<ns:DescriptionReviseMode>
   
Content: 
{ enumeration of xs:token }
</ns:DescriptionReviseMode>
Simple Content
Enumeration:
"Replace"
 - 
Use this value in the Item.DescriptionReviseMode field if you want to completely replace (overwrite) the item description of the active listing.
"Prepend"
 - 
Use this value in the Item.DescriptionReviseMode field if you want to prepend text to the item description of the active listing.
"Append"
 - 
Use this value in the Item.DescriptionReviseMode field if you want to append text to the item description of the active listing.
"CustomCode"
 - 
This value is reserved for internal or future use.
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="DescriptionReviseMode" type="ns:DescriptionReviseModeCodeType"/>

ns:DigitalGoodInfo
Type:
ns:DigitalGoodInfoType, complex content
This container is used in Add/Revise/Relist/Verify listing calls to designate the listing as a digital gift card listing. It is also returned in GetItem to indicate that the listing contains a digital gift card.
Component Diagram
XML Representation Summary
<ns:DigitalGoodInfo>
   
Content: 
</ns:DigitalGoodInfo>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="DigitalGoodInfo" type="ns:DigitalGoodInfoType"/>

ns:DisableBuyerRequirements
Type:
xs:boolean, predefined, simple content
If true, all buyer requirements (from Item.BuyerRequirementDetails or Buyer requirements preferences in My eBay) are ignored.

If false (or omitted): Item.BuyerRequirementDetails or Buyer requirements preferences are used, with Item.BuyerRequirementDetails having the higher precedence.
XML Representation Summary
<ns:DisableBuyerRequirements>
   
Content: 
{ xs:boolean }
</ns:DisableBuyerRequirements>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="DisableBuyerRequirements" type="xs:boolean"/>

ns:DiscountPriceInfo
Type:
ns:DiscountPriceInfoType, complex content
This container provides information for an item that has a Strikethrough Price (STP) or a Minimum Advertised Price (MAP) discount pricing treatment. STP and MAP apply only to fixed-price listings. STP is available on the US, eBay Motors, UK, Germany, Canada (English and French), France, Italy, and Spain sites, while MAP is available only on the US site.

Discount pricing is available to qualified sellers (and their associated developers) who participate in the Discount Pricing Program. Once qualified, sellers receive a 'special account flag' (SAF) that allows them to apply Discount Pricing to both single-variation and multi-variation items. STP is intended for eBay partners and their sellers only.

As a seller listing Discount Price items, you are required to maintain records of your discount pricing in the event you are called upon to substantiate your item pricing.

For AddFixedPriceItem, RelistFixedPriceItem, ReviseFixedPriceItem, and VerifyAddFixedPriceItem: If you are listing variations (MSKU items), use Variation.DiscountPriceInfo for each variation.
Component Diagram
XML Representation Summary
<ns:DiscountPriceInfo>
   
Content: 
</ns:DiscountPriceInfo>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="DiscountPriceInfo" type="ns:DiscountPriceInfoType"/>

ns:DispatchTimeMax
Type:
xs:int, predefined, simple content
Specifies the maximum number of business days the seller commits to for preparing an item to be shipped after receiving a cleared payment. This time does not include the shipping time (the carrier's transit time).

Note: If the seller opts into the eBay Guaranteed Delivery feature and wants to make a listing eligible for eBay Guaranteed Delivery, the DispatchTimeMax value must be set to 0 or 1 (days) and the cumulative value of DispatchTimeMax plus the transit time of the shipping service (returned in ShippingServiceDetails.ShippingTimeMax field of GeteBayDetails) must be 4 business days or less to be eligible for this feature. See the eBay Guaranteed Delivery page in Seller Center for more information on this program. The eBay Guaranteed Delivery feature is only available on the US and Australia marketplaces.
For Add/Revise/Relist calls: Required for listings in certain categories when certain shipping services (with delivery) are offered. See HandlingTimeEnabled in GetCategoryFeatures.

The seller sets this to a positive integer value corresponding to the number of 'handling' days. For a list of allowed values on each eBay site, use DispatchTimeMaxDetails in GeteBayDetails. Supported handling times for most sites in most categories range from 0 (same-day handling) to 3 business days, but this can vary by site. Some categories on some sites support longer handling times, and this generally comes into play with extremely large items where freight shipping may be required.

This field is required whenever flat-rate or calculated shipping is used, but does not apply when there is no shipping involved, which is the case for digital gift card listings, or any orders where local pickup is available and this option is selected by the buyer.

For ReviseItem only: If the listing has bids or sales and it ends within 12 hours, you can't change this value. If the listing is a GTC listing that has sales or ends within 12 hours (one or the other, but not both), you can add or change this value. If the listing has no bids or sales and more than 12 hours remain before the listing ends, you can add or change the dispatch (handling) time.

For GetItem: GetItem returns DispatchTimeMax only when shipping service options are specified for the item and the seller specified a dispatch time.
XML Representation Summary
<ns:DispatchTimeMax>
   
Content: 
{ xs:int }
</ns:DispatchTimeMax>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="DispatchTimeMax" type="xs:int"/>

ns:Distance
Type:
ns:DistanceType, complex content
This field is deprecated, and should no longer be used.
Component Diagram
XML Representation Summary
<ns:Distance>
   
Content: 
</ns:Distance>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="Distance" type="ns:DistanceType"/>

ns:eBayNotes
Type:
xs:string, predefined, simple content
Returns a note from eBay displayed below items in the user's My eBay account.
XML Representation Summary
<ns:eBayNotes>
   
Content: 
{ xs:string }
</ns:eBayNotes>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="eBayNotes" type="xs:string"/>

ns:eBayPlus
Type:
xs:boolean, predefined, simple content
eBay Plus is a premium account option for buyers, which provides benefits such as fast and free domestic shipping, and free returns on selected items. To offer this feature to buyers, sellers must opt in to eBay Plus, and their selling status must be 'Above Standard' or above.

Note: Currently, eBay Plus is only available to buyers on the Germany and Australia marketplaces, and this field should only be used by sellers selling eligible items in Germany.

In Australia, the seller has no control/responsibility over setting the eBay Plus feature for a listing. Instead, eBay will evaluate/determine whether a listing is eligible for eBay Plus. Due to this fact, an Australian seller will also get the 21919431: This listing isn't eligible for eBay Plus. warning message in an add/revise/relist call, even though eBay may ultimately set the eBay Plus feature on the listing if the item is eligible.

In an add/revise/relist call, a seller on the Germany site must include this field and set its value to true. If the seller is not eligible for/opted in to eBay Plus and/or the listing category or item does not qualify for eBay Plus, a warning message will be returned to the seller in the response indicating this. In addition to the seller, listing category, and item being eligible for eBay Plus, the seller must also set/commit to the following for the listing:
  • Listing format must be fixed-price.
  • Same-day or one-day handling (DispatchTimeMax set to 0 or 1).
  • A free, next-day shipping option offered.
  • A return policy that offers a 30-day (or longer) return period.
If this field is returned as true in a 'Get' call, it indicates that the item is eligible for eBay Plus treatment, but eBay Plus will only come into play if the buyer is subscribed to eBay Plus.
XML Representation Summary
<ns:eBayPlus>
   
Content: 
{ xs:boolean }
</ns:eBayPlus>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="eBayPlus" type="xs:boolean"/>

ns:eBayPlusEligible
Type:
xs:boolean, predefined, simple content
If this field is returned as true, this item is eligible to be listed under the eBay Plus program. eBay Plus is a premium account option for buyers, which provides benefits such as fast and free domestic shipping and free returns on selected items. eBay sellers must opt in to eBay Plus to be able offer the program on qualifying listings. Among other requirements, sellers must commit to next-day delivery of those items.

Note: Currently, eBay Plus is available only to buyers in Germany and Australia marketplaces.
XML Representation Summary
<ns:eBayPlusEligible>
   
Content: 
{ xs:boolean }
</ns:eBayPlusEligible>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="eBayPlusEligible" type="xs:boolean"/>

ns:EligibleForPickupDropOff
Type:
xs:boolean, predefined, simple content
For 'Click and Collect' eligible sellers, this field was once used to set 'Click and Collect' eligibility at the listing level. However, now the seller can only opt in to 'Click and Collect' at the account level, and then each of their listings will be automatically evaluated for 'Click and Collect' eligibility.

Note: Until this field is fully deprecated in the Trading WSDL (and in Add/Revise/Relist/Verify calls), it can still be used, but it will have no functional affect. However, if set in an Add/Revise/Relist/Verify call, it will get returned in GetItem, but it won't be a true indicator if the item is available for the 'Click and Collect' logistics type. Instead, the Item.AvailableForPickupDropOff field should be referenced to see if the item is available for 'Click and Collect'.
XML Representation Summary
<ns:EligibleForPickupDropOff>
   
Content: 
{ xs:boolean }
</ns:EligibleForPickupDropOff>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="EligibleForPickupDropOff" type="xs:boolean"/>

ns:eMailDeliveryAvailable
Type:
xs:boolean, predefined, simple content
The boolean value that is returned in this field will indicate whether or not a digital gift card can be delivered by email to the buyer or recipient of the gift card. This field is only applicable to digital gift card listings.
XML Representation Summary
<ns:eMailDeliveryAvailable>
   
Content: 
{ xs:boolean }
</ns:eMailDeliveryAvailable>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="eMailDeliveryAvailable" type="xs:boolean"/>

ns:ExtendedSellerContactDetails
Type:
Extended contact information for sellers using the Classified Ad format. Specifies the days and hours when the seller can be contacted. To remove seller contact information when revising or relisting an item, use DeletedField.
Component Diagram
XML Representation Summary
<ns:ExtendedSellerContactDetails>
   
Content: 
</ns:ExtendedSellerContactDetails>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="ExtendedSellerContactDetails" type="ns:ExtendedContactDetailsType"/>

ns:FloorPrice
Type:
ns:AmountType, simple content
This value sets the minimum price threshold for a seller's product price in a fixed-price listing. Regardless of the product price on eBay Value Box or Amazon listings, the seller's product price will not be reduced lower than this dollar value.

This value is only applicable to sellers enabled to use the Dynamic Pricing API, and if a dynamic pricing rule is assigned to the listing's product.
Component Diagram
XML Representation Summary
<ns:FloorPrice
   
 = 
("AFA" | "ALL" | "DZD" | "ADP" | "AOA" | "ARS" | "AMD" | "AWG" | "AZM" | "BSD" | "BHD" | "BDT" | "BBD" | "BYR" | "BZD" | "BMD" | "BTN" | "INR" | "BOV" | "BOB" | "BAM" | "BWP" | "BRL" | "BND" | "BGL" | "BGN" | "BIF" | "KHR" | "CAD" | "CVE" | "KYD" | "XAF" | "CLF" | "CLP" | "CNY" | "COP" | "KMF" | "CDF" | "CRC" | "HRK" | "CUP" | "CYP" | "CZK" | "DKK" | "DJF" | "DOP" | "TPE" | "ECV" | "ECS" | "EGP" | "SVC" | "ERN" | "EEK" | "ETB" | "FKP" | "FJD" | "GMD" | "GEL" | "GHC" | "GIP" | "GTQ" | "GNF" | "GWP" | "GYD" | "HTG" | "HNL" | "HKD" | "HUF" | "ISK" | "IDR" | "IRR" | "IQD" | "ILS" | "JMD" | "JPY" | "JOD" | "KZT" | "KES" | "AUD" | "KPW" | "KRW" | "KWD" | "KGS" | "LAK" | "LVL" | "LBP" | "LSL" | "LRD" | "LYD" | "CHF" | "LTL" | "MOP" | "MKD" | "MGF" | "MWK" | "MYR" | "MVR" | "MTL" | "EUR" | "MRO" | "MUR" | "MXN" | "MXV" | "MDL" | "MNT" | "XCD" | "MZM" | "MMK" | "ZAR" | "NAD" | "NPR" | "ANG" | "XPF" | "NZD" | "NIO" | "NGN" | "NOK" | "OMR" | "PKR" | "PAB" | "PGK" | "PYG" | "PEN" | "PHP" | "PLN" | "USD" | "QAR" | "ROL" | "RUB" | "RUR" | "RWF" | "SHP" | "WST" | "STD" | "SAR" | "SCR" | "SLL" | "SGD" | "SKK" | "SIT" | "SBD" | "SOS" | "LKR" | "SDD" | "SRG" | "SZL" | "SEK" | "SYP" | "TWD" | "TJS" | "TZS" | "THB" | "XOF" | "TOP" | "TTD" | "TND" | "TRL" | "TMM" | "UGX" | "UAH" | "AED" | "GBP" | "USS" | "USN" | "UYU" | "UZS" | "VUV" | "VEB" | "VND" | "MAD" | "YER" | "YUM" | "ZMK" | "ZWD" | "ATS" | "CustomCode")
   
>
   
Content: 
{ xs:double }
</ns:FloorPrice>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="FloorPrice" type="ns:AmountType"/>

ns:FreeAddedCategory
Type:
ns:CategoryType, complex content
The unique identifier for a secondary category that eBay has added as a free promotion. You cannot add this yourself. This container is only returned if the item was listed in a single category and eBay added a free secondary category.
Component Diagram
XML Representation Summary
<ns:FreeAddedCategory>
   
Content: 
</ns:FreeAddedCategory>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="FreeAddedCategory" type="ns:CategoryType"/>

ns:GetItFast
Type:
xs:boolean, predefined, simple content
This field is deprecated.
XML Representation Summary
<ns:GetItFast>
   
Content: 
{ xs:boolean }
</ns:GetItFast>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="GetItFast" type="xs:boolean"/>

ns:GroupCategoryID
Type:
xs:string, predefined, simple content
This field is deprecated.
XML Representation Summary
<ns:GroupCategoryID>
   
Content: 
{ xs:string }
</ns:GroupCategoryID>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="GroupCategoryID" type="xs:string"/>

ns:HideFromSearch
Type:
xs:boolean, predefined, simple content
This boolean field is returned as true if the listing has been hidden from all searches occurring on eBay. If a listing is hidden from eBay searches, the reason can be found in the ReasonHideFromSearch field.
XML Representation Summary
<ns:HideFromSearch>
   
Content: 
{ xs:boolean }
</ns:HideFromSearch>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="HideFromSearch" type="xs:boolean"/>

ns:HitCount
Type:
xs:long, predefined, simple content
This value indicates the number of page views for the listing. This number is calculated by eBay and is returned in 'Get' calls if the HitCounter value is set to BasicStyle, RetroStyle, or HiddenStyle.
XML Representation Summary
<ns:HitCount>
   
Content: 
{ xs:long }
</ns:HitCount>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="HitCount" type="xs:long"/>

ns:HitCounter
Type:
ns:HitCounterCodeType, simple content
Indicates whether an optional hit counter is displayed on the item's listing page and, if so, what type. See HitCounterCodeType for specific values.
<br/><br/><b>Restriction:</b> <code>HiddenStyle</code> is not enabled on the Germany, Austria, Switzerland, or Poland sites.
XML Representation Summary
<ns:HitCounter>
   
Content: 
{ enumeration of xs:token }
</ns:HitCounter>
Simple Content
Enumeration:
"NoHitCounter"
 - 
No hit counter. The number of page views will not be available.
"HonestyStyle"
 - 
A basic style hit counter (US only). Non-US sites will return errors if they use HonestyStyle as input, and should use BasicStyle instead.
"GreenLED"
 - 
A green LED, computer-style hit counter (US only). Non-US sites will return errors if they use GreenLED as input, and should use RetroStyle instead.
"Hidden"
 - 
A hidden hit counter (US only). The number of page views will only be available to the item's seller. For faster "View Item" page loads, use HiddenStyle.
"BasicStyle"
 - 
A basic style hit counter.
"RetroStyle"
 - 
A retro, computer-style hit counter.
"HiddenStyle"
 - 
A hidden hit counter. The number of page views will only be available to the item's seller.
"CustomCode"
 - 
Reserved for internal or future use
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="HitCounter" type="ns:HitCounterCodeType"/>

ns:IgnoreQuantity
Type:
xs:boolean, predefined, simple content
This boolean field is returned as true if the actual quantity of a multiple-quantity, fixed-price listing (indicated in the Item.Quantity field) can not be accurately determined by eBay.
XML Representation Summary
<ns:IgnoreQuantity>
   
Content: 
{ xs:boolean }
</ns:IgnoreQuantity>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="IgnoreQuantity" type="xs:boolean"/>

ns:IntegratedMerchantCreditCardEnabled
Type:
xs:boolean, predefined, simple content
Indicates whether the item can be paid for through a payment gateway (Payflow) account. If IntegratedMerchantCreditCardEnabled is true, then integrated merchant credit card (IMCC) is enabled for credit cards because the seller has a payment gateway account. Therefore, if IntegratedMerchantCreditCardEnabled is true, an AmEx, Discover, or VisaMC is returned for an item, then on checkout, an online credit-card payment is processed through a payment gateway account. A payment gateway account is used by sellers to accept online credit cards (Visa, MasterCard, American Express, and Discover).

Note: As of May 1, 2019, eBay no longer supports electronic payments through Integrated Merchant Credit Card accounts. To accept online credit card payments from buyers, a seller must specify PayPal as an accepted payment method, or opt in to eBay managed payments program (if the program is available to that seller).

Note: For the GetItemTransactions, GetOrders, and GetOrderTransactions calls, this field is only returned to the seller of the order; this field is not returned for the buyer or third party.
XML Representation Summary
<ns:IntegratedMerchantCreditCardEnabled>
   
Content: 
{ xs:boolean }
</ns:IntegratedMerchantCreditCardEnabled>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="IntegratedMerchantCreditCardEnabled" type="xs:boolean"/>

ns:InventoryTrackingMethod
Type:
Indicates whether you prefer to track your eBay listings by eBay Item ID or by your own SKU.

If a seller will be converting an existing eBay listing into the new Inventory model using the bulkMigrateListings call of the Inventory API, the InventoryTrackingMethod value must be set to ItemID (default value), but the item must also have a SKU value (Item.SKU or Variation.SKU) associated with it. For GetItem and related calls: Only returned when the value is SKU; not returned when the value is ItemID.
XML Representation Summary
<ns:InventoryTrackingMethod>
   
Content: 
{ enumeration of xs:token }
</ns:InventoryTrackingMethod>
Simple Content
Enumeration:
"ItemID"
 - 
Indicates the seller prefers to track the listing by its eBay item ID. This is the default for all listings.
"SKU"
 - 
Indicates the seller prefers to track the listing by their own SKU.

When you track by SKU, it means you can pass in your SKU instead of the eBay item ID in other calls that support SKU as an input field. If you choose SKU as your tracking preference for a listing, the value in Item.SKU must be unique across your active listings. You cannot create new listings with the same Item.SKU value while the listing is active (that is, until the existing listing with that SKU has ended).

However, you can use ReviseInventoryStatus to update the quantity and/or price for the existing SKU as needed. When revising a listing where the InventoryTrackingMethod was set to SKU, you must pass in both the InventoryTrackingMethod tag (with the value set to SKU) and the SKU tag with the SKU value from your original listing.
"CustomCode"
 - 
Reserved for internal or future use.
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="InventoryTrackingMethod" type="ns:InventoryTrackingMethodCodeType"/>

ns:IsIntermediatedShippingEligible
Type:
xs:boolean, predefined, simple content
This boolean field is returned as true if the item is eligible is to be shipped internationally via eBay's Global Shipping Program. With the Global Shipping Program, the buyer pays a single shipping fee for the order, which includes the domestic shipping leg, the international shipping leg, and handling charges, and import charges.

eBay uses a shipping partner that allows the seller to ship the package to a domestic location and then the shipping partner takes care of the rest, including the international shipping leg.
XML Representation Summary
<ns:IsIntermediatedShippingEligible>
   
Content: 
{ xs:boolean }
</ns:IsIntermediatedShippingEligible>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="IsIntermediatedShippingEligible" type="xs:boolean"/>

ns:IsSecureDescription
Type:
xs:boolean, predefined, simple content
This boolean field indicates whether or not the listing description is HTTPS secure/compliant. To be HTTPS secure/compliant, the Item.Description field may not contain any links to site pages that use the HTTP (and not HTTPS) protocol. This field will be returned with each listing that is found unless one or more OutputSelector fields are used and Item.IsSecureDescription is not one of the values passed in to one of these fields.

If this field is returned as true, the listing is HTTPs secure/compliant, and the whole listing description will appear on the View Item page for the listing. If this field is returned as false, the listing is not HTTPs secure/compliant, and only a partial/brief listing description will appear on the View Item page for the listing, with a link to the full listing description that will load in another tab.

If the listing description is not HTTPS compliant, the fix is to call ReviseItem or ReviseFixedPriceItem and update the Item.Description field, removing all links to HTTP pages.

For more information about why eBay made this change, please see the Policy Updates page of the Fall 2017 Seller Updates page.
XML Representation Summary
<ns:IsSecureDescription>
   
Content: 
{ xs:boolean }
</ns:IsSecureDescription>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="IsSecureDescription" type="xs:boolean"/>

ns:ItemCompatibilityCount
Type:
xs:int, predefined, simple content
Indicates the number of compatible applications specified for the given item. Applies to items listed with fitment by application only (either manually or with a catalog product that supports compatibility).

Not returned if the item has no specified compatible applications. Not returned if IncludeItemCompatibilityList is specified in the request.

To retrieve the list of compatibility information, set IncludeItemCompatibilityList to true in the request.

Parts Compatibility is supported in limited Parts & Accessories categories for the eBay Motors (US) site (site ID 100) only.
XML Representation Summary
<ns:ItemCompatibilityCount>
   
Content: 
{ xs:int }
</ns:ItemCompatibilityCount>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="ItemCompatibilityCount" type="xs:int"/>

ns:ItemCompatibilityList
Type:
A list of parts compatibility information specified as name and value pairs. Describes an assembly with which a part is compatible (i.e., compatibility by application). For example, to specify a part's compatibility with a vehicle, the name (search name) would map to standard vehicle characteristics (e.g., Year, Make, Model, Trim, and Engine). The values would describe the specific vehicle, such as a 2006 Honda Accord. Use the Product Metadata API to retrieve valid search names and corresponding values.

For the AddItem family of calls: Use this for specifying parts compatibility by application manually. This can only be used in categories that support parts compatibility by application. Use GetCategoryFeatures with the CompatibilityEnabled feature ID to determine which categories support parts compatibility by application.

For ReviseFixedPriceItem and ReviseItem: When you revise a listing, if the listing has bids and/or ends within 12 hours, item compatibilities cannot be deleted. You may add item compatibilities at any time.

For GetItem: ItemCompatibilityList is only returned if the seller included item compatibility in the listing and IncludeItemCompatibilityList is set to true in the GetItem request.

Component Diagram
XML Representation Summary
<ns:ItemCompatibilityList>
   
Content: 
</ns:ItemCompatibilityList>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="ItemCompatibilityList" type="ns:ItemCompatibilityListType"/>

ns:ItemID
Type:
ns:ItemIDType, simple content
The unique identifier of the eBay listing. This identifier is generated by eBay and returned in the response of an Add call if an item is successfully listed. Once an item is successfully created, the ItemID cannot be modified.

Note: Although we represent item IDs as strings in the schema, we recommend you store them as 64-bit signed integers. If you choose to store item IDs as strings, allocate at least 19 characters (assuming decimal digits are used) to hold them. Your code should be prepared to handle IDs of up to 19 digits.
XML Representation Summary
<ns:ItemID>
   
Content: 
{ xs:string }
</ns:ItemID>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="ItemID" type="ns:ItemIDType"/>

ns:ItemPolicyViolation
Type:
Specifies the details of policy violations if the item was administratively canceled.
Component Diagram
XML Representation Summary
<ns:ItemPolicyViolation>
   
Content: 
</ns:ItemPolicyViolation>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="ItemPolicyViolation" type="ns:ItemPolicyViolationType"/>

ns:ItemSpecifics
Type:
ns:NameValueListArrayType, complex content
This container is a list of Item Specific Name/Value pairs used by the seller to provide desciptive details of an item in a structured manner.

If creating, revising, or relisting an item with an Add, Revise, or Relist call, it is recommended that you use the GetCategorySpecifics call to retrieve mandatory and recommended Item Specifics for a listing category.

For ReviseItem only: When you revise a listing, if an auction listing has one or more bids and ends within 12 hours, you cannot change or add Item Ppecifics. If the auction listing has bids but ends in more than 12 hours, you cannot change existing Item Specifics, but you can add Item Specifics that were not previously included.

If your listing is in a eBay product catalog-enabled category, certain Name/Value pairs will be accepted as product identifying information. The Name can be Brand, MPN, or a Global Trade Item Number (GTIN). GTINs are a set of globally recognized identifiers, including EAN, ISBN, and UPC. However, the Values provided for these Names must comply with eBay's constraints or they will not be recognized as product identifiers. The Value for Brand must be an actual brand name (except that if the item is not branded, Value can be Unbranded.) The Value for Brand or MPN cannot contain only special characters (e.g. %$*#@). All GTINs must comply with international formatting standards. For more details, see Listing with Item Specifics.

If the ProductListingDetails container in an Add/Revise/Relist call is successfully used to find and use an eBay catalog product to create/revise listing, the seller should not remove or change the value of any Item Specific name or value that is defined as part of the eBay catalog product definition.

Note: If a listing is associated with an eBay catalog product, the seller does not need to pass in any Item Specifics that are already defined in the eBay catalog product. Sellers can make a GetCategorySpecifics call to see if the listing category supports any 'instance aspects', which can be thought of as Item Specifics that are unique to the specific item that is being listed. Instance aspects are identified in the GetCategorySpecifics response by looking for a value of Instance in one or more NameRecommendation.ValidationRules.aspectUsage fields. Many categories support the following instance aspects: Custom Bundle, Bundle Description, Modified Item, Modification Description, and California Prop 65 Warning. These instance aspects allow the seller to provide more information about product bundles or modified products in a structured way. Depending on the category, there are other instance aspects as well. Note: To specify an item's condition, use the ConditionID field instead of a condition Item Specific. Use GetCategoryFeatures to see which categories support ConditionID and to get a list of valid condition IDs. (If you specify ConditionID and you also specify Condition as a Item Specific, eBay drops the condition Item Specific.) For GetItem: This list is returned only when you specify IncludeItemSpecifics in the request (and the seller included Item Specifics in their listing).

To delete all Item Specifics when you revise or relist, specify Item.ItemSpecifics in DeletedField, and don't pass ItemSpecifics in the request.
Component Diagram
XML Representation Summary
<ns:ItemSpecifics>
   
Content: 
</ns:ItemSpecifics>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="ItemSpecifics" type="ns:NameValueListArrayType"/>

ns:LeadCount
Type:
xs:int, predefined, simple content
Specifies the number of leads (emails) buyers have posted about the item. You must be the seller of the item to retrieve the lead count.
XML Representation Summary
<ns:LeadCount>
   
Content: 
{ xs:int }
</ns:LeadCount>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="LeadCount" type="xs:int"/>

ns:LimitedWarrantyEligible
Type:
xs:boolean, predefined, simple content
This field is deprecated.
XML Representation Summary
<ns:LimitedWarrantyEligible>
   
Content: 
{ xs:boolean }
</ns:LimitedWarrantyEligible>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="LimitedWarrantyEligible" type="xs:boolean"/>

ns:ListingDetails
Type:
ns:ListingDetailsType, complex content
Various details about a listing, some of which are calculated or derived after the item is listed. These include the start and end time, converted (localized) prices, and certain flags that indicate whether the seller specified fields whose values are not visible to the requesting user. For GetMyeBayBuying, returned as a self-closed element if no listings meet the request criteria.

In an Add/Revise/Relist call, this container is used to set the Best Offer Auto-Accept and Best Offer Auto-Decline threshold values.
Component Diagram
XML Representation Summary
<ns:ListingDetails>
   
Content: 
</ns:ListingDetails>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="ListingDetails" type="ns:ListingDetailsType"/>

ns:ListingDuration
Type:
xs:token, predefined, simple content
Describes the number of days the seller wants the listing to be active (available for bidding/buying). The duration specifies the seller's initial intent at listing time.

The end time for a listing is calculated by adding the duration to the item's start time. If the listing ends early, the value of the listing duration does not change. When a listing's duration is changed, any related fees (e.g., 10-day fee) may be debited or credited (as applicable).

The valid choice of values depends on the listing format (see Item.ListingType). For a list of valid values, call GetCategoryFeatures with DetailLevel set to ReturnAll and look for ListingDurations information.

When you revise a listing, the duration cannot be reduced if it will result in ending the listing within 24 hours of the current date-time. You are only allowed to increase the duration of the listing if fewer than 2 hours have passed since you initially listed the item and the listing has no bids. You can decrease the value of this field only if the listing has no bids (or no items have sold) and the listing does not end within 12 hours.

Note: As of April 1, 2019, 'GTC' is the only supported listing duration for all eBay marketplaces with the following exceptions:
  • The following eBay Motors US categories are exempt from this change: Cars & Trucks (6001), Motorcycles (6024), Other Vehicles & Trailers (6038), Boats (26429), Powersports (66466).
  • All child categories under Cars, Motorcycles & Vehicles (9800) categories on the eBay UK and eBay Italy sites are also exempt from this change.
If any other listing duration value besides GTC is specified in this field, it will be ignored, and GTC will be used instead.
XML Representation Summary
<ns:ListingDuration>
   
Content: 
{ xs:token }
</ns:ListingDuration>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="ListingDuration" type="xs:token"/>

ns:ListingEnhancement
Type:
Describes listing upgrades that sellers can select for a fee, such as the BoldTitle upgrade. Also includes feature packs for saving on listing upgrades. See Listing Upgrades in the eBay site help.

You cannot remove listing upgrades when you revise a listing. When you relist an item, use DeletedField to remove a listing upgrades.
XML Representation Summary
<ns:ListingEnhancement>
   
Content: 
{ enumeration of xs:token }
</ns:ListingEnhancement>
Simple Content
Enumeration:
XML Source (w/o annotations (1); see within schema source)
<xs:element maxOccurs="unbounded" minOccurs="0" name="ListingEnhancement" type="ns:ListingEnhancementsCodeType"/>

ns:ListingSubtype2
Type:
Indicates a specific type of lead generation format listing, such as classified ad or local market best offer listing. Only applicable when ListingType = LeadGeneration.

Note: ListingSubtype2 replaces the deprecated ListingSubtype field. If both are specified in a request, ListingSubtype2 takes precedence.
XML Representation Summary
<ns:ListingSubtype2>
   
Content: 
{ enumeration of xs:token }
</ns:ListingSubtype2>
Simple Content
Enumeration:
"ClassifiedAd"
 - 
This value indicates that the lead generation listing is a classifed ad. Note that only some eBay categories support classified ad listings. Use the GetCategoryFeatures call (with FeatureID value set to AdFormatEnabled) to see which categories support classified ad listings.
"LocalMarketBestOfferOnly"
 - 
This value indicates that the lead generation listing is a US Motors Local Market listing. Note that only some eBay Motors categories support Motors Local Market listings. Use the GetCategoryFeatures call (with the SITEID header set to 100 and the FeatureID value set to LocalMarketAdFormatEnabled) to see which eBay Motors categories support Motors Local Market listings.
"CustomCode"
 - 
Reserved for internal or future use
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="ListingSubtype2" type="ns:ListingSubtypeCodeType"/>

ns:ListingType
Type:
ns:ListingTypeCodeType, simple content
The selling format of the eBay listing, such as auction (indicated with Chinese value), fixed-price (indicated with FixedPriceItem value), or classified ad (indicated with AdType value).

If this field is not included in an AddItem, AddItems, or VerifyAddItem call, the listing type defaults to auction

For AddFixedPriceItem, RelistFixedPriceItem, or VerifyAddFixedPriceItem call, this field must be included and set to FixedPriceItem, since these calls only work with fixed-price listings.

This field is not applicable to Revise calls because the selling format of active listings cannot be changed.
XML Representation Summary
<ns:ListingType>
   
Content: 
{ enumeration of xs:token }
</ns:ListingType>
Simple Content
Enumeration:
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="ListingType" type="ns:ListingTypeCodeType"/>

ns:LiveAuction
Type:
xs:boolean, predefined, simple content
Note: This field is no longer applicable as eBay Live Auctions are no longer being held as of September 1, 2018. If this field is used in an Add/Revise/Relist call, it will be ignored and dropped.
XML Representation Summary
<ns:LiveAuction>
   
Content: 
{ xs:boolean }
</ns:LiveAuction>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="LiveAuction" type="xs:boolean"/>

ns:LocalListing
Type:
xs:boolean, predefined, simple content
This field is deprecated.
XML Representation Summary
<ns:LocalListing>
   
Content: 
{ xs:boolean }
</ns:LocalListing>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="LocalListing" type="xs:boolean"/>

ns:Location
Type:
xs:string, predefined, simple content
Indicates the geographical location of the item (along with the value in the Country field). When you revise a listing, you can add or change this value only if the listing has no bids (or no items have sold) and it does not end within 12 hours.

If you do not specify Location, you must specify Item.PostalCode. If you specify a postal code, but do not specify a location, then the location is given a default value derived from the postal code.

For the Classified Ad format for motors vehicle listings, the value provided in the Location field is used as item location only if the SellerContactDetails.Street and the SellerContactDetails.Street2 are empty. Else, the SellerContactDetails.Street and the SellerContactDetails.Street2 will be used for item location.
XML Representation Summary
<ns:Location>
   
Content: 
{ xs:string }
</ns:Location>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="Location" type="xs:string"/>

ns:LocationDefaulted
Type:
xs:boolean, predefined, simple content
If true, eBay provided a central location as a result of the user not specifying a location. This typically occurs when the seller specifies PostalCode without Location.
XML Representation Summary
<ns:LocationDefaulted>
   
Content: 
{ xs:boolean }
</ns:LocationDefaulted>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="LocationDefaulted" type="xs:boolean"/>

ns:LookupAttributeArray
Type:
This field is deprecated, and should no longer be used.
Component Diagram
XML Representation Summary
<ns:LookupAttributeArray>
   
Content: 
</ns:LookupAttributeArray>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="LookupAttributeArray" type="ns:LookupAttributeArrayType"/>

ns:LotSize
Type:
xs:int, predefined, simple content
A lot is a set of two or more similar items included in a single listing that must be purchased together in a single order line item. The Item.LotSize value is the number of items in the lot. This field is required if two or more items are including in one listing.

Lots can be used for auction and fixed-price listings. Lot items can be listed only in lot-enabled categories. Call GetCategories to determine if a category supports lots. If the returned CategoryArray.Category.LSD (LotSize Disabled) value is true, the category does not support lots.
XML Representation Summary
<ns:LotSize>
   
Content: 
{ xs:int }
</ns:LotSize>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="LotSize" type="xs:int"/>

ns:MechanicalCheckAccepted
Type:
xs:boolean, predefined, simple content
Indicates whether the seller allows the bidder to request mechanical inspection services from RAC. For the Car category listings on the UK site.
XML Representation Summary
<ns:MechanicalCheckAccepted>
   
Content: 
{ xs:boolean }
</ns:MechanicalCheckAccepted>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="MechanicalCheckAccepted" type="xs:boolean"/>

ns:NewLeadCount
Type:
xs:int, predefined, simple content
Specifies the number of new leads (unanswered emails) buyers have posted about the item.
XML Representation Summary
<ns:NewLeadCount>
   
Content: 
{ xs:int }
</ns:NewLeadCount>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="NewLeadCount" type="xs:int"/>

ns:PartnerCode
Type:
xs:string, predefined, simple content
This field is deprecated.
XML Representation Summary
<ns:PartnerCode>
   
Content: 
{ xs:string }
</ns:PartnerCode>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="PartnerCode" type="xs:string"/>

ns:PartnerName
Type:
xs:string, predefined, simple content
This field is deprecated.
XML Representation Summary
<ns:PartnerName>
   
Content: 
{ xs:string }
</ns:PartnerName>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="PartnerName" type="xs:string"/>

ns:PaymentAllowedSite
Type:
ns:SiteCodeType, simple content
Enables you to view the sites on which an item can be purchased, based on the payment methods offered for the item.
XML Representation Summary
<ns:PaymentAllowedSite>
   
Content: 
{ enumeration of xs:token }
</ns:PaymentAllowedSite>
Simple Content
Enumeration:
XML Source (w/o annotations (1); see within schema source)
<xs:element maxOccurs="unbounded" minOccurs="0" name="PaymentAllowedSite" type="ns:SiteCodeType"/>

ns:PaymentDetails
Type:
ns:PaymentDetailsType, complex content
This container is used in an Add/Revise/Relist/Verify call if the seller is selling a motor vehicle, and is requiring an initial deposit on that vehicle. This container is only applicable for motor vehicle listings.

Note: If you set up a payment policy via the Account API or the Business Polices Managment API, then you should not populate the fields in this PaymentDetails container. Instead, indicate your payment policy using the SellerProfiles.SellerPaymentProfile container.
This container will only be returned in 'Get' calls for motor vehicle listings where an initial deposit is required for that vehicle.
Component Diagram
XML Representation Summary
<ns:PaymentDetails>
   
Content: 
</ns:PaymentDetails>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="PaymentDetails" type="ns:PaymentDetailsType"/>

ns:PaymentMethods
Type:
Identifies the payment method (such as PayPal) that the seller will accept when the buyer pays for the item. For Add/Revise/Relist calls, at least one payment method must be specified unless the seller is onboarded for eBay managed payments.

Note: If you set up a payment policy via the Account API or the Business Polices Managment API, then you should not populate this field. Instead, indicate your payment policy using the SellerProfiles.SellerPaymentProfile container.
Note: eBay managed payments is currently available to a select set of sellers. For the current list of eBay marketplaces in which eBay managed payments has rolled out, see the eBay Managed Payments landing page. For sellers in the eBay managed payments program, a payment method does not need to be specified at listing time. Any payment method that is specified at listing time (or defined in a payment business policy) will be ignored and dropped from the listing, and the seller will get a warning message in the response. Immediate payment is supported for sellers in the eBay managed payments program, so they can include the AutoPay field in the request and set its value to true.
Note: As of May 1, 2019, eBay no longer supports electronic payments through a seller's Integrated Merchant Credit Card account. If IMCC is passed in as a value, this value will be ignored and dropped (and listing will possibly get blocked if IMCC is the only specified payment method).
Use GetCategoryFeatures to determine the payment methods that are allowed for a category on a site. For example, the response data of GetCategoryFeatures will show that on the US site, most categories only allow electronic payments. Also use GetCategoryFeatures to determine the default payment methods for a site.

Do not use GeteBayDetails to determine the payment methods for a site.

If you specify multiple PaymentMethods fields, the repeating fields must be contiguous. For example, you can specify PayPalEmailAddress after a list of repeating PaymentMethods fields, but not between them:

<PaymentMethods>VisaMC</PaymentMethods>
<PaymentMethods>PayPal</PaymentMethods>
<PayPalEmailAddress>mypaypalemail@ebay.com</PayPalEmailAddress>


In general, if you separate repeating instances of a field, the results will be unpredictable. This rule applies to all repeating fields (maxOccurs="unbounded" or greater than 1) in the schema. See Overview of the API Schema in the eBay Features Guide.

Note: Required or allowed payment methods vary by site and category. Refer to Determining the Payment Methods Allowed for a Category in the eBay Features Guide to help you determine which payment methods you are required or allowed to specify.
Payment methods are not applicable to any classified ad listings, as any agreement and payment is handled off of the eBay platform.

For ReviseItem and RelistItem only: A listing must have at least one valid payment method. When you revise or relist an item and you specify a payment method that is invalid for the target site, eBay ignores the invalid payment method, applies the other valid changes, and returns a warning to indicate that the invalid payment method was ignored.

If multiple payment methods were invalid, the warning indicates that they were all ignored. If you modify the listing so that it includes no valid payment methods, an error is returned. This situation could occur when the seller removes all valid payment methods or when all the payment methods specified for the item are no longer valid on the target site.
XML Representation Summary
<ns:PaymentMethods>
   
Content: 
{ enumeration of xs:token }
</ns:PaymentMethods>
Simple Content
Enumeration:
XML Source (w/o annotations (1); see within schema source)
<xs:element maxOccurs="unbounded" minOccurs="0" name="PaymentMethods" type="ns:BuyerPaymentMethodCodeType"/>

ns:PayPalEmailAddress
Type:
xs:string, predefined, simple content
Valid PayPal email address for the PayPal account that the seller will use if they offer PayPal as a payment method for the listing.

Note: If you set up a payment policy via the Account API or the Business Polices Managment API, then you should not populate this field. Instead, indicate your payment policy using the SellerProfiles.SellerPaymentProfile container.
eBay uses this to identify the correct PayPal account when the buyer pays via PayPal during the checkout process. (As a seller can have more than one PayPal account, you cannot necessarily rely on PayPal account data returned from GetUser for details about the account associated with the PayPal email address that the seller specifies.)

Required if seller has chosen PayPal as a payment method (PaymentMethods) for the listing.

For digital listings, the seller needs to use an email address that is associated with a PayPal Premier or PayPal business account.

For ReviseItem and RelistItem only: To remove this value when you revise or relist an item, use DeletedField. When you revise a listing, if the listing has bids (or items have been sold) or it ends within 12 hours, you can add PayPalEmailAddress, but you cannot remove it.
XML Representation Summary
<ns:PayPalEmailAddress>
   
Content: 
{ xs:string }
</ns:PayPalEmailAddress>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="PayPalEmailAddress" type="xs:string"/>

ns:PickupInStoreDetails
Type:
This container is used in Add/Revise/Relist/Verify listing calls by the seller to enable a listing with the 'In-Store Pickup' feature. The 'In-Store Pickup' feature is only available to a limited number of large retail merchants in the US, Canada, UK, Germany, and Australia marketplaces.

This container is returned in the 'Get' calls if the listing is enabled with the In-Store Pickup feature.
Component Diagram
XML Representation Summary
<ns:PickupInStoreDetails>
   
Content: 
</ns:PickupInStoreDetails>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="PickupInStoreDetails" type="ns:PickupInStoreDetailsType"/>

ns:PictureDetails
Type:
ns:PictureDetailsType, complex content
This container consists of the data associated with photos within the listing. With most eBay sites and categories, a seller can add up to 12 photos to their listings free of charge. These photos can be hosted by eBay Picture Services (EPS), or the seller can host pictures on a non-eBay server. If pictures are externally-hosted, they must be hosted on a site that is using the 'https' protocol.

It is required that all listings have at least one picture. eBay Motors listings can have up to 24 pictures.
Component Diagram
XML Representation Summary
<ns:PictureDetails>
   
Content: 
</ns:PictureDetails>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="PictureDetails" type="ns:PictureDetailsType"/>

ns:PostalCode
Type:
xs:string, predefined, simple content
Postal code of the place where the item is located. This value is used for proximity searches. To remove this value when revising or relisting an item, use DeletedField. If you do not specify PostalCode, you must specify Item.Location. If you specify PostalCode, but do not specify Item.Location, then Item.Location is given a default value derived from the postal code.

Note: As of late January 2020, the displayed postal code returned in GetItem is now masked to all users except for the seller of the item. Different countries will mask postal/zip codes in slightly different ways, but an example would be 951**.
XML Representation Summary
<ns:PostalCode>
   
Content: 
{ xs:string }
</ns:PostalCode>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="PostalCode" type="xs:string"/>

ns:PrimaryCategory
Type:
ns:CategoryType, complex content
This container is used in an Add/Revise/Relist call to set the primary listing category. This field is conditionally required in an Add call unless the seller successfully uses the ProductListingDetails container to find an eBay catalog product match. When the seller successfully uses an eBay catalog product to create a listing, the listing title, listing description, Item Specifics, listing category, and stock photo defined in the catalog product is used to create the listing.

If you do not know the appropriate eBay category for your product, you can use the GetSuggestedCategories call. Once you know your category, and want to know which listing features it supports, you can use the GetCategoryFeatures call. To discover if the category requires or recommends GTIN types and other Item Specifics, you can use the GetCategorySpecifics call.

If you do use an eBay catalog product, it is advised that you do not include this field, as any primary category ID you specify in this field may get dropped if this category is different than the primary category defined in the eBay catalog product.

For ReviseItem only: When revising a listing, you can change the primary category only if an auction listing has no bids or a multiple-quantity, fixed-price listing has no sales, and the listing does not end within 12 hours. If you change the listing category, any Item Specifics that were previously specified may be dropped from the listing if they aren't valid for the new category.

When you list an event ticket on the US site, you must specify one of the leaf categories under the Tickets & Experiences meta category.
Component Diagram
XML Representation Summary
<ns:PrimaryCategory>
   
Content: 
</ns:PrimaryCategory>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="PrimaryCategory" type="ns:CategoryType"/>

ns:PrivateListing
Type:
xs:boolean, predefined, simple content
A true value in this field indicates that the listing is private. In a private listing, a bidder or buyer's user ID will not be exposed to any other eBay user besides the seller of the listing. Sellers may want to use this option when they believe that a listing's potential bidders/buyers would not want their user IDs exposed to other users.
XML Representation Summary
<ns:PrivateListing>
   
Content: 
{ xs:boolean }
</ns:PrivateListing>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="PrivateListing" type="xs:boolean"/>

ns:PrivateNotes
Type:
xs:string, predefined, simple content
A note that a user makes on an item from their My eBay account. GetMyeBayBuying and GetMyeBaySelling return this field, and only if you pass in the IncludeNotes field in the request, and set its value to true. This field will only be returned if set for an item, and only returned to the user who created the note.

Not supported as input in ReviseItem. Use SetUserNotes instead.

For GetMyeBayBuying In WatchList, notes for variations are only returned at the Item level, not the variation level. They are only set if you specified ItemID (if no purchases) or ItemID and VariationSpecifics (if there are purchases) in SetUserNotes (or selected the equivalent in the My eBay UI on the site).

In WonList, notes for variations are only returned at the Item level, not the variation level. They are only set if you specified ItemID and TransactionID in SetUserNotes (or selected the equivalent in the My eBay UI on the site).
XML Representation Summary
<ns:PrivateNotes>
   
Content: 
{ xs:string }
</ns:PrivateNotes>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="PrivateNotes" type="xs:string"/>

ns:ProductListingDetails
Type:
This container is used to provide one or more product identifiers for a product, and if desired by the seller, eBay will use the identifier(s) of the product to try to match it to a defined product in the eBay catalog. If a seller's product is matched to an eBay catalog product, the product details associated with that catalog product will be prefilled for the listing. Product details defined for a catalog product include the product title, product description, product aspects, and stock image(s) of the product (if available).

In some eBay categories, one or more product identifier types (e.g. UPC or ISBN) may be required, but the category may not have any eBay catalog products defined, or the category does not allow listings to be created using a catalog product. Note that the GetCategorySpecifics call or the GetCategoryFeatures call can be used to retrieve supported/required product identifier types.

Note: If a product identifier type is required, the corresponding field must be used, even if the seller is not interested in finding an eBay catalog product match. A large percentage of eBay US categories require one or more product identifier types when listing an item. See the Structured Data - Product Identifiers help page for more information on which eBay US categories require which product identifier types. If known, an ePID (specified through the ProductReferenceID field) is always the best bet to find an eBay catalog product match, although an EAN, ISBN, UPC, or Brand/MPN pair can also be used in an attempt to find a catalog product match. If a Brand/MPN pair is required for the product, these values must be input through the BrandMPN container.
When you use ProductListingDetails, in an Add/Revise/Relist call, you must specify at least one GTIN, a ProductReferenceID (also known as an ePID), a Brand/MPN pair, or TicketListingDetails. If you specify more than one GTIN value, eBay uses the first one that matches a product in eBay's catalog.

For ReviseItem and RelistItem only: When you revise a listing, if it has bids or it ends within 12 hours, you cannot change the product identifier and you cannot remove existing product listing details data. However, you can change or add preferences such as IncludeStockPhotoURL, UseStockPhotoURLAsGallery, and IncludePrefilledItemInformation. To delete all catalog data when you revise or relist an item, specify Item.ProductListingDetails in DeletedField and don't pass ProductListingDetails in the request.
Component Diagram
XML Representation Summary
<ns:ProductListingDetails>
   
Content: 
</ns:ProductListingDetails>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="ProductListingDetails" type="ns:ProductListingDetailsType"/>

ns:ProxyItem
Type:
xs:boolean, predefined, simple content
Some listings on the eBay platform originate from eBay affiliates. Depending on the relationship the affiliate has with eBay, there are times when the affiliate retains ownership of the listing. When this occurs the representation of the listing on eBay is considered a proxy item. Proxy items can only be edited using API requests from the applications that originally listed them.
XML Representation Summary
<ns:ProxyItem>
   
Content: 
{ xs:boolean }
</ns:ProxyItem>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="ProxyItem" type="xs:boolean"/>

ns:Quantity
Type:
xs:int, predefined, simple content
For AddItem family of calls: The Quantity value for auction listings must always be 1. For a fixed-price listing, the Quantity value indicates the number of identical items the seller has available for sale in the listing. If this field is not included when creating a new fixed-price listing, quantity defaults to '1'. If variations are specified in AddFixedPriceItem or VerifyAddFixedPriceItem, the Item.Quantity is not required since the quantity of variations is specified in Variation.Quantity instead. See the Creating a listing with variations eBay Help page for more information on variations.

For ReviseItem and ReviseFixedPriceItem: This value can only be changed for a fixed-price listing with no variations. The quantity of variations is controlled in the Variation.Quantity field and the Item.Quantity value for an auction listing should always be 1.

For RelistItem and RelistFixedPriceItem: Like most fields, when you use RelistItem or RelistFixedPriceItem, Quantity retains its original value unless you specifically change it. This means that the item is relisted with the value that was already in Quantity, not with the remaining quantity available. For example, if the original Quantity value was 10, and three items have been sold, eBay sets the relisted item's Quantity to 10 by default, and not 7. So, we strongly recommend that you always set Quantity to the correct value (your actual quantity available) in your relist requests.

When eBay auto-renews a GTC listing (ListingDuration = GTC) on your behalf, eBay relists with correct quantity available.

For GetSellerEvents: Quantity is only returned for listings where item quantity is greater than 1.

For GetItem and related calls: This is the total of the number of items available for sale plus the quantity already sold. To determine the number of items available, subtract SellingStatus.QuantitySold from this value.

For order line item calls with variations: In GetItemTransactions, Item.Quantity is the same as GetItem (the total quantity across all variations). In GetSellerTransactions, Transaction.Item.Quantity is the total quantity of the applicable variation (quantity available plus quantity sold).

Note: For the US site, new eBay sellers are subject to Seller Limits, which limit the quantity of items that may be listed and/or the total cumulative value of these listings. While subject to these selling limits, an eBay seller can use the GetMyeBaySelling call to retrieve both the remaining number of listings they can create and the remaining cumulative value of these listings. These values are shown in the Summary.QuantityLimitRemaining and Summary.AmountLimitRemaining fields in the GetMyeBaySelling response. If a call to add an item or revise an item would result in the exceeding of these limits, the add item or revise item call will fail. These fields will only be returned if the seller is subject to seller limits.
XML Representation Summary
<ns:Quantity>
   
Content: 
{ xs:int }
</ns:Quantity>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="Quantity" type="xs:int"/>

ns:QuantityAvailable
Type:
xs:int, predefined, simple content
This integer value indicates the quantity of an item that is still available for purchase in a multiple-quantity, fixed-price listing. This field is not applicable to auction listings.
XML Representation Summary
<ns:QuantityAvailable>
   
Content: 
{ xs:int }
</ns:QuantityAvailable>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="QuantityAvailable" type="xs:int"/>

ns:QuantityAvailableHint
Type:
Indicates the type of message that will be returned describing the quantity available for the item.
XML Representation Summary
<ns:QuantityAvailableHint>
   
Content: 
{ enumeration of xs:token }
</ns:QuantityAvailableHint>
Simple Content
Enumeration:
"Limited"
 - 
(out) The message "Limited quantity available" is shown in the web flow (e.g., for a flash sale or a Daily Deal).
"MoreThan"
 - 
(out) The message "More than 10 available" is shown in the web flow. 10 is the value of QuantityThreshold tag based on the seller's preference.
"CustomCode"
 - 
Reserved for internal or future use.
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="QuantityAvailableHint" type="ns:QuantityAvailableHintCodeType"/>

ns:QuantityInfo
Type:
ns:QuantityInfoType, complex content
This container is used to set the minimum number of event tickets that should remain available after a buyer makes a purchase. This functionality allows the seller to avoid the possibility of being left with just one event ticket after a sale.

This container can be used when adding, revising, or relisting event tickets, and it will only be returned in GetItem if set for the listing.
Component Diagram
XML Representation Summary
<ns:QuantityInfo>
   
Content: 
</ns:QuantityInfo>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="QuantityInfo" type="ns:QuantityInfoType"/>

ns:QuantityRestrictionPerBuyer
Type:
This container is used by the seller to restrict the quantity of items that may be purchased by one buyer during the duration of a fixed-price listing (single or multi-variation). This is an optional container that can be used with an Add, Revise, or Relist call.

This container is not applicable to auction listings.
Component Diagram
XML Representation Summary
<ns:QuantityRestrictionPerBuyer>
   
Content: 
</ns:QuantityRestrictionPerBuyer>
XML Source (w/o annotations (1); see within schema source)

ns:QuantityThreshold
Type:
xs:int, predefined, simple content
The quantity threshold above which the seller prefers not to show the actual quantity available. Returned when the quantity available is greater than the value of quantity threshold. Currently, 10 is the only available value for this threshold.
XML Representation Summary
<ns:QuantityThreshold>
   
Content: 
{ xs:int }
</ns:QuantityThreshold>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="QuantityThreshold" type="xs:int"/>

ns:QuestionCount
Type:
xs:long, predefined, simple content
Specifies the number of questions buyers have posted about the item. Returned only if greater than 0.
XML Representation Summary
<ns:QuestionCount>
   
Content: 
{ xs:long }
</ns:QuestionCount>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="QuestionCount" type="xs:long"/>

ns:ReasonHideFromSearch
Type:
This field is returned only when the listing is currently being hidden from any searches occurring on eBay. Listings may be hidden from search if an active listing is currently out of stock or if the listing has been determined by eBay to be a duplicate listing.
XML Representation Summary
<ns:ReasonHideFromSearch>
   
Content: 
{ enumeration of xs:token }
</ns:ReasonHideFromSearch>
Simple Content
Enumeration:
"DuplicateListing"
 - 
This value indicates that the listing is being hidden from search on the eBay site because the listing has been determined by eBay to be a duplicate listing.

This enumeration value is associated with eBay Duplicate Listings Policy, which is applicable on the US, CA, CA-FR, and eBay Motors (Parts and Accessories only) sites. Event Tickets, Real Estate, and Motor Vehicle categories are excluded from this policy. For more information, read eBay's Duplicate Listings Policy help page.
"OutOfStock"
 - 
This value indicates that the listing is currently hidden from search because the quantity in the listing is zero. However, the listing is still alive and will reappear in the search results when the quantity is set to something greater than zero. The 'Out-of-stock' option is set by the seller at the account level. This option can be enabled in My eBay Site Preferences, or the seller can use the OutOfStockControlPreference field in the SetUserPreferences call.
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="ReasonHideFromSearch" type="ns:ReasonHideFromSearchCodeType"/>

ns:RegionID
Type:
xs:string, predefined, simple content
This field is deprecated.
XML Representation Summary
<ns:RegionID>
   
Content: 
{ xs:string }
</ns:RegionID>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="RegionID" type="xs:string"/>

ns:Relisted
Type:
xs:boolean, predefined, simple content
This boolean field is returned as true if the item in this listing was relisted. When an item is relisted, a brand new Item ID value is automatically created by eBay. This field is only returned for an original listing whose item has been relisted, so a false value should never get returned.

Note: A new listing will not return this field.
XML Representation Summary
<ns:Relisted>
   
Content: 
{ xs:boolean }
</ns:Relisted>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="Relisted" type="xs:boolean"/>

ns:RelistLink
Type:
xs:boolean, predefined, simple content
Applicable only to relisting an item. If true, creates a link in the item's old listing for the item that points to the new relist page, which accommodates users who might still look for the item under its old item ID.
XML Representation Summary
<ns:RelistLink>
   
Content: 
{ xs:boolean }
</ns:RelistLink>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="RelistLink" type="xs:boolean"/>

ns:RelistParentID
Type:
xs:long, predefined, simple content
The identifier of the original listing that contained the item before the item was relisted. This field is only returned for an item that was relisted.
XML Representation Summary
<ns:RelistParentID>
   
Content: 
{ xs:long }
</ns:RelistParentID>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="RelistParentID" type="xs:long"/>

ns:ReservePrice
Type:
ns:AmountType, simple content
The lowest price at which the seller is willing to sell an auction item. (StartPrice must be lower than ReservePrice .) Not all categories support a Reserve Price. Use GetCategories to see if a category supports a Reserve Price. In calls that retrieve item data, the ReservePrice field will only be returned to the auction item's seller, and only if a Reserve Price has been set up. A Reserve Price is not applicable to fixed-price or classified ad listings.

You can remove the Reserve price of a US eBay Motors listing if the category allows it, the current Reserve Price has not been met, and the Reserve Price is at least $2.00 more than the current high bid. In this case, if the item has bids, the Reserve Price is set to $1.00 over the current high bid. The next bid meets the Reserve Price and wins. See Fees Overview below for information about fee credits that may be available when the Reserve Price is removed for a Motors listing.
Component Diagram
XML Representation Summary
<ns:ReservePrice
   
 = 
("AFA" | "ALL" | "DZD" | "ADP" | "AOA" | "ARS" | "AMD" | "AWG" | "AZM" | "BSD" | "BHD" | "BDT" | "BBD" | "BYR" | "BZD" | "BMD" | "BTN" | "INR" | "BOV" | "BOB" | "BAM" | "BWP" | "BRL" | "BND" | "BGL" | "BGN" | "BIF" | "KHR" | "CAD" | "CVE" | "KYD" | "XAF" | "CLF" | "CLP" | "CNY" | "COP" | "KMF" | "CDF" | "CRC" | "HRK" | "CUP" | "CYP" | "CZK" | "DKK" | "DJF" | "DOP" | "TPE" | "ECV" | "ECS" | "EGP" | "SVC" | "ERN" | "EEK" | "ETB" | "FKP" | "FJD" | "GMD" | "GEL" | "GHC" | "GIP" | "GTQ" | "GNF" | "GWP" | "GYD" | "HTG" | "HNL" | "HKD" | "HUF" | "ISK" | "IDR" | "IRR" | "IQD" | "ILS" | "JMD" | "JPY" | "JOD" | "KZT" | "KES" | "AUD" | "KPW" | "KRW" | "KWD" | "KGS" | "LAK" | "LVL" | "LBP" | "LSL" | "LRD" | "LYD" | "CHF" | "LTL" | "MOP" | "MKD" | "MGF" | "MWK" | "MYR" | "MVR" | "MTL" | "EUR" | "MRO" | "MUR" | "MXN" | "MXV" | "MDL" | "MNT" | "XCD" | "MZM" | "MMK" | "ZAR" | "NAD" | "NPR" | "ANG" | "XPF" | "NZD" | "NIO" | "NGN" | "NOK" | "OMR" | "PKR" | "PAB" | "PGK" | "PYG" | "PEN" | "PHP" | "PLN" | "USD" | "QAR" | "ROL" | "RUB" | "RUR" | "RWF" | "SHP" | "WST" | "STD" | "SAR" | "SCR" | "SLL" | "SGD" | "SKK" | "SIT" | "SBD" | "SOS" | "LKR" | "SDD" | "SRG" | "SZL" | "SEK" | "SYP" | "TWD" | "TJS" | "TZS" | "THB" | "XOF" | "TOP" | "TTD" | "TND" | "TRL" | "TMM" | "UGX" | "UAH" | "AED" | "GBP" | "USS" | "USN" | "UYU" | "UZS" | "VUV" | "VEB" | "VND" | "MAD" | "YER" | "YUM" | "ZMK" | "ZWD" | "ATS" | "CustomCode")
   
>
   
Content: 
{ xs:double }
</ns:ReservePrice>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="ReservePrice" type="ns:AmountType"/>

ns:ReturnPolicy
Type:
ns:ReturnPolicyType, complex content
Describes the seller's return policy. Most categories on most eBay sites require the seller to clearly specify whether or not returns are accepted (see ReturnsAcceptedOption).

Note: If you set up a return policy via the Account API or the Business Polices Managment API, then you should not populate the fields in this ReturnPolicy container. Instead, indicate your return policy using the SellerProfiles.SellerReturnProfile container.

However, if you do not configure a return policy, all the fields in this ReturnPolicy container that are marked conditional must be populated in your request.

For the AddItem family of calls: Required for most categories on most sites. Use ReturnPolicyEnabled in GetCategoryFeatures to determine which categories require this field. Also use ReturnPolicyDetails in GeteBayDetails to determine which ReturnPolicy fields can be used on each site.

Australia (AU) and US eBay Motors Parts and Accessories categories typically support but do not require a return policy. (However, we strongly recommend that you specify a clear return policy whenever possible.)

For ReviseItem only: If the listing has bids or sales and it ends within 12 hours, you can't change the return policy details. If the listing is a GTC listing that has sales or ends within 12 hours (one or the other, but not both), you can add a return policy to the GTC listing (but you can't change return policy details if already present). If the listing has no bids or sales and more than 12 hours remain before the listing ends, you can add or change the return policy. When you revise your return policy, you only need to specify the fields you want to add or change. You don't need to specify all the other ReturnPolicy fields again. The other fields will retain their existing settings.

For the GetItem family of calls: Only returned if the site you sent the request to supports the seller's return policy. Typically, the return policy details are only returned when the request is sent to the listing site.

Note: The GeteBayDetails call can be used to retrieve site-wide return policy metadata, but it is recommended that sellers use the GetCategoryFeatures call instead, as this call was recently updated to retrieve category-level metadata for both domestic and international return policies.
Note: In May 2018, eBay added the ability to create a separate international return policy for items that are shipped to international customers. If a seller does not add a separate international return policy, the settings in the domestic return policy will be used instead for international returns. For more information on setting separate domestic and international return policies, see the International returns policy help topic. For the international equivalent of this field, see the InternationalRefundMethodValues field.
Component Diagram
XML Representation Summary
<ns:ReturnPolicy>
   
Content: 
</ns:ReturnPolicy>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="ReturnPolicy" type="ns:ReturnPolicyType"/>

ns:ReviseStatus
Type:
ns:ReviseStatusType, complex content
This container is returned if a listing has been revised in any way since it first became active. One or more boolean fields will be returned under this container based on the type of revision(s) that occured, including a general revision, a price change, or a feature added or removed.
Component Diagram
XML Representation Summary
<ns:ReviseStatus>
   
Content: 
</ns:ReviseStatus>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="ReviseStatus" type="ns:ReviseStatusType"/>

ns:ScheduleTime
Type:
xs:dateTime, predefined, simple content
Allows the user to specify a time in the future that the listing becomes active on eBay. To schedule the listing start time, specify a time in the future in GMT format. In GetItem and related calls, the scheduled time is returned in StartTime. For ReviseItem, you can modify this value if the currently scheduled start time is in the future (listing has yet to go live).

When you schedule a start time, the start time is randomized within 15-minute intervals. Randomized start times applies to the following sites:
AT, BEFR, BENL, CH, DE, ES, FR, IE, IT, NL, PL, UK

Also see the following article in the Knowledge Base: Why scheduled time is sometimes getting reset.
XML Representation Summary
<ns:ScheduleTime>
   
Content: 
{ xs:dateTime }
</ns:ScheduleTime>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="ScheduleTime" type="xs:dateTime"/>

ns:SearchDetails
Type:
ns:SearchDetailsType, complex content
This field is deprecated.
Component Diagram
XML Representation Summary
<ns:SearchDetails>
   
Content: 
</ns:SearchDetails>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="SearchDetails" type="ns:SearchDetailsType"/>

ns:SecondaryCategory
Type:
ns:CategoryType, complex content
The unique identifer for a secondary category. This field is only applicable if the seller decides to list the item under two categories.

You cannot list US eBay Motors vehicles in two categories. However, you can list Parts & Accessories in two categories. The Final Value Fee is based on the primary category in which the item is listed. Furthermore, you can list the same item in an eBay Motors Parts & Accessories category and in an eligible eBay category, as long as the primary category is associated with the site on which you are listing. That is, the two categories can be a mix of Motors Parts & Accessories and eBay site categories. (Real Estate, Mature Audience (adult), and Business & Industrial categories are not eligible for listing in two categories in this manner.) For example, if you list on Motors, the primary category could be 6750 (eBay Motors > Parts & Accessories > Apparel & Merchandise > Motorcycle > Jackets & Leathers), and the secondary category could be 57988 (eBay > Clothing, Shoes > Accessories > Men's Clothing > Outerwear). If you list on the main eBay site, the primary category could be 57988 and the secondary category could be 6750.

If eBay has designated a listing category as a value category (see ValueCategory in GetCategoryFeatures), and that listing category will be the seller's primary category, the seller will not be able to list their item in a secondary category. If a seller's request payload includes a primary or a secondary category that is designated as a value category, then eBay drops the SecondaryCategory ID and only lists the item in the category specified with the PrimaryCategory ID. Also, if the listing request includes Item Specifics (in ItemSpecifics) that are associated with the SecondaryCategory, eBay drops those values as well when the SecondaryCategory is dropped. The same logic is used if you revise an existing listing to add a secondary category, or to change one of the categories: If either the primary or secondary category is a value category, eBay drops the secondary category from your request.)

To remove this value when relisting an item, use DeletedField.

For ReviseItem only: When revising a listing within 12 hours of the listing's scheduled end time, you can only add or change the secondary category when an auction listing has no active bids or a multiple-quantity, fixed-price listing has no items sold. If you change the secondary category, any corresponding Item Specifics that were previously specified may be dropped from the listing if they aren't valid for the category.

For ReviseItem only: Previously, removing the listing from a secondary category was only possible within 12 hours of the listing's scheduled end time when an auction listing had no active bids or a multiple-quantity, fixed-price listing had no items sold, but this restriction no longer exists. Now, the secondary category can be dropped for any active listing at any time, regardless of whether an auction listing has bids or a fixed-price listing has sales. To drop a secondary category, the seller passes in a value of 0 in the SecondaryCategory.CategoryID field.
Component Diagram
XML Representation Summary
<ns:SecondaryCategory>
   
Content: 
</ns:SecondaryCategory>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="SecondaryCategory" type="ns:CategoryType"/>

ns:Seller
Type:
ns:UserType, complex content
Container for information about this listing's seller.

Returned by GetItemsAwaitingFeedback if Buyer is making the request.
Component Diagram
XML Representation Summary
<ns:Seller>
   
Content: 
</ns:Seller>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="Seller" type="ns:UserType"/>

ns:SellerContactDetails
Type:
ns:AddressType, complex content
This container is used by sellers of Classified Ad listings to provide contact information.
Component Diagram
XML Representation Summary
<ns:SellerContactDetails>
   
Content: 
</ns:SellerContactDetails>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="SellerContactDetails" type="ns:AddressType"/>

ns:SellerProfiles
Type:
ns:SellerProfilesType, complex content
This container is used if the seller would like to use/reference business policies to create, revise, relist, or verify their listing. The seller's account must be opted in to business policies to use this container. If this container is used, exactly one Payment Business Policy, one Shipping Business Policy, and one Return Business Policy must be specified and applied to the listing. If the seller's account is not opted in to business policies, that seller may not use this container. Sellers must opt-in to business policies through My eBay or by using the optInToProgram call of the eBay Account API.

If business policies are applied to a listing, all payment, shipping, and return policy settings in these policies will override any other payment, shipping, or return policy legacy fields that are included in the call request.

This container is only returned in 'Get' calls if business policies are set for the listing, and the person making the API call is the seller of the listing.
Component Diagram
XML Representation Summary
<ns:SellerProfiles>
   
Content: 
</ns:SellerProfiles>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="SellerProfiles" type="ns:SellerProfilesType"/>

ns:SellerProvidedTitle
Type:
xs:string, predefined, simple content
A descriptive free-text title for a US or CA eBay Motors vehicle listing. This title appears below eBay's pre-filled listing title on the View Item page (not at the top of the View Item page). It's also appended to the listing title in search results (like a subtitle) on the US eBay Motors site. Keywords in this title help buyers find or distinguish your listing.

Applicable to listings in US eBay Motors Cars and Trucks, Motorcycle, and some of the Powersport, Boats and RV campers categories; or to Cars and Trucks listings on CA eBay Motors.

This replaces the older US and Canada eBay Motors Subtitle attribute (attribute ID 4148).
XML Representation Summary
<ns:SellerProvidedTitle>
   
Content: 
{ xs:string }
</ns:SellerProvidedTitle>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="SellerProvidedTitle" type="xs:string"/>

ns:SellerVacationNote
Type:
xs:string, predefined, simple content
This field is returned if the seller of the item is currently on vacation and that seller has turned on the Store vacation setting, and has included a message to display to shoppers who visit the eBay store. If the seller turns on the Store vacation setting, the listing will be hidden from search result pages.

Store vacation settings, including this note, are set through the Messages tab in My eBay, or this message can also be set through the SetStorePreferences call.

The Store vacation setting is only applicable for sellers with eBay stores.
XML Representation Summary
<ns:SellerVacationNote>
   
Content: 
{ xs:string }
</ns:SellerVacationNote>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="SellerVacationNote" type="xs:string"/>

ns:SellingStatus
Type:
ns:SellingStatusType, complex content
Various details about the current status of the listing, such as the current number of bids, the current high bidder, quantity sold, current price, and listing status.
Component Diagram
XML Representation Summary
<ns:SellingStatus>
   
Content: 
</ns:SellingStatus>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="SellingStatus" type="ns:SellingStatusType"/>

ns:ShippingDetails
Type:
ns:ShippingDetailsType, complex content
The shipping-related details for an order, including flat and calculated shipping costs.

Note: For sellers who are using a shipping (aka Fulfillment) business policy to create/revise/relist an item, none of the fields under the ShippingDetails container are necessary. A fulfillment business policy can be set up and/or modified in My eBay, or via the Account API or the Business Polices Managment API. A fulfillment business policy is associated to a listing through the Item.SellerProfiles.SellerShippingProfile container.

If you do not use a fulfillment business policy, many of the fields under this ShippingDetails container become required in your request.

New users who list their first items in selected categories on the US site must specify at least one domestic shipping service. This applies to a category if GetCategoryFeatures returns true for Category.ShippingTermsRequired.

For multi-quantity, fixed-price listings, a seller can revise all shipping details of the listing (except for sales tax and for shipping type of Freight) for all unsold items. This applies to both domestic and international shipping. Checkout is not affected for those who bought items prior to the seller's shipping changes—the shipping details that were in effect at the time of purchase are used for that buyer at the time of checkout.

Shipping details are not applicable to any classified ad listings, as shipping/delivery/pickup is handled by the buyer and seller off of the eBay platform.

Note: To create a listing that is 'Local Pickup only' (buyer picks up, with no shipping/delivery available), the user does the following two things:
  • Either omit the entire ShippingDetails container, or pass in an empty ShippingDetails container - <ShippingDetails/>
  • Pass in one ShipToLocations field, with its value set to None - <ShipToLocations>None</ShipToLocations>

For GetMyeBayBuying, GetMyeBaySelling: ShippingDetails is not returned.
Component Diagram
XML Representation Summary
<ns:ShippingDetails>
   
Content: 
</ns:ShippingDetails>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="ShippingDetails" type="ns:ShippingDetailsType"/>

ns:ShippingOverride
Type:
ns:ShippingOverrideType, complex content
This field is reserved for internal or future use.
Component Diagram
XML Representation Summary
<ns:ShippingOverride>
   
Content: 
</ns:ShippingOverride>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="ShippingOverride" type="ns:ShippingOverrideType"/>

ns:ShippingPackageDetails
Type:
ns:ShipPackageDetailsType, complex content
Container consisting of dimension and size details related to a shipping package in which an item will be sent. The information in this container is applicable if the seller is using calculated shipping or flat rate shipping using shipping rate tables with weight surcharges. This container is only returned in the Get calls if specified for the item.
Component Diagram
XML Representation Summary
<ns:ShippingPackageDetails>
   
Content: 
</ns:ShippingPackageDetails>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="ShippingPackageDetails" type="ns:ShipPackageDetailsType"/>

ns:ShippingServiceCostOverrideList
Type:
This container is used when the seller wants to override the flat shipping costs for all domestic and/or all international shipping services defined in the shipping business policy referenced in the SellerProfiles.SellerShippingProfile.ShippingProfileID field. Shipping costs include the cost to ship one item, the cost to ship each additional identical item, and any shipping surcharges applicable to domestic shipping services.

A ShippingServiceCostOverrideList.ShippingServiceCostOverride container is required for each domestic and/or international shipping service that is defined in the domesticShippingPolicyInfoService and intlShippingPolicyInfoService containers of the shipping business policy.

Shipping service cost overrides are a listing-level concept, and the shipping costs specified through each ShippingServiceCostOverrideList.ShippingServiceCostOverride container will not change the shipping costs defined for the same shipping services in the shipping business policy.

For Revise and Relist calls: To delete all shipping service cost overrides when you revise or relist, specify Item.ShippingServiceCostOverrideList in DeletedField, and don't pass ShippingServiceCostOverrideList in the request.
Component Diagram
XML Representation Summary
<ns:ShippingServiceCostOverrideList>
   
Content: 
</ns:ShippingServiceCostOverrideList>
XML Source (w/o annotations (1); see within schema source)

ns:ShipToLocations
Type:
xs:string, predefined, simple content
An international location or region to which the seller is willing to ship, regardless of shipping service. The country of the listing site is added by eBay.

Note: If you set up a fulfillment policy via the Account API or the Business Polices Managment API, then you should not populate the ShipToLocations field. Instead, indicate your fulfillment policy using the SellerProfiles.SellerShippingProfile container.
Use GeteBayDetails with a DetailName of ShippingLocationDetails to determine which international locations are valid for the site. Omit ShipToLocations if you want to ship only within the country of the listing site. To state that you do not wish to ship at all, set ShipToLocations to None. ReviseItem can add a ShipToLocations. On output, ShipToLocations is the collection of all input item-level ShipToLocations plus international shipping service-level ShipToLocation values.

If you have specified a region to which you will ship (such as Asia), you can use ExcludeShipToLocation to exclude certain countries within that region to where you will not ship (such as Afghanistan).

Note: To create a listing that is 'Local Pickup only' (buyer picks up, with no shipping/delivery available), the user does the following two things:
  • Either omit the entire ShippingDetails container, or pass in an empty ShippingDetails container - <ShippingDetails/>
  • Pass in one ShipToLocations field, with its value set to None - <ShipToLocations>None</ShipToLocations>
XML Representation Summary
<ns:ShipToLocations>
   
Content: 
{ xs:string }
</ns:ShipToLocations>
XML Source (w/o annotations (1); see within schema source)
<xs:element maxOccurs="unbounded" minOccurs="0" name="ShipToLocations" type="xs:string"/>

ns:Site
Type:
ns:SiteCodeType, simple content
The name of the eBay listing site. The listing site affects the business logic and validation rules that are applied to the request, which in turn affect the values that are returned in the response, as well as values that appear on the eBay site. For example, the listing site can affect the validation of Category in listing requests, international business seller requirements, the values of converted (localized) prices in responses, the item-related time stamps that are displayed on the eBay site, the visibility of the item in some types of searches (e.g., GetCategoryListings), and other information. In some cases, the rules are determined by a combination of the site, the user's registration address, and other information. You cannot change the site when you revise a listing.

When you specify Item.Site in AddItem or AddFixedPriceItem, it must be consistent with the numeric site ID that you specify in the request URL (for the SOAP API) or the X-EBAY-API-SITEID header (for the XML API).
XML Representation Summary
<ns:Site>
   
Content: 
{ enumeration of xs:token }
</ns:Site>
Simple Content
Enumeration:
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="Site" type="ns:SiteCodeType"/>

ns:SiteId
Type:
xs:int, predefined, simple content
The unique identifier of the eBay site on which the item is listed. If the Site ID is already passed in as an HTTP header, this field is not needed. If Site ID is specified in the HTTP header and through this request field, the value in this field will override the value in the HTTP headerWhen this is given we would ignore the site Id, which is given in header. See SiteCodeType for a full list of Site IDs for the eBay sites that are compatible with the Trading API.
XML Representation Summary
<ns:SiteId>
   
Content: 
{ xs:int }
</ns:SiteId>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="SiteId" type="xs:int"/>

ns:SKU
Type:
ns:SKUType, simple content
A SKU (Stock Keeping Unit) value is a seller-defined identifier for a product. Each product within a seller's inventory should be unique. Most large-volume sellers use SKUs, but eBay only requires a SKU value if the InventoryTrackingMethod field is included in an AddFixedPriceItem call and its value is set to SKU. Setting the InventoryTrackingMethod field to SKU allows the seller to use a SKU value instead of an ItemID value as a unique identifier in calls such as GetItem and ReviseInventoryStatus

A seller can specify a SKU when listing an item with AddItem and related calls. eBay preserves the SKU on the item, enabling you to obtain it before and after an order line item is created. (SKU is recommended as an alternative to ApplicationData.)

If both ItemID and SKU are specified in calls that support the use of SKU as a unique identifier, the ItemID value takes precedence.

If a seller wants to use SKUs for multiple-variation listings, the SKU value for each product variation is actually specified at the variation level (Item.Variations.Variation.SKU) field, and the Item.SKU) field should not be included in the call request.

Note: The eBay site cannot identify listings by SKU. For example, My eBay pages and Search pages all identify listings by item ID. When a buyer contacts you via eBay's messaging functionality, eBay uses the item ID as the identifier. Buyer-focused APIs (like the Shopping API) also do not support SKU as an identifier. For revising and relisting only: To remove a SKU when you revise or relist an item, use DeletedField. (You cannot remove a SKU when Item.InventoryTrackingMethod is set to SKU.)

For GetItem, GetMyeBaySelling, and other 'Get' call, the SKU value will only be returned if defined for the listing.
XML Representation Summary
<ns:SKU>
   
Content: 
{ xs:string }
</ns:SKU>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="SKU" type="ns:SKUType"/>

ns:StartPrice
Type:
ns:AmountType, simple content
The original price of the item at listing or re-listing time. If this value changes when the item is revised, the new value becomes the original price.

For auction listings: Competitive bidding starts at this value. Once at least one bid has been placed, StartPrice remains the same but CurrentPrice is incremented to the amount of each succeeding bid. If ReservePrice is also specified, the value of StartPrice must be lower than the value of ReservePrice.

For input on fixed-price listings (FixedPriceItem): This is the constant price at which a buyer may purchase the item.

GetMyeBaySelling does not return Item.StartPrice for fixed price items—it returns Item.SellingStatus.CurrentPrice.

For AddFixedPriceItem and VerifyAddFixedPriceItem: Required when no variations are specified. If variations are specified, use Variation.StartPrice for each variation instead.

For Revise calls: If the StartPrice value for a fixed-price item is changed with a Revise call, the MinimumBestOfferPrice and BestOfferAutoAcceptPrice fields in the ListingDetails container will be dropped (if set), basically turning off the Best Offer Auto Accept and/or Auto Decline features. If the seller wanted to reintroduce either of these Best Offer threshold values in the listing again, an additional Revise call would have to be made, passing in the desired threshold values.

Note: For the US site, new eBay sellers are subject to Seller Limits, which limit the quantity of items that may be listed and/or the total cumulative value of these listings. While subject to these selling limits, an eBay seller can use the GetMyeBaySelling call to retrieve both the remaining number of listings they can create and the remaining cumulative value of these listings. These values are shown in the Summary.QuantityLimitRemaining and Summary.AmountLimitRemaining fields in the GetMyeBaySelling response. If a call to add an item or revise an item would result in the exceeding of these limits, the add item or revise item call will fail. These fields will only be returned if the seller is subject to seller limits.
Component Diagram
XML Representation Summary
<ns:StartPrice
   
 = 
("AFA" | "ALL" | "DZD" | "ADP" | "AOA" | "ARS" | "AMD" | "AWG" | "AZM" | "BSD" | "BHD" | "BDT" | "BBD" | "BYR" | "BZD" | "BMD" | "BTN" | "INR" | "BOV" | "BOB" | "BAM" | "BWP" | "BRL" | "BND" | "BGL" | "BGN" | "BIF" | "KHR" | "CAD" | "CVE" | "KYD" | "XAF" | "CLF" | "CLP" | "CNY" | "COP" | "KMF" | "CDF" | "CRC" | "HRK" | "CUP" | "CYP" | "CZK" | "DKK" | "DJF" | "DOP" | "TPE" | "ECV" | "ECS" | "EGP" | "SVC" | "ERN" | "EEK" | "ETB" | "FKP" | "FJD" | "GMD" | "GEL" | "GHC" | "GIP" | "GTQ" | "GNF" | "GWP" | "GYD" | "HTG" | "HNL" | "HKD" | "HUF" | "ISK" | "IDR" | "IRR" | "IQD" | "ILS" | "JMD" | "JPY" | "JOD" | "KZT" | "KES" | "AUD" | "KPW" | "KRW" | "KWD" | "KGS" | "LAK" | "LVL" | "LBP" | "LSL" | "LRD" | "LYD" | "CHF" | "LTL" | "MOP" | "MKD" | "MGF" | "MWK" | "MYR" | "MVR" | "MTL" | "EUR" | "MRO" | "MUR" | "MXN" | "MXV" | "MDL" | "MNT" | "XCD" | "MZM" | "MMK" | "ZAR" | "NAD" | "NPR" | "ANG" | "XPF" | "NZD" | "NIO" | "NGN" | "NOK" | "OMR" | "PKR" | "PAB" | "PGK" | "PYG" | "PEN" | "PHP" | "PLN" | "USD" | "QAR" | "ROL" | "RUB" | "RUR" | "RWF" | "SHP" | "WST" | "STD" | "SAR" | "SCR" | "SLL" | "SGD" | "SKK" | "SIT" | "SBD" | "SOS" | "LKR" | "SDD" | "SRG" | "SZL" | "SEK" | "SYP" | "TWD" | "TJS" | "TZS" | "THB" | "XOF" | "TOP" | "TTD" | "TND" | "TRL" | "TMM" | "UGX" | "UAH" | "AED" | "GBP" | "USS" | "USN" | "UYU" | "UZS" | "VUV" | "VEB" | "VND" | "MAD" | "YER" | "YUM" | "ZMK" | "ZWD" | "ATS" | "CustomCode")
   
>
   
Content: 
{ xs:double }
</ns:StartPrice>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="StartPrice" type="ns:AmountType"/>

ns:Storefront
Type:
ns:StorefrontType, complex content
This container provides details about the seller's eBay store.

In an Add/Revise/Relist call, the seller can include this container to set/change which customized eBay store category that the item will be placed in.

For 'Get' calls, this container is returned if the seller of the item has an eBay store.
Component Diagram
XML Representation Summary
<ns:Storefront>
   
Content: 
</ns:Storefront>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="Storefront" type="ns:StorefrontType"/>

ns:SubTitle
Type:
xs:string, predefined, simple content
Subtitle to use in addition to the title. Provides more keywords when buyers search in titles and descriptions. You cannot use HTML in the Subtitle. (HTML characters will be interpreted literally as plain text.) If you pass any value, this feature is applied (with applicable fees).

When you revise a item, you can add, change, or remove the subtitle.
XML Representation Summary
<ns:SubTitle>
   
Content: 
{ xs:string }
</ns:SubTitle>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="SubTitle" type="xs:string"/>

ns:TaxCategory
Type:
xs:string, predefined, simple content
Tax exception category code. This is to be used only by sellers who have opted into sales tax being calculated by a sales tax calculation vendor. If you are interested in becoming a tax calculation vendor partner with eBay, contact developer-relations@ebay.com.
XML Representation Summary
<ns:TaxCategory>
   
Content: 
{ xs:string }
</ns:TaxCategory>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="TaxCategory" type="xs:string"/>

ns:TimeLeft
Type:
xs:duration, predefined, simple content
Time left before the listing ends. The duration is represented in the ISO 8601 duration format (PnYnMnDTnHnMnS). See Data Types in the Trading API Guide for information about this format. For ended listings, the time left is PT0S (zero seconds).
XML Representation Summary
<ns:TimeLeft>
   
Content: 
{ xs:duration }
</ns:TimeLeft>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="TimeLeft" type="xs:duration"/>

ns:Title
Type:
xs:string, predefined, simple content
This field is used to specify the title of the listing. This field is conditionally required in an Add call unless the seller successfully uses the ProductListingDetails container to find an eBay catalog product match. When the seller successfully uses an eBay catalog product to create a listing, the listing title, listing description, Item Specifics, and stock photo defined in the catalog product are used to create the listing.

You cannot use HTML or JavaScript in the Title. (HTML characters will be interpreted literally as plain text.)

The listing title can only be changed if the active listing has yet to have any bids or sales, and the listing does not end within 12 hours.
XML Representation Summary
<ns:Title>
   
Content: 
{ xs:string }
</ns:Title>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="Title" type="xs:string"/>

ns:TopRatedListing
Type:
xs:boolean, predefined, simple content
This boolean field is returned as true if the listing was created by a Top-Rated Seller and the listing has all of the requirements that qualifies it as a Top-Rated Plus listing. The Top-Rated Seller program is only available on the US, UK, and Germany sites. See the Top-Rated Seller requirements help topic for more information on qualifying as a Top-Rated Seller and the Top-Rated Plus listing requirements help topic for more information on what a listing must offer to qualify as a Top-Rated Plus listing and get the Top-Rated Plus badge. Information on the overall program can be found on the Top-Rated Seller home page in the Seller Center.
XML Representation Summary
<ns:TopRatedListing>
   
Content: 
{ xs:boolean }
</ns:TopRatedListing>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="TopRatedListing" type="xs:boolean"/>

ns:TotalQuestionCount
Type:
xs:long, predefined, simple content
The number of questions asked about this item. Applies to eBay Motors Pro applications only.
XML Representation Summary
<ns:TotalQuestionCount>
   
Content: 
{ xs:long }
</ns:TotalQuestionCount>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="TotalQuestionCount" type="xs:long"/>

ns:UnitInfo
Type:
ns:UnitInfoType, complex content
This container provides information about the weight, volume or other quantity measurement of a listed item. The European Union requires listings for certain types of products to include the price per unit so buyers can accurately compare prices. eBay uses the UnitType and UnitQuantity values and the item's listed price to calculate and display the per-unit price on eBay EU sites.

This container will only be returned if price per unit information exists for the listing, and the IncludeItemSpecifics field was included in the call request and set to true.
Component Diagram
XML Representation Summary
<ns:UnitInfo>
   
Content: 
</ns:UnitInfo>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="UnitInfo" type="ns:UnitInfoType"/>

ns:UpdateReturnPolicy
Type:
xs:boolean, predefined, simple content
Specifies whether the Return Policy Details have been updated for the item specified in the request.
XML Representation Summary
<ns:UpdateReturnPolicy>
   
Content: 
{ xs:boolean }
</ns:UpdateReturnPolicy>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="UpdateReturnPolicy" type="xs:boolean"/>

ns:UpdateSellerInfo
Type:
xs:boolean, predefined, simple content
Specifies whether the following Business Seller fields have been updated for the item specified in the request: First Name, Last Name, Fax, Email Address, Additional Contact Information, Trade Registration Number, VAT Identification Number.
XML Representation Summary
<ns:UpdateSellerInfo>
   
Content: 
{ xs:boolean }
</ns:UpdateSellerInfo>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="UpdateSellerInfo" type="xs:boolean"/>

ns:UseTaxTable
Type:
xs:boolean, predefined, simple content
Indicates whether the seller's tax table is to be used when applying and calculating sales tax for an order line item. A sales tax table can be created programmatically using the SetTaxTable call, or it can be created manually in My eBay's Payment Preferences. If UseTaxTable is set to true, the values contained in the seller's sales tax table will supersede the values contained in the Item.ShippingDetails.SalesTax container (if included in the request).

Note: As of September 1, 2020, buyers in over 40 US states will automatically be charged sales tax for eBay purchases. eBay will collect and remit this sales tax to the proper taxing authority on the buyer's behalf. The Sales Tax Table page for eBay US is being updated as each US state starts requiring collection of sales tax. This means that the seller no longer has control over, nor can specify a sales tax rate for these states. For a list of the US states that are currently subject to 'eBay Collect and Remit', or will become subject to 'eBay Collect and Remit', see the eBay sales tax collection help topic.
XML Representation Summary
<ns:UseTaxTable>
   
Content: 
{ xs:boolean }
</ns:UseTaxTable>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="UseTaxTable" type="xs:boolean"/>

ns:UUID
Type:
ns:UUIDType, simple content
Use an UUID value to ensure that you only list (or relist) a particular item once. This field can be particularly useful if you are listing many items on a daily basis and/or many items at once with an AddItems call. If your call request does not generate a response, or if you get one or more (blocking) errors, be sure to use the same UUID value when you attempt to list or relist the same item with another call request.

If you pass in a UUID value that has already been used to successfully create or relist an item, you will receive an error message that includes the Item ID for that listing and a boolean value indicating whether the duplicate UUID was sent by the same application.

We recommend that you use the Item.UUID field for add and relist calls (for example, AddItem and RelistItem), but use the Item.InvocationID field instead when using a revise call.

The UUID can only contain digits from 0-9 and letters from A-F and must be 32 characters long. The UUID value must be unique across all of the seller's eBay across all eBay marketplaces.
XML Representation Summary
<ns:UUID>
   
Content: 
{ xs:string }
</ns:UUID>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="UUID" type="ns:UUIDType"/>

ns:Variations
Type:
ns:VariationsType, complex content
Variations are multiple similar (but not identical) items in a single fixed-price listing. For example, a T-shirt listing could contain multiple items of the same brand that vary by color and size (like "Blue, Large" and "Black, Medium"). Each variation specifies a combination of one of these colors and sizes. Each variation can have a different quantity and price. You can buy multiple items from one variation at the same time. (That is, one order line item can contain multiple items from a single variation.)

If you list in two categories, both categories must support listing with variations. See VariationsEnabled in GetCategoryFeatures to determine applicable categories.

For ReviseFixedPriceItem and RelistFixedPriceItem: Once a listing has been submitted with variations, you can't delete all the variations when you revise or relist the listing (because it would be considered a different listing). You also can't add or change variation specifics (because they are unique identifiers). However, you can delete or replace individual variations as needed to match your current inventory. If a variation has no purchases, use the Variation.Delete field to delete the variation. If it has inventory, set the Quantity to 0.

As a best practice, if you want to revise multiple variations in the same listing at the same time (i.e., within a very short period), use a single ReviseFixedPriceItem request and include all the variation revisions in the same request. If your application design requires you to revise each variation individually, then avoid using multiple parallel threads. Instead, use a serial, synchronous process. That is, wait until each revision has been processed by eBay before submitting the next revision request for another variation in the same listing.

For GetItem and related calls Only returned when a listing has variations.

For GetSellerList: Only returned when a listing has variations, IncludeVariations was set to true in the request, the DetailLevel was set to ReturnAll, and an applicable pagination value and time range were specified.

For GetItemTransactions Only returned in Item when a listing has variations and IncludeVariations was set to true in the request. (Also see Variation returned in Transaction for information about which variation was actually purchased.)

For GetSellerEvents, GetMyeBayBuying, and GetMyeBaySelling: Only returned when a listing has variations and HideVariations was set to false or not specified in the request.
Component Diagram
XML Representation Summary
<ns:Variations>
   
Content: 
</ns:Variations>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="Variations" type="ns:VariationsType"/>

ns:VATDetails
Type:
ns:VATDetailsType, complex content
This container is used in an Add/Revise/Relist call to set the VAT (Value-added Tax) percentage rate that will be charged to buyers when an item is purchased from the listing, and to enable Business Seller-related features.

This container is returned in 'Get' calls only if VAT is applicable to the listing, and unless the person making the 'Get' call owns the listing, only the VATPercent field is returned (if applicable). However, Business Seller-related information will be returned to all users in 'Get' calls under the SellerInfo and BusinessSellerDetails containers.

Note: VAT is not applicable to all countries, including the US. Allowed VAT percentage rates can vary by region/country, so sellers should be aware of the rates they are legally required/allowed to charge. Sellers must be registered as Business Sellers on the site they are selling on in order to use the Business Seller-related fields.
Component Diagram
XML Representation Summary
<ns:VATDetails>
   
Content: 
</ns:VATDetails>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="VATDetails" type="ns:VATDetailsType"/>

ns:VideoDetails
Type:
ns:VideoDetailsType, complex content
This container is used if the seller wants to add a video to their listing. At this time, only one video can be added per listing, and the video must be uploaded to eBay via the Media API. See the Media API reference documentation for all of the necessary details to upload videos to eBay.

This container will only be returned in GetItem if the listing contains a video, and the seller of the item is the one making the GetItem call.

Note: Videos can only be attached to listings on supported eBay marketplaces and can only be viewed through supported platforms. See Managing videos in the Selling Integration Guide for a full list of supported marketplaces and platforms.
Component Diagram
XML Representation Summary
<ns:VideoDetails>
   
Content: 
</ns:VideoDetails>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="VideoDetails" type="ns:VideoDetailsType"/>

ns:VIN
Type:
xs:string, predefined, simple content
This field displays the Vehicle Identification Number, which is a unique serial number for a motor vehicle.

This field is applicable to listings in US eBay Motors Cars and Trucks (6001), Motorcycles (6024), Commercial Trucks (63732), RVs and Campers (50054), ATVs (6723), Snowmobiles (42595), and UTVs (173665); and to Cars and Trucks listings in CA, CAFR and AU eBay Motors. For vehicle categories that do not use VIN, call GetCategorySpecifics to determine applicable Item Specifics (such as 'Hull ID Number' for Boats).

For the US, CA, and CAFR eBay Motors sites, required for cars and trucks from model year 1981 and later. (The US developed national standards for VIN values in 1981.)

For the eBay Australia site, required for vehicles from model year 1989 or later. For the eBay Australia site, only appears on the View Item page if you also specify the date of first registration in the listing's Item Specifics.

Appears in the VIN field in the Item Specifics section of eBay's View Item page.
XML Representation Summary
<ns:VIN>
   
Content: 
{ xs:string }
</ns:VIN>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="VIN" type="xs:string"/>

ns:VINLink
Type:
xs:string, predefined, simple content
This field is deprecated.
XML Representation Summary
<ns:VINLink>
   
Content: 
{ xs:string }
</ns:VINLink>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="VINLink" type="xs:string"/>

ns:VRM
Type:
xs:string, predefined, simple content
Vehicle Registration Mark, which is a unique identifier for a motor vehicle in the UK.

Applicable to listings in UK eBay Motors Cars and Trucks, Motorcycle, and some Powersport categories.

Appears as a VRM field in the Item Specifics section of eBay's View Item page. On the View Item page, the VRM value is masked (i.e., only a portion of the value is shown to users). In the GetItem response, the VRM is only returned if the call is made by the seller (i.e., the AuthToken is associated with the vehicle's seller).
XML Representation Summary
<ns:VRM>
   
Content: 
{ xs:string }
</ns:VRM>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="VRM" type="xs:string"/>

ns:VRMLink
Type:
xs:string, predefined, simple content
This field is deprecated.
XML Representation Summary
<ns:VRMLink>
   
Content: 
{ xs:string }
</ns:VRMLink>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="VRMLink" type="xs:string"/>

ns:WatchCount
Type:
xs:long, predefined, simple content
The number of watches placed on this item from buyers' My eBay accounts. Specify IncludeWatchCount as true in the request. Returned by GetMyeBaySelling only if greater than 0.
XML Representation Summary
<ns:WatchCount>
   
Content: 
{ xs:long }
</ns:WatchCount>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="WatchCount" type="xs:long"/>

{any element from any namespace}
XML Source (see within schema source)
<xs:any maxOccurs="unbounded" minOccurs="0" processContents="lax"/>

 Component 
SUMMARY: XML REP | DERIVED | USE
DETAIL: DESC | XML SRC | TYPE | ATTR | CHILD
eBay Trading API

WSDL documentation generated with FlexDoc/XML 1.13 using FlexDoc/XML WSDLDoc 1.2.5 template set. All XSD diagrams generated by FlexDoc/XML DiagramKit.