GetItemRequestType
Returns item data (title, description, price information, seller information, and so on) for the specified item ID.
Fields
IncludeCrossPromotion ( boolean )
IncludeItemSpecifics ( boolean )
IncludeTaxTable ( boolean )
IncludeWatchCount ( boolean )
ItemID ( ItemIDType (string) )
SKU ( SKUType (string) )
TransactionID ( string )
VariationSKU ( SKUType (string) )
VariationSpecifics ( NameValueListArrayType )

IncludeCrossPromotion ( boolean ) [0..1]
Specifies whether or not to include cross-promotion information for the item in the call response.

With a request version of 485 or higher, the default is false (do not include cross-promotion details). Set to true to retrieve cross-promotion information for the item. Cross-promotion information is returned in Item.CrossPromotion.PromotedItem.PromotionDetails. A promoted item will now contain multiple PromotionDetails containers.

With a request version lower than 485, the default is true (include cross-promotions). Set the value to false if you do not want to retrieve cross-promotion information. Cross-promotion information, PromotedPrice and PromotedPriceType, are returned in Item.CrossPromotion.PromotedItem. If a promoted item has multiple PromotedPriceType and PromotedPrice value pairs, only the last pair is returned.
See the Field Index to learn which calls use IncludeCrossPromotion.

IncludeItemSpecifics ( boolean ) [0..1]
If true, the response returns the ItemSpecifics node (if the listing has custom Item Specifics).

Item Specifics are well-known aspects of items in a given category. For example, items in a washer and dryer category might have an aspect like Type=Top-Loading; whereas items in a jewelry category might have an aspect like Gemstone=Amber.

(This does not cause the response to include ID-based attributes. To also retrieve ID-based attributes, pass DetailLevel in the request with the value ItemReturnAttributes or ReturnAll.)
See the Field Index to learn which calls use IncludeItemSpecifics.

IncludeTaxTable ( boolean ) [0..1]
If true, an associated tax table is returned in the response. If no tax table is associated with the item, then no tax table is returned, even if IncludeTaxTable is set to true.
See the Field Index to learn which calls use IncludeTaxTable.

IncludeWatchCount ( boolean ) [0..1]
Indicates if the caller wants to include watch count for that item in the response. You must be the seller of the item to retrieve the watch count.
See the Field Index to learn which calls use IncludeWatchCount.

ItemID ( ItemIDType (string) ) [0..1]
Specifies the item ID that uniquely identifies the item listing for which to retrieve the data.

ItemID is a required input in most cases. SKU can be used instead in certain cases (see the description of SKU). If both ItemID and SKU are specified for items where the inventory tracking method is ItemID, ItemID takes precedence.
See the Field Index to learn which calls use ItemID.

SKU ( SKUType (string) ) [0..1]
Retrieves an item that was listed by the user identified in AuthToken and that is being tracked by this SKU.

A SKU (stock keeping unit) is an identifier defined by a seller. Some sellers use SKUs to track complex flows of products and information on the client side. eBay preserves the SKU on the item, enabling you to obtain it before and after a transaction is created. (SKU is recommended as an alternative to ApplicationData.)

In GetItem, SKU can only be used to retrieve one of your own items, where you listed the item by using AddFixedPriceItem or RelistFixedPriceItem, and you set Item.InventoryTrackingMethod to SKU at the time the item was listed. (These criteria are necessary to uniquely identify the listing by a SKU.)

Either ItemID or SKU is required in the request. If both are passed, they must refer to the same item, and that item must have InventoryTrackingMethod set to SKU.
See the Field Index to learn which calls use SKU.

TransactionID ( string ) [0..1]
Identifies a single transaction for a listing. A transaction begins when a winning bidder or buyer is determined, and ends when the buyer finishes the checkout process.

Since sellers can change active multiple-quantity fixed price listings, even after one of the items has been purchased, the transaction ID is associated with a snapshot of the item data at the time of the purchase. Specifying a TransactionID in the request enables developers to retrieve a snapshot of the listing as it was when the transaction was created.
See the Field Index to learn which calls use TransactionID.

VariationSKU ( SKUType (string) ) [0..1]
Variation-level SKU that uniquely identifes a Variation within the listing identified by ItemID. Only applicable when the seller listed the item with Variation-level SKU (Variation.SKU) values. Retrieves all the usual Item fields, but limits the Variations content to the specified Variation. If not specified, the response includes all Variations.
See the Field Index to learn which calls use VariationSKU.

VariationSpecifics ( NameValueListArrayType ) [0..1]
Name-value pairs that identify one or more Variations within the listing identified by ItemID. Only applicable when the seller listed the item with Variations. Retrieves all the usual Item fields, but limits the Variations content to the specified Variation(s). If the specified pairs do not match any Variation, eBay returns all Variations.

To retrieve only one variation, specify the full set of name/value pairs that match all the name-value pairs of one Variation.

To retrieve multiple variations (using a wildcard), specify one or more name/value pairs that partially match the desired variations. For example, if the listing contains Variations for shirts in different colors and sizes, specify Color as Red (and no other name/value pairs) to retrieve all the red shirts in all sizes (but no other colors).
See the Field Index to learn which calls use VariationSpecifics.

This document was generated with a customized version of the apireferencedocs tool.

© 2005–2009 eBay, Inc. All rights reserved. This documentation and the API may only be used in accordance with the eBay Developers Program and API License Agreement.