AddItemFromSellingManagerTemplate

Note: AddItemFromSellingManagerTemplate and all Selling Manager Pro calls are being deprecated. Selling Manager Pro calls will start being decommissioned beginning on June 1, 2021.

Creates a listing from a Selling Manager template. A Selling Manager template contains the data needed to list an item. To use this call, you must be a Selling Manager Pro subscriber and have at least one Selling Manager template.

See:
Using Selling Manager Calls in the Trading API
Selling Manager Pro page on the eBay Site

See also the reference documentation for these calls:

AddSellingManagerTemplate - Creates a Selling Manager listing template that can be used to create an eBay listing based on the Selling Manager product associated with the template.
GetSellingManagerTemplates - Retrieves Selling Manager templates.

Input

See also Samples.

The box below lists all fields that could be included in the call request. 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).

See also the Deprecated Objects link above. Fields presented in this color are deprecated, and fields presented in this color are (or soon will be) non-operational.

The XML prototype does not include requester credentials. This is a documentation limitation only (see Standard Requester Credentials for Making Calls).

<?xml version="1.0" encoding="utf-8"?>
<AddItemFromSellingManagerTemplateRequest xmlns="urn:ebay:apis:eBLBaseComponents">
  <!-- Call-specific Input Fields -->
  <Item> ItemType
    <CategoryMappingAllowed> boolean </CategoryMappingAllowed>
    <PaymentMethods> BuyerPaymentMethodCodeType </PaymentMethods>
    <!-- ... more PaymentMethods values allowed here ... -->
    <PayPalEmailAddress> string </PayPalEmailAddress>
  </Item>
  <SaleTemplateID> long </SaleTemplateID>
  <ScheduleTime> dateTime </ScheduleTime>
  <!-- Standard Input Fields -->
  <ErrorLanguage> string </ErrorLanguage>
  <MessageID> string </MessageID>
  <Version> string </Version>
  <WarningLevel> WarningLevelCodeType </WarningLevel>
</AddItemFromSellingManagerTemplateRequest>

Argument	Type	Occurrence	Meaning

Call-specific Input Fields [Jump to standard fields]

Item	ItemType	Optional	This container is intended for specifying setting in the listing that differ from values in the Selling Manager template being used. Note: Only the following three values of ItemType may be used for a AddItemFromSellingManagerTemplate call: CategoryMappingAllowed, PaymentMethods, and PayPalEmailAddress.
Item.CategoryMappingAllowed	boolean	Optional	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. Default: true. See Maintaining Category Data.
Item.PaymentMethods	BuyerPaymentMethodCodeType	Conditional, repeatable: [0..*]	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. Applicable values: See PaymentMethods.
Item.PayPalEmailAddress	string	Conditional	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. See (SetUserPreferences) SellerPaymentPreferences.
SaleTemplateID	long	Optional	The unique identifier of the Selling Manager template that a seller is using to create a listing. Unique identifiers of Selling Manager templates can be retrieved programatically by using the GetSellingManagerInventory call.
ScheduleTime	dateTime	Optional	This field allows the user to specify a time in the future when the listing being created becomes active. If this field is not used, the listing will become active immediately upon being created successfully. The time in this field should be specified in GMT format.

Standard Input Fields

ErrorLanguage

string

Optional

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. Below are some examples from different countries.

ID	Country
en_AU	Australia
de_AT	Austria
nl_BE	Belgium (Dutch)
fr_BE	Belgium (French)
en_CA	Canada
fr_CA	Canada (French)
zh_CN	China
fr_FR	France
de_DE	Germany
zh_HK	Hong Kong
en_IN	India
en_IE	Ireland
it_IT	Italy
nl_NL	Netherlands
en_SG	Singapore
es_ES	Spain
de_CH	Switzerland
en_GB	United Kingdom
en_US	United States

MessageID string Optional Most Trading API calls support a MessageID element in the request and a CorrelationID element in the response. If you pass in a MessageID in a request, the same value will be returned in the CorrelationID field in the response. Pairing these values can help you track and confirm that a response is returned for every request and to match specific responses to specific requests. If you do not pass a MessageID value in the request, CorrelationID is not returned.

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.

Version

string

Conditional

The version number of the API code that you are programming against (e.g., 1149). The version you specify for a call has these basic effects:

It indicates the version of the code lists and other data that eBay should use to process your request.
It indicates the schema version you are using.

You need to use a version that is greater than or equal to the lowest supported version.
For the SOAP API: If you are using the SOAP API, this field is required. Specify the version of the WSDL your application is using.

For the XML API: If you are using the XML API, this field has no effect. Instead, specify the version in the X-EBAY-API-COMPATIBILITY-LEVEL HTTP header. (If you specify Version in the body of an XML API request and it is different from the value in the HTTP header, eBay returns an informational warning that the value in the HTTP header was used instead.)

See:
    HTTP Headers
    eBay Schema Versioning Strategy
    Lowest Supported Version

WarningLevel

WarningLevelCodeType

Optional

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

An unrecognized element is one that is not defined in any supported version of the schema. Schema element names are case-sensitive, so using WarningLevel can also help you remove any potential hidden bugs within your application due to incorrect case or spelling in field names before you put your application into the Production environment.

WarningLevel only validates elements; it doesn't validate XML attributes. It also doesn't control warnings related to user-entered strings or numbers, or warnings for logical errors.

We recommend that you only use this during development and debugging. Do not use this in requests performed in the Production environment.

Applicable values:

High

(in) The WarningLevel value is set to High if the user wishes to receive warnings when the application passes unrecognized or deprecated elements in an API call request. Setting the WarningLevel value to High is not recommended in a production environment. Instead, it should only be used during the development/debugging stage.

Low

(in) The WarningLevel value is set to Low if the user does not wish to receive warnings when the application passes unrecognized or deprecated elements in an API call request. This is the default value if WarningLevel is not specified in the call request.

See Warning Level.

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).

See also the Deprecated Objects link above. Fields presented in this color are deprecated, and fields presented in this color are not returned (or soon will not be returned) or are not operational (or soon will be non-operational).

<?xml version="1.0" encoding="utf-8"?>
<AddItemFromSellingManagerTemplateResponse xmlns="urn:ebay:apis:eBLBaseComponents">
  <!-- Call-specific Output Fields -->
  <Category2ID> string </Category2ID>
  <CategoryID> string </CategoryID>
  <EndTime> dateTime </EndTime>
  <Fees> FeesType
    <Fee> FeeType
      <Fee currencyID="CurrencyCodeType"> AmountType (double) </Fee>
      <Name> string </Name>
      <PromotionalDiscount currencyID="CurrencyCodeType"> AmountType (double) </PromotionalDiscount>
    </Fee>
    <!-- ... more Fee nodes allowed here ... -->
  </Fees>
  <ItemID> ItemIDType (string) </ItemID>
  <StartTime> dateTime </StartTime>
  <!-- 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>
</AddItemFromSellingManagerTemplateResponse>

Return Value	Type	Occurrence	Meaning

Call-specific Output Fields [Jump to standard fields]

Category2ID	string	Conditionally	Unique identifier of the secondary category in which the item was listed. This field is only returned if the Item.CategoryMappingAllowed boolean field is set to `true` in the request (or omitted) and the Category ID passed in as the secondary listing category was automatically mapped to a new Category ID by eBay. If the secondary category ID passed in the request is still active/valid, this field is not returned. Note: The Item.CategoryMappingAllowed field value in the request now defaults to `true` if 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. Max length: 10.
CategoryID	string	Conditionally	The unique identifier of the primary category in which the item was listed. This field is only returned if the Item.CategoryMappingAllowed boolean field is set to `true` in the request (or omitted) and the Category ID passed in as the primary listing category was automatically mapped to a new Category ID by eBay. If the primary category ID passed in the request is still active/valid, this field is not returned. Note: The Item.CategoryMappingAllowed field value in the request now defaults to `true` if 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. Max length: 10.
EndTime	dateTime	Always	Date and time when the new listing is scheduled to end based on the start time and the listing duration value that was set in the ListingDuration field at listing time. If the value of ListingDuration was set to `GTC` (Good 'Til Cancelled) this value will be set one month ahead of the start time, and this value will continue to be updated one month ahead each time the GTC listing needs to be renewed. Fixed-price listings get renewed automatically as long as there is still a quantity of `1` or above, or even if the quantity is `0`, but the 'out-of-stock control' feature is enabled. Note that `GTC` is not a supported listing duration for auction listings, but is the only supported listing duration for fixed-price listings except for a few motor vehicle categories on eBay Motors US, eBay UK, and eBay Italy. Note: As of July 1, 2019, the Good 'Til Cancelled renewal schedule has been modified from every 30 days to once per calendar month. For example, if a GTC listing is created July 5, the next monthly renewal date will be August 5. If a GTC listing is created on the 31st of the month, but the following month only has 30 days, the renewal will happen on the 30th in the following month. Finally, if a GTC listing is created on January 29-31, the renewal will happen on February 28th (or 29th during a 'Leap Year'). See the Good 'Til Cancelled listings update in the Spring 2019 Seller Updates for more information about this change.
Fees	FeesType	Always	This container is an array of fees associated with the creation of the listing. The fees in this container will not include any fees that are based on the purchase price (such as Final Value Fee) and only come into play when the listing has a sale. Note: The currency used for all fees returned under the Fees container reflects the currency used for the listing site, and not necessarily in the seller's default/home currency. For example, if a Canadian seller is using the AddItemFromSellingManagerTemplate call to list an item on the eBay US site, the currency type shown for each fee will be `USD` and not `CAD`. See: eBay.com Selling Fees Fees Per Site
Fees.Fee	FeeType	Conditionally, repeatable: [0..*]	A Fee container is returned for each listing fee associated with listing an item. Each Fee container consists of the fee type, the amount of the fee, and any applicable eBay promotional discount on that listing fee. A Fee container is returned for each listing feature, even if the associated cost is 0.
Fees.Fee.Fee	AmountType (double)	Conditionally	Amount of the fee that eBay will charge the member for the associated listing feature. See: eBay.com Fees for A current schedule of listing features and their associated fees. Fees Resulting from Listing an Item for A table listing the type of fees that can be charged when you list an item.
Fees.Fee.Fee [ attribute currencyID ]	CurrencyCodeType	Always	Amount of the fee that eBay will charge the member for the associated listing feature. For a list of possible enumeration values, see CurrencyCodeType.
Fees.Fee.Name	string	Conditionally	This is the name of the listing feature, such as `ListingFee`, `SubtitleFee`, or `BoldFee`. See Fees Resulting from Listing an Item.
Fees.Fee.PromotionalDiscount	AmountType (double)	Conditionally	This field exists in the response when the user has selected a feature that participates in a promotional discount. Note: Verify calls might not return the PromotionalDiscount fee in the response. See Standard selling fees for A current schedule of listing features and their associated fees..
Fees.Fee.PromotionalDiscount [ attribute currencyID ]	CurrencyCodeType	Always	This field exists in the response when the user has selected a feature that participates in a promotional discount. Note: Verify calls might not return the PromotionalDiscount fee in the response. For a list of possible enumeration values, see CurrencyCodeType.
ItemID	ItemIDType (string)	Always	Unique identifier for the new listing. This field is returned as long as the listing was successfully created.
StartTime	dateTime	Always	Starting date and time for the new listing. This value is based on the time the listing was received and processed, or the time the item will be listed if the seller included the ScheduleTime field in the request and set a custom start time of the listing (in the future).

Standard Output Fields

Ack	AckCodeType	Always	A token representing the application-level acknowledgement code that indicates the response status (e.g., success). The AckCodeType list specifies the possible values for the Ack field. Applicable values: CustomCode (out) Reserved for internal or future use. Failure (out) This value indicates that the call request processing failed. Success (out) This value indicates that the call request was processed successfully without any issues. Warning (out) This value indicates that the call request was successful, but processing was not without any issues. These issues can be checked in the Errors container, that will also be returned when one or more known issues occur with the call request. (Not all values in AckCodeType apply to this field.) Code so that your app gracefully handles any future changes to this list.
Build	string	Always	This refers to the specific software build that eBay used when processing the request and generating the response. This includes the version number plus additional information. eBay Developer Support may request the build information when helping you resolve technical issues.
CorrelationID	string	Conditionally	Most Trading API calls support a MessageID element in the request and a CorrelationID element in the response. If you pass in a MessageID in a request, the same value will be returned in the CorrelationID field in the response. Pairing these values can help you track and confirm that a response is returned for every request and to match specific responses to specific requests. If you do not pass a MessageID value in the request, CorrelationID is not returned. 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.
Errors	ErrorType	Conditionally, repeatable: [0..*]	A list of application-level errors (if any) that occurred when eBay processed the request.
Errors.ErrorClassification	ErrorClassificationCodeType	Conditionally	API errors are divided between two classes: system errors and request errors. Applicable values: CustomCode (out) Reserved for internal or future use. RequestError (out) An error has occurred either as a result of a problem in the sending application or because the application's end-user has attempted to submit invalid data (or missing data). In these cases, do not retry the request. The problem must be corrected before the request can be made again. If the problem is due to something in the application (such as a missing required field), the application must be changed. If the problem is a result of end-user data, the application must alert the end-user to the problem and provide the means for the end-user to correct the data. Once the problem in the application or data is resolved, resend the request to eBay with the corrected data. SystemError (out) Indicates that an error has occurred on the eBay system side, such as a database or server down. 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. Code so that your app gracefully handles any future changes to this list.
Errors.ErrorCode	token	Conditionally	A unique code that identifies the particular error condition that occurred. Your application can use error codes as identifiers in your customized error-handling algorithms. See the "Errors by Number" document.
Errors.ErrorParameters	ErrorParameterType	Conditionally, 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.
Errors.ErrorParameters [ 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.
Errors.ErrorParameters.Value	string	Conditionally	This is the value of the request parameter noted in the ParamID attribute. So, if the ParamID value was ItemID, the value in this field would be the actual value of that ItemID.
Errors.LongMessage	string	Conditionally	A more detailed description of the condition that raised the error.
Errors.SeverityCode	SeverityCodeType	Conditionally	Indicates whether the error is a severe error (causing the request to fail) or an informational error (a warning) that should be communicated to the user. Applicable values: CustomCode (out) Reserved for internal or future use. Error (out) The request that triggered the error was not processed successfully. When a serious application-level error occurs, the error is returned instead of the business data. 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 Compatible Application Check section of the eBay Features Guide for more information. Warning (out) The request was processed successfully, but something occurred that may affect your application or the user. For example, eBay may have changed a value the user sent in. In this case, eBay returns a normal, successful response and also returns the warning. 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.
Errors.ShortMessage	string	Conditionally	A brief description of the condition that raised the error.
HardExpirationWarning	string	Conditionally	Expiration date of the user's authentication token. Only returned within the 7-day period prior to a token's expiration. To ensure that user authentication tokens are secure and to help avoid a user's token being compromised, tokens have a limited life span. A token is only valid for a period of time (set by eBay). After this amount of time has passed, the token expires and must be replaced with a new token.
Timestamp	dateTime	Always	This value represents the date and time when eBay processed the request. The time zone of this value is GMT and the format is the ISO 8601 date and time format (YYYY-MM-DDTHH:MM:SS.SSSZ). See the Time Values section in the eBay Features Guide for information about this time format and converting to and from the GMT time zone. 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.
Version	string	Always	The version of the response payload schema. Indicates the version of the schema that eBay used to process the request. See the Standard Data for All Calls section in the eBay Features Guide for information on using the response version when troubleshooting CustomCode values that appear in the response.

Detail Controls

DetailLevel

This call does not support varying Detail Levels. You do not need to pass DetailLevel in the request.

Samples

New to making API calls? Please see Making a Call.

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.

Sample: Basic Call

Lists an item from a template in Selling Manager.

Description

User m***************r would like to list a new Harry Potter book. She provides a SaleTemplateID.

Input

The only required field in the AddItemFromSellingManagerTemplate request is SaleTemplateID.

XML format.

<?xml version="1.0" encoding="utf-8"?>
<AddItemFromSellingManagerTemplateRequest xmlns="urn:ebay:apis:eBLBaseComponents">
  <RequesterCredentials>
    <eBayAuthToken>A*******3</eBayAuthToken>
  </RequesterCredentials>
  <Version>1081</Version>
  <SaleTemplateID>6********3</SaleTemplateID>
</AddItemFromSellingManagerTemplateRequest>

Output

The response includes the ItemID and associated Fees with the listing. A start time and end time for the listing are also returned.

XML format.
<?xml version="1.0" encoding="utf-8"?>
<AddItemFromSellingManagerTemplateResponse xmlns="urn:ebay:apis:eBLBaseComponents">
  <Timestamp>2018-10-29T18:36:52.001Z</Timestamp>
  <Ack>Success</Ack>
  <Version>1081</Version>
  <Build>E1081_UNI_API5_18856241_R1</Build>
  <ItemID>1**********7</ItemID>
  <Fees>
    <Fee>
      <Name>AuctionLengthFee</Name>
      <Fee currencyID="USD">0.0</Fee>
    </Fee>
    <Fee>
      <Name>BoldFee</Name>
      <Fee currencyID="USD">0.0</Fee>
    </Fee>
    <Fee>
      <Name>BuyItNowFee</Name>
      <Fee currencyID="USD">0.0</Fee>
    </Fee>
    <Fee>
      <Name>CategoryFeaturedFee</Name>
      <Fee currencyID="USD">0.0</Fee>
    </Fee>
    <Fee>
      <Name>FeaturedFee</Name>
      <Fee currencyID="USD">0.0</Fee>
    </Fee>
    <Fee>
      <Name>GalleryPlusFee</Name>
      <Fee currencyID="USD">0.0</Fee>
    </Fee>
    <Fee>
      <Name>FeaturedGalleryFee</Name>
      <Fee currencyID="USD">0.0</Fee>
    </Fee>
    <Fee>
      <Name>FixedPriceDurationFee</Name>
      <Fee currencyID="USD">0.0</Fee>
    </Fee>
    <Fee>
      <Name>GalleryFee</Name>
      <Fee currencyID="USD">0.0</Fee>
    </Fee>
    <Fee>
      <Name>GiftIconFee</Name>
      <Fee currencyID="USD">0.0</Fee>
    </Fee>
    <Fee>
      <Name>HighLightFee</Name>
      <Fee currencyID="USD">0.0</Fee>
    </Fee>
    <Fee>
      <Name>InsertionFee</Name>
      <Fee currencyID="USD">0.35</Fee>
    </Fee>
    <Fee>
      <Name>InternationalInsertionFee</Name>
      <Fee currencyID="USD">0.0</Fee>
    </Fee>
    <Fee>
      <Name>ListingDesignerFee</Name>
      <Fee currencyID="USD">0.0</Fee>
    </Fee>
    <Fee>
      <Name>ListingFee</Name>
      <Fee currencyID="USD">0.35</Fee>
    </Fee>
    <Fee>
      <Name>PhotoDisplayFee</Name>
      <Fee currencyID="USD">0.0</Fee>
    </Fee>
    <Fee>
      <Name>PhotoFee</Name>
      <Fee currencyID="USD">0.0</Fee>
    </Fee>
    <Fee>
      <Name>ReserveFee</Name>
      <Fee currencyID="USD">0.0</Fee>
    </Fee>
    <Fee>
      <Name>SchedulingFee</Name>
      <Fee currencyID="USD">0.0</Fee>
    </Fee>
    <Fee>
      <Name>SubtitleFee</Name>
      <Fee currencyID="USD">0.0</Fee>
    </Fee>
    <Fee>
      <Name>BorderFee</Name>
      <Fee currencyID="USD">0.0</Fee>
    </Fee>
    <Fee>
      <Name>ProPackBundleFee</Name>
      <Fee currencyID="USD">0.0</Fee>
    </Fee>
    <Fee>
      <Name>BasicUpgradePackBundleFee</Name>
      <Fee currencyID="USD">0.0</Fee>
    </Fee>
    <Fee>
      <Name>ValuePackBundleFee</Name>
      <Fee currencyID="USD">0.0</Fee>
    </Fee>
    <Fee>
      <Name>PrivateListingFee</Name>
      <Fee currencyID="USD">0.0</Fee>
    </Fee>
    <Fee>
      <Name>ExtendedDurationFee</Name>
      <Fee currencyID="USD">0.0</Fee>
    </Fee>
    <Fee>
      <Name>ProPackPlusBundleFee</Name>
      <Fee currencyID="USD">0.0</Fee>
    </Fee>
    <Fee>
      <Name>MotorsGermanySearchFee</Name>
      <Fee currencyID="USD">0.0</Fee>
    </Fee>
  </Fees>
</AddItemFromSellingManagerTemplateResponse>

Change History

Change Date	Description
1189 2021-01-15	(deprecated) This call is being deprecated. It will no longer be supported after June 1, 2021.
1173 2020-09-25	Fees.Fee.Fee (modified): The currency of the listing fees returned under the Fees container will reflect the listing site's currency, and not necessarily the seller's default/home currency.
1107 2019-05-10	EndTime (modified): Starting July 1, 2019, the Good 'Til Cancelled renewal schedule will be modified from every 30 days to once per calendar month. For example, if a GTC listing is created July 5, the next monthly renewal date will be August 5. If a GTC listing is created on the 31st of the month, but the following month only has 30 days, the renewal will happen on the 30th in the following month. Finally, if a GTC listing is created on January 29-31, the renewal will happen on February 28th (or 29th during a 'Leap Year').
1091 2019-01-18	Item.CategoryMappingAllowed (modified): The default value of this boolean field has been changed from `false` to `true`. This means that this field can be omitted, and eBay will map outdated primary and secondary Category IDs to the updated Category IDs (where applicable).
1085 2018-10-26	Item.PaymentMethods (modified): For sellers enrolled in the new eBay Managed Payments program, a specified payment method is not necessary. If a payment method is specified, such as PayPal, it will be dropped from the listing and the seller will get a warning message when the call is run.
0945 2015-10-15	BuyerPaymentMethodCodeType (modified): Sellers can no longer specify Moneybookers, ProPay, or Paymate as values in a PaymentMethods field. If any of these values are used, the listing will be rejected.
0931 2015-07-10	NameValueList.Name (modified): The maximum length was increased to 65. NameValueList.Value (modified): The maximum length was increased to 65.
0899 2014-11-04	BuyerPaymentMethodCodeType (modified): 'QIWI' added as enumeration value. This payment method can only be specified on the US site and is only applicable to Russian buyers.
0851 2013-11-19	Item.ConditionDescription (modified): ConditionDescription is now supported on the following eBay sites: US and US Motors (0, 100), CA (2), CAFR (210), UK (3), AU (15), AT (16), BEFR (23), BENL (123) FR (71), DE (77), IT (101), NL (146), ES (186), CH (193), IE (205), PL (212).
0849 2013-11-05	Item.ConditionDescription (modified): In addition to the eBay US and US eBay Motors (0), UK (3), CA (2), CAFR (210) and AU (15) sites, ConditionDescription is now supported on the AT (16), FR (71), IT (101) and ES (186) sites. Item.PaymentMethods (modified): 'CreditCard' and 'DirectDebit' added as acceptable buyer payment methods. These two values should only be used for eBay Now-enabled listings. ShippingServiceOptions.ShippingService (modified): 'eBayNowImmediateDelivery' added as an acceptable value in the ShippingService field. This value should only be used for eBay Now-enabled listings.
0789 2012-08-29	Item.ConditionDescription (added): This string field is used by the seller to more clearly describe the condition of items that are not brand new.
0687 2010-09-15	ItemCompatibilityList (modified): Invalid item compatibility combinations will no longer cause the request to fail as long as ItemCompatibilityList contains at least one valid item compatibility.
0661 2010-03-17	ConditionID (added): ConditionID is supported in the Sandbox for a few categories. Starting in May 2010, it will be functional in production for most categories. Use ConditionID instead of AttributeSetArray or ItemSpecifics to specify the item's condition when GetCategoryFeatures shows ConditionEnabled=Enabled or Required for the listing's primary category.
0653 2010-01-20	Item.CompatibilityList (added): Specify a list of parts compatibility information specified as name and value pairs. Describes assemblies (e.g., year, make, model, trim, and engine values for specific vehicles) to which the part/item applies (i.e., compatibility by application).
0639 2009-10-14	ScheduleTime (modified): The start time for new, scheduled listings is now randomized within 15-minute intervals. With this change, it is possible that the scheduled start time of your listing will be delayed by up to 15 minutes. Listing end times are modified accordingly. This upgrade affects the following sites: `AT, BEFR, BENL, CH, DE, ES, FR, IE, IT, NL, PL, UK`
0635 2009-09-16	ExcludeShipToLocation (added): Sellers can now exclude specific regions and countries from where they will ship items.
0621 2009-06-10	(doc change) The schema input section was updated to indicate that only the following can be specified as children of the Item container: payment methods and the PayPal email address.
0589 2008-10-30	(added) New call.