Detail levels are instructions that define standard subsets of data to return for particular data components (e.g., each Item, Transaction, or User) within the response payload. »

Use ErrorLanguage to return error strings for the call in a different language from the language commonly associated with the site that the requesting user is registered with. »

Most Trading API calls support a MessageID element in the request and a CorrelationID element in the response. »

The version number of the API code that you are programming against (e.g., 1149). »

The public IP address of the machine from which the request is sent. »

Error tolerance level for the call. »

A unique identifier for a particular call. »

You can use the OutputSelector field to restrict the data returned by a call. »

Controls whether or not to return warnings when the application passes unrecognized or deprecated elements in a request. »

This container is only used by the PlaceOffer call request if the previous PlaceOffer call resulted in a BotBlock container in the response. »

The Item container is used to make changes to the active listing. The seller must pass in the ItemID value for the listing that is being revised. For anything else that the seller wishes to change, such as quantity or price, the seller should include this field in the call request and give it a new value.

If the seller wants to delete one or more optional settings in the listing, the seller should use the DeletedField tag.

Specifies the name of a field to delete from a listing. The request can contain zero, one, or many instances of DeletedField (one for each field to be deleted). See the relevant field descriptions to determine when to use DeletedField (and potential consequences).

You cannot delete required fields from a listing.

Some fields are optional when you first list an item (e.g., SecondaryCategory), but once they are set they cannot be deleted when you revise an item. Some optional fields cannot be deleted if the item has bids and/or ends within 12 hours. Some optional fields cannot be deleted if other fields depend on them.

Some data (such as Variation nodes within the Variations container) can't be deleted by using DeletedField. See the relevant field descriptions for how to delete such data.

Use values that match the case of the schema element names (Item.PictureDetails.PictureURL) or make the initial letter of each field name lowercase (item.pictureDetails.pictureURL). However, do not change the case of letters in the middle of a field name. For example, item.picturedetails.pictureUrl is not allowed.

To delete a listing enhancement like BoldTitle, specify the value you are deleting in square brackets ("[ ]"); for example, Item.ListingEnhancement[BoldTitle].