ActiveInventoryReport
Note: You must wrap the file to be uploaded within BulkDataExchangeRequest tags, which will also be returned in the response. This container is not shown in the standard Output section for this call, but is shown in the Samples. For additional information, see XML data files overview in the LMS Feed API Guide. A report that contains price and quantity information for all of the active listings for a specific seller. A seller can use this information to maintain their inventory on eBay.
The eBay servers read the token information passed in by the seller's application to determine which seller's data to retrieve.
Output
See also Samples.
The box below lists all fields that might be returned in the response. To learn more about an individual field or its type, click its name in the box (or scroll down to find it in the table below the box).
<?xml version="1.0" encoding="utf-8"?> <ActiveInventoryReport xmlns="urn:ebay:apis:eBLBaseComponents"> <!-- Call-specific Output Fields --> <SKUDetails> SKUDetailsType <BidCount> int </BidCount> <ItemID> ItemIDType (string) </ItemID> <Price currencyID="CurrencyCodeType"> AmountType (double) </Price> <Quantity> int </Quantity> <ReserveMet> boolean </ReserveMet> <SKU> SKUType (string) </SKU> <Variations> MerchantDataVariationsType <Variation> MerchantDataVariationType <Price currencyID="CurrencyCodeType"> AmountType (double) </Price> <Quantity> int </Quantity> <SKU> SKUType (string) </SKU> <VariationSpecifics> NameValueListArrayType <NameValueList> NameValueListType <Name> string </Name> <Value> string </Value> <!-- ... more Value values allowed here ... --> </NameValueList> <!-- ... more NameValueList nodes allowed here ... --> </VariationSpecifics> </Variation> <!-- ... more Variation nodes allowed here ... --> </Variations> </SKUDetails> <!-- ... more SKUDetails nodes allowed here ... --> <!-- Standard Output Fields --> <Ack> AckCodeType </Ack> <Build> string </Build> <CorrelationID> string </CorrelationID> <Errors> ErrorType <ErrorClassification> ErrorClassificationCodeType </ErrorClassification> <ErrorCode> token </ErrorCode> <ErrorParameters ParamID="string"> ErrorParameterType <Value> string </Value> </ErrorParameters> <!-- ... more ErrorParameters nodes allowed here ... --> <LongMessage> string </LongMessage> <SeverityCode> SeverityCodeType </SeverityCode> <ShortMessage> string </ShortMessage> </Errors> <!-- ... more Errors nodes allowed here ... --> <HardExpirationWarning> string </HardExpirationWarning> <Timestamp> dateTime </Timestamp> <Version> string </Version> </ActiveInventoryReport>
| Return Value | Type | Occurrence | Meaning |
|---|
repeatable: [1..*] Describes or includes keywords associated with the SKU.
See activeInventoryReportFilter
You can revise this value using ReviseFixedPriceItem or ReviseInventoryStatus in the Trading API.
[ attribute currencyID ] CurrencyCodeType Always The price that the seller assigns to the item. If this value changes when the item is revised, the new value becomes the price. For a multi-variation listing, price is only returned at the variation level.
You can revise this value using ReviseFixedPriceItem or ReviseInventoryStatus in the Trading API.
For a list of possible enumeration values, see CurrencyCodeType.
You can revise this value using ReviseFixedPriceItem or ReviseInventoryStatus in the Trading API.
See activeInventoryReportFilter
You can include a SKU when you list any item, and then use the SKU instead of (or in addition to) using the ItemID to track your inventory on eBay.
For fixed-price items, if you set Item.InventoryTrackingmethod to SKU, you can use the SKU instead of ItemID as a unique ID when you revise the listing.
Only returned when the listing included a SKU.
Max length: 70.
.Variation MerchantDataVariationType Conditionally,
repeatable: [0..*] Contains data that distinguishes one variation from another. For example, if the items vary by color and size, each Variation node specifies a combination of one of those colors and sizes. Always returned when variations are present.
.Variation.Price AmountType (double) Conditionally The fixed price of all items identified by this variation. For example, a "Blue, Large" variation price could be USD 10.00, and a "Black, Medium" variation price could be USD 5.00.
.Variation.Price
[ attribute currencyID ] CurrencyCodeType Always The fixed price of all items identified by this variation. For example, a "Blue, Large" variation price could be USD 10.00, and a "Black, Medium" variation price could be USD 5.00.
For a list of possible enumeration values, see CurrencyCodeType.
.Variation.Quantity int Always For ActiveInventoryReport: The number of items available for sale that are associated with this variation.
.Variation.SKU SKUType (string) Conditionally Stock Keeping Unit that serves as the seller's unique identifier for items within the same variation. You can use the variation's SKU instead of the variation specifics to revise a variation and to keep track of your eBay inventory.
Many merchants assign a SKU to an item of a specific type, size, and color. This way, they can keep track of how many products of each type, size, and color are selling, and they can re-stock their shelves or update the variation quantity on eBay according to customer demand.
Only returned if the seller specified a SKU for the variation.
.Variation.VariationSpecifics NameValueListArrayType Conditionally A list of name/value pairs that uniquely identify the variation within the listing. All variations specify the same set of names, and each variation provides a unique combination of values for those names. For example, if the items vary by color and size, then every variation specifies Color and Size as names, and no two variations specify the same combination of color and size values.
If a variation has no SKU, use the variation specifics as a unique ID to revise the variation and to keep track of your eBay inventory.
.Variation.VariationSpecifics
.NameValueList NameValueListType Conditionally,
repeatable: [0..*] For the AddItem family of calls: Contains the name and value(s) for an Item Specific. Only required when the ItemSpecifics container is specified.
Note: The maximum number of item specifics that may be defined for a listing has increased from 30 to 45.
For the AddFixedPriceItem family of calls: The same NameValueList schema is used for the ItemSpecifics node, the VariationSpecifics node, and the VariationSpecifcsSet node.
If the listing has variations, any name that you use in the VariationSpecifics and VariationSpecificsSet nodes can't be used in the ItemSpecifics node.
When you list with Item Variations:
- Specify shared Item Specifics (e.g., Brand) in the ItemSpecifics node.
- Specify up to five VariationSpecifics in each Variation node.
- Specify all applicable names with all their supported values in the VariationSpecificSet node.
For PlaceOffer: Required if the item being purchased includes Item Variations.
For AddToWatchList and RemoveFromWatchList: The ItemID value of the multiple-variation listing and the name-value pair to identify each variation in the listing are required.
Note: As of August 30, 2018, California will require sellers to display a Proposition 65 warning on online retail sites if products contain chemicals and/or substances that may impact the health of California buyers. This requirement is applicable to most eBay US categories, including eBay Motors, Motors Parts & Accessories, and catalog-enabled categories. The warning message can be customized by the seller, but should contain the following basic information:
- The name of at least one listed chemical that prompted the warning
- Text stating that the product 'can expose you to' the chemical(s) in the product
- The URL for OEHHA's new Proposition 65 warnings website, which is www.P65Warnings.ca.gov
.Variation.VariationSpecifics
.NameValueList.Name string Conditionally Depending on the call and context, this value is either a name of an Item/Variation Specific, or a Parts Compatibility name.
For the AddItem and AddFixedPriceItem families of calls: In the Item.ItemSpecifics context, the value in this field will either be the name of a required/recommended/optional item specific name for the category, or it may be a seller's customized item specific name.
For the AddFixedPriceItem family of calls: In the Compatibility.NameValueList context, this value is a motor vehicle aspect such as Year, Make, and Model. A Compatibility.NameValueList container is applicable for motor vehicle parts and accessories listings.
For PlaceOffer: Required if the line item being purchased is an item variation within a multiple-variation listing.
Note: For required and recommended item specifics that are returned in the getItemAspectsForCategory method of the Taxonomy API, the seller should pass in the name of these item specifics just as they are shown in the getItemAspectsForCategory response. Similarly, for catalog-enabled categories, the seller should pass in the name of instance aspects just as they are shown in the getItemAspectsForCategory response. Instance aspects are additional details unique to a specific item or listing that a seller can include along with the product aspects that are already defined in the eBay catalog product associated with the listing. Instance aspects common to many catalog-enabled categories include 'Bundle Description' and 'Modification Description'. eBay US sellers who ship to California are required to pass in a 'California Prop 65 Warning' item specific if the item in the listing contains one or more chemicals known to be harmful to human health. This item specific is passed at the listing level for both single-variation and multiple-variation listings. The 'California Prop 65 Warning' is considered an instance specific because it will be retained on the listing even when the seller lists using an eBay catalog product. The 'California Prop 65 Warning' may be applicable in most eBay US categories, including eBay Motors, Motors Parts & Accessories, and catalog-enabled categories. Note: If Brand and MPN (Manufacturer Part Number) are being used to identify product variations in a multiple-variation listing, the Brand must be specified at the item level (ItemSpecifics container) and the MPN for each product variation must be specified at the variation level (VariationSpecifics container). The Brand name must be the same for all variations within a single listing.
Max length: 65.
.Variation.VariationSpecifics
.NameValueList.Value string Conditionally,
repeatable: [0..*] Depending on the call and context, this value is either the value of an Item/Variation Specific, a Parts Compatibility value, or a product identifier.
For the AddItem family of calls: Multiple values can only be specified for an Item Specific if the itemToAspectCardinality field of the getItemAspectsForCategory method shows a value of
MULTI. If an item specific only supports a single value, only the first item specific value specified in the request will be used. For the Compatibility.NameValueList context, this is the corresponding value of a motor vehicle aspect such as Year, Make, and Model. A Compatibility.NameValueList container is applicable for motor vehicle parts and accessories listings.
For PlaceOffer: Required if the line item being purchased is an item variation within a multiple-variation listing.
Note: The standard maximum length for the value of an item specific is 65, but the maximum allowed length increases for instance aspects such as 'Bundle Description' and 'Modification Description'. For item specifics with max lengths greater than 65, the actual max length will be returned in a corresponding aspectMaxLength field. The maximum allowed length for the new 'California Prop 65 Warning' item specific is 800 characters. For more information about the 'California Prop 65 Warning' item specific, see the ItemSpecifics.NameValueList field description.
Max length: 65 (but longer for some instance aspects, including 800 for 'California Prop 65 Warning').
Applicable values:
(Not all values in AckCodeType apply to this field.)
Code so that your app gracefully handles any future changes to this list.
Note: GetCategories is designed to retrieve very large sets of metadata that change once a day or less often. To improve performance, these calls return cached responses when you request all available data (with no filters). When this occurs, the MessageID and CorrelationID fields aren't applicable. However, if you specify an input filter to reduce the amount of data returned, the calls retrieve the latest data (not cached). When this occurs, MessageID and CorrelationID are applicable.
repeatable: [0..*] A list of application-level errors (if any) that occurred when eBay processed the request.
Applicable values:
Code so that your app gracefully handles any future changes to this list.
repeatable: [0..*] This optional element carries a list of context-specific error variables that indicate details about the error condition. These are useful when multiple instances of ErrorType are returned.
[ attribute ParamID ] string Conditionally This optional element carries a list of context-specific error variables that indicate details about the error condition. These are useful when multiple instances of ErrorType are returned.
Applicable values:
If the source of the problem is within the application (such as a missing required element), change the application before you retry the request.
- If the problem is due to end-user input data, please alert the end-user to the problem and provide the means for them to correct the data. Once the problem in the application or data is resolved, you can attempt to re-send the request to eBay.
- If the source of the problem is on eBay's side, An application can retry the request as-is a reasonable number of times (eBay recommends twice). If the error persists, contact Developer Technical Support. Once the problem has been resolved, the request may be resent in its original form.
See the Error handling section of the Making a Trading API call guide for more information.
When a warning occurs, the error is returned in addition to the business data. In this case, you do not need to retry the request (as the original request was successful). However, depending on the cause or nature of the warning, you might need to contact either the end user or eBay to effect a long term solution to the problem to prevent it from reoccurring in the future.
Code so that your app gracefully handles any future changes to this list.
Note: GetCategories and other Trading API calls are designed to retrieve very large sets of metadata that change once a day or less often. To improve performance, these calls return cached responses when you request all available data (with no filters). When this occurs, this time value reflects the time the cached response was created. Thus, this value is not necessarily when the request was processed. However, if you specify an input filter to reduce the amount of data returned, the calls retrieve the latest data (not cached). When this occurs, this time value does reflect when the request was processed.
Samples
Note: Some item IDs, user IDs, or other data in these samples might no longer be active on eBay. If necessary, you can substitute current eBay data in your requests.
Lists the active inventory for a specific seller ID (ID associated with the auth token). This sample represents a data file that you will download using the Bulk Data Exchange Service and File Transfer Service.
Description
User m****************t wants to see a list of her active inventory on the eBay site. She sends a Bulk Data Exchange startDownloadJob request with the ActiveInventoryReport parameter, uses a Bulk Data Exchange getJobStatus request to see if her report is ready to download, and then sends a File Transfer Service downloadJob request to retrieve the report data.
Input
Since a Large Merchant Services report returns a pre-determined set of elements, there is no input request for a report. Instead, the report type is specified as a parameter of a Bulk Data Exchange startDownloadJob call.
XML format.
Do not send a request file for reports. See description above.
Output
The response returns the SKU Details, which include: ItemID and/or SKU, Price, and Quantity.
If you need to change the price and quantity data that you see in this report, you can use the ReviseInventoryStatus call in eBay's Trading API, which lets you change the price and quantity of currently active fixed-price listings.
XML format.
<?xml version="1.0" encoding="utf-8"?>
<BulkDataExchangeResponses xmlns="urn:ebay:apis:eBLBaseComponents">
<ActiveInventoryReport>
<SKUDetails>
<SKU></SKU>
<Price currencyID="USD">50.00</Price>
<Quantity>6</Quantity>
<ItemID>1**********4</ItemID>
</SKUDetails>
<SKUDetails>
<SKU></SKU>
<Price currencyID="USD">50.00</Price>
<Quantity>6</Quantity>
<ItemID>1**********6</ItemID>
</SKUDetails>
<SKUDetails>
<SKU></SKU>
<Price currencyID="USD">50.00</Price>
<Quantity>5</Quantity>
<ItemID>1**********7</ItemID>
</SKUDetails>
<SKUDetails>
<SKU></SKU>
<Price currencyID="USD">50.00</Price>
<Quantity>1</Quantity>
<ItemID>1**********5</ItemID>
</SKUDetails>
<SKUDetails>
<SKU></SKU>
<Price currencyID="USD">50.00</Price>
<Quantity>4</Quantity>
<ItemID>1**********3</ItemID>
</SKUDetails>
<SKUDetails>
<SKU></SKU>
<Price currencyID="USD">65.00</Price>
<Quantity>5</Quantity>
<ItemID>1**********7</ItemID>
</SKUDetails>
<SKUDetails>
<SKU></SKU>
<Price currencyID="USD">5.00</Price>
<Quantity>11</Quantity>
<ItemID>1**********8</ItemID>
</SKUDetails>
<SKUDetails>
<SKU></SKU>
<Price currencyID="USD">50.00</Price>
<Quantity>6</Quantity>
<ItemID>1**********7</ItemID>
</SKUDetails>
<SKUDetails>
<SKU></SKU>
<Price currencyID="USD">55.00</Price>
<Quantity>4</Quantity>
<ItemID>1**********8</ItemID>
</SKUDetails>
<!-- Items just added with AddFixedPriceItem data file upload
(using AddFixedPriceItem sample) have a SoldReport with data
similar to this -->
<SKUDetails>
<SKU></SKU>
<Price currencyID="USD">40.00</Price>
<Quantity>6</Quantity>
<ItemID>1**********6</ItemID>
</SKUDetails>
<SKUDetails>
<SKU></SKU>
<Price currencyID="USD">55.00</Price>
<Quantity>4</Quantity>
<ItemID>1**********9</ItemID>
</SKUDetails>
</ActiveInventoryReport>
</BulkDataExchangeResponses>
Change History
| Change Date | Description |
|---|---|
| 657 2010年2月17日 |
|
| 589 2008年11月29日 |
|