eBay Moves Developer Discussion Board, Old Posts Vaporized

eBay moved the discussion board for third-party developers who develop tools for eBay buyers and sellers (and for sellers who use eBay developer tools directly).

The new board is “exclusively for collaborating with your fellow developers using APIs,” eBay explained in a welcome post. “You will be able to start new conversations and answer questions in the appropriate topic thread.”

eBay created the following 14 sections where sellers can post questions and comments:

• Traditional APIs: Orders, resolutions and feedback
• Traditional APIs: Search
• Traditional APIs: Selling
• eBay APIs: Talk to your fellow developers
• eBay APIs: SDKs
• Token, Messaging, Sandbox related issues
• Feedback, Comments, Suggestions
• RESTful Sell APIs: Account, Inventory, Catalog and Compliance
• RESTful Sell APIs: Fulfillment
• RESTful Sell APIs: Marketing, Analytics, Metadata
• Post Order APIs – Cancellation
• Post Order APIs – Inquiry, Case Management
• Post Order APIs – Return
• RESTful Buy APIs: Browse

The original link, forums.developer.ebay.com, now redirects to this page on the community.ebay.com section of eBay’s website.

It appears eBay vaporized discussion posts from the old board. For example, in September of 2021, a develop had asked if it was possible to send PDF invoices to customers. But in the new Selling API board, there are only 5 discussions with the earliest posting date of February 1st.

eBay did not provide a reason for moving the developer discussion board.

Ina Steiner

Ina Steiner is co-founder and Editor of EcommerceBytes and has been reporting on ecommerce since 1999. She's a widely cited authority on marketplace selling and is author of "Turn eBay Data Into Dollars" (McGraw-Hill 2006). Her blog was featured in the book, "Blogging Heroes" (Wiley 2008). She is a member of the Online News Association (Sep 2005 - present) and Investigative Reporters and Editors (Mar 2006 - present). Follow her on Twitter at @ecommercebytes and send news tips to ina@ecommercebytes.com. See disclosure at EcommerceBytes.com/disclosure/.