GunBroker.com has made many changes to the listing rules over the past 16 months.
These changes have been in effect on the web site for quite a while. GunBroker.com is now going to apply these rules to the SOAP API in September of 2011.
We have listed out the changes to our SOAP API below. Please have your software development department make any necessary changes to your code to avoid any listing issues.
Your software developers can make the changes as soon as they are ready. They do not have to wait until September to implement.
Contact GunBroker.com customer support if you have any questions.
| CHANGE 1: |
| | All items are required to state if it requires FFL or not. Developers will have to add the NEW tag below. If the new tag is not present, the item will NOT launch. |
| |
| | CODE: |
| | | METHODS: | AddItem,
CreateLaunchItem |
| OLD: | N/A |
| NEW: | <RequiresFFL>boolean</RequiresFFL> |
|
| CHANGE 2: |
| | All items are required to state if Sales Tax will be collected. “Unspecified” will no longer be an option. If the “Unspecified” option is present, the item will NOT launch. |
| |
| | CODE: |
| | | METHODS: | AddItem,
CreateLaunchItem |
| OLD: | <CollectSalesTax>Unspecified or Collected or Not_Collected</CollectSalesTax> |
| NEW: | <CollectSalesTax>Collected or Not_Collected</CollectSalesTax> |
|
| CHANGE 3: |
| | The tags, “SalesTaxRate” & “SalesTaxStates”, will no longer be supported. Any values in these tags will be ignored. Developers must use the new “SalesTaxStateTypes” array to pass sales tax information. The “State” tag only supports 2 character USPS state abbreviations. |
| |
| | CODE: |
| | | METHODS: | AddItem,
CreateLaunchItem |
| OLD: | <SalesTaxRate>decimal</SalesTaxRate> |
| NEW: | <SalesTaxRateTypes>
<SalesTaxStateType>
<State>string</state>
<TaxRate>decimal</TaxRate>
</SalesTaxStateType>
</SalesTaxRateTypes> |
|
| CHANGE 4: |
| | All items are required to state what kind of shipping classes are supported. Developers will have to add the NEW tag below. If the new tag is not present, the item will NOT launch. |
| |
| | CODE: |
| | | METHODS: | AddItem,
CreateLaunchItem |
| OLD: | N/A |
| NEW: | <ShippingClassesSupported>
<ShipperClassEnum>Overnight or Two_Day or Three_Day or Ground or First_Class or Priority </ShipperClassEnum>
</ShippingClassesSupported> |
|
| CHANGE 5: |
| | The tag, “ShippingFixedCost”, will no longer be supported. Any values in this tag will be ignored. Users must use the new “ShippingCosts” array to pass fixed cost. |
| |
| | CODE: |
| | | METHODS: | AddItem,
CreateLaunchItem |
| OLD: | <ShippingFixedCost>decimal</ShippingFixedCost> |
| NEW: | <ShippingCosts>
<ShipperCostType>
<ShipperClass>Overnight or Two_Day or Three_Day or Ground or First_Class or Priority</ShipperClass>
<FixedCost>decimal</FixedCost>
</ShipperCostType>
</ShippingCosts> |
|
| CHANGE 6: |
| | All items with a quantity greater than 1 must have the “FixedPrice” tag set tag set to a value greater than zero. If the “FixedPrice” tag is used for either a single or multiple quantity, values in the “StartBid”, “ReservePrice” and “BuyNowPrice” will be ignored. The “ListingDuration” tag for Fixed Price listings can only contain the values of ‘Thirty_Day’, ‘Sixty_Day’ or ‘Ninety_Day’. |
| |
| | CODE: |
| | | METHODS: | AddItem,
CreateLaunchItem |
| OLD: | <ListingDuration>Unspecified or One_Day or Three_Day or Five_Day or Seven_Day or Ten_Day or Fourteen_Day</ListingDuration> |
| NEW: | <FixedPrice>decimal</FixedPrice>
<ListingDuration>Unspecified or One_Day or Three_Day or Five_Day or Seven_Day or Ten_Day or Fourteen_Day or Thirty_Day or Sixty_Day or Ninety_Day</ListingDuration> |
|
| CHANGE 7: |
| | Dutch auction will not longer be supported. Items with quantity greater than one will have to have the "FixedPrice" field populated. |
| |
| | CODE: |
| | | METHODS: | AddItem,
CreateLaunchItem |
| OLD: | N/A |
| NEW: | <FixedPrice>decimal</FixedPrice>
|
|
| CHANGE 8: |
| | All SOAP API calls will not require username and password tags. For security reasons, any values passed in these tags will be ignored and should not be sent. The assigned ‘AppKey’ and ‘DevKey’ values will be used as authentication into the SOAP API. |
| |
| | CODE: |
| | | METHODS: | AddItem,
AddItemCommit,
AddToDescription,
CreateLaunchItem,
EndItem,
GenerateUserSubKey,
GetChilderen,
GetFeedback,
GetGunBrokerFeeSchedule,
GetItem,
GetItemHistory,
GetMyAuctions,
GetSearchResults,
GetUser,
ItemFees,
LeaveFeedback,
Login,
RelistItem
|
