eBay APIs | eBay Community

Home
News & Updates
Buying & Selling
Explore Categories
About
Community Events
eBay Help

Categories

eBay APIs | eBay Community

Special Categories

eBay Developers Program

eBay APIs

Created May 5, 2026

0 members

8 discussions

bestconnections
bulkMigrateListing
I have been trying to do this but get and item id error and not sure why.
2 weeks agolast reply 2 weeks ago
1
sunset_hills
Commerce Catalog Access
Hi, My app uses client credentials OAuth with the Browse API (works pretty cool). How do i access the Commerce Catalog API to search for ePIDs by keyword? Can I get approved to use /commerce/catalog/v1_beta/product_summary/search ?" Thanks, Gary
Jun 19, 2026 at 9:17 PM
0
sunse5569
Browse API — getItem works, batch getItems doesn't (ticket submitted)
Hi, Quick one on the Buy Browse API . What works Browse search returns results fine getItem on those same item IDs works (200, full item payload) What doesn't getItems (batch) with the same OAuth app, same token, same IDs fails Example: GET /buy/browse/v1/item/v1|{itemId}|0 → OK GET /buy/browse/v1/item/?item_ids=v1|{itemId}|0 → fails Same headers ( Authorization , X-EBAY-C-MARKETPLACE-ID , etc.) on both. I'm not looking for a quota increase — the default 5,000/day buy.browse limit is fine for us. I just want batch getItems to work so we're not forced into one getItem call per listing. I've opened a developer support ticket for this. Two questions for anyone who's been through it: Roughly how long does eBay dev support usually take to respond / resolve Browse API issues? Any faster channel — forum escalation, account manager, known workaround — or is ticket the only route? Thanks!
1 month ago
0
dusm8341
BUG REPORT: Edge Gateway WAF blocking valid API IPs (401 invalid_client)
Hello fellow developers and eBay API Support, I am hoping a network engineer or API Gateway team member can look into a routing bug that began on June 1st. Our established inventory sync integration was working flawlessly until June 1st. Now, our requests are being aggressively dropped at the edge by eBay's Web Application Firewall (WAF) with a 401 Unauthorized "invalid_client" error. The exact same credentials authenticate perfectly when sent via Postman. The issue is strictly an IP/User-Agent block at the Edge Gateway against our server's IPs. We are currently stuck in a loop with Developer Support on Ticket 260601-000052 . Tier 1 is understandably requesting an internal rlogId to investigate. However, because the firewall drops the request at the edge before it reaches the core application servers, a valid internal rlogId is physically impossible to generate. We have provided the raw Edge Response headers and timestamps to Tier 1, but they are unable to escalate without the internal ID. Could an API engineer please pull the WAF/Edge logs for this ticket to verify the false-positive block against our server so we can resume our integration? Thank you!
1 month ago
0
dusm8341
BUG REPORT: Edge Gateway WAF blocking valid API IPs (401 invalid_client)
Hello fellow developers and eBay API Support, I am hoping a network engineer or API Gateway team member can look into a routing bug that is actively dropping our Google Apps Script traffic. Our established inventory sync integration is being aggressively dropped at the edge by eBay's Web Application Firewall (WAF) with a 401 Unauthorized "invalid_client" error. The exact same credentials authenticate perfectly when sent via Postman. The issue is strictly an IP/User-Agent block at the Edge Gateway against our server's IPs. To prevent redundant troubleshooting, please review our established paper trail. We have had two separate Zoom calls with Developer Support proving this is an internal gateway configuration issue: Ticket 260419-00023 (April 19 - May 6): We experienced an "invalid grant error on new token exchange." This was escalated to a Tier 2 Zoom call, completely resolved on May 6th, and our integration ran flawlessly for nearly a month. June 1: The current Edge Gateway WAF block abruptly began. Ticket 260601-000052 (June 5): We secured a second Zoom call at 5:00 PM. Support successfully cleared the WAF block, and our API access was fully restored. However, by 10:00 PM that exact same evening, the WAF reverted and began blocking our IPs again. Administrative Loop (June 5 - Present): We have been stuck in a circle since the evening of June 5th. Support is understandably requesting an internal rlogId to investigate. However, because the firewall drops the request at the edge before it reaches the core application servers, a valid internal rlogId is physically impossible to generate. We provided raw Edge headers, but Tier 1 cannot escalate without the ID. Furthermore, EPN Support (TIG Ticket 00448864) simply points back to Developer Support, and standard phone support is unequipped for API routing. Could an API engineer please pull the WAF/Edge logs for these specific tickets to verify the false-positive block against our server so we can permanently restore our integration? Please let me know if you need me to provide specific Google Cloud IP ranges or additional raw headers to assist with your internal escalation. Thank you, Dusty LRS Collectibles
1 month ago
0
dusm8341
Subject: URGENT: Edge Gateway blocking API & EPN - Caught in Support Loop (Ticket 260601-000052)
Subject: URGENT: Edge Gateway blocking API & EPN - Caught in Support Loop (Ticket 260601-000052) Hey everyone, I need an actual Tier 3 Integration Engineer or Community Manager to look at this, because standard support has had me in an endless email loop since June 1st and my business is completely bottlenecked. I run LRS Collectibles. I'm a Top-Rated Seller with a flawless feedback record. Since this API issue started, my total sales are down 45.1%, and my sports card singles are down 68.1%. I have a massive physical inventory of collectibles just sitting here ready to go, but I haven't even been able to start listing them because my automation is hard-down. On top of that, I'm an EPN Affiliate. I'm trying to launch my external business website right now (structured with pillars for sports, gaming, breaks, a blog, and bedding) to drive outside traffic directly to my eBay listings. But I can't connect the site or route the traffic. eBay is actively losing out on Final Value Fees because your API block is stopping me from operating. This whole thing has been a mess since February, and this is actually the third separate time your system has locked me out. (I have the ticket numbers for the previous crashes if you need them): February: Your system wouldn't even let me log in to generate a Client ID. Mid/Late March: I finally got everything up and running correctly. Then eBay dropped that massive Spring update around the middle of March. Everything crashed, and I had to go back in and completely rewrite my code to comply with your backend changes. June (Current): After rewriting my code, I got it working perfectly again for a few weeks in May—and my sales immediately spiked—but now it's hit me again, and my production environment is permanently blocked. Here is the actual technical issue: My credentials are 100% valid. They authenticate and generate a token flawlessly using Postman. But when I pass those exact same credentials through my production server (Google Apps Script), eBay's edge gateway actively rejects the handshake with a 401 Unauthorized ( "error":"invalid_client" ). Every time I explain this to Tier 1, they send me a canned reply saying: "We are unable to locate the request in our logs, and without a valid rlogId, we cannot investigate further." I am literally stuck in a Catch-22. Your edge firewall is killing my script BEFORE it reaches your core API logs. The rlogId I gave support IS the exact timestamp of your firewall rejecting me. You can't ask me for a log that your own perimeter security destroys before it's even created. Tier 1 support is searching the core API database and obviously doesn't have the clearance to view edge gateway drops. I need a network/integration engineer to pull the firewall drops for the timestamp I provided, see why my server environment is getting blacklisted, and lift this block so I can actually run my business.
1 month ago
0
fishmonger1000
Browse API buyingOptions issue with price filtering?
With the Browse API item_summary is there a bug with the price filtering when you set buyingOptions:{BEST_OFFER|FIXED_PRICE|AUCTION}? In the past week or so my queries have started returning items over the max price when all three buying options are set, but it respects the max price if only one buying option is set. My queries have been working fine for months and I didn't change anything on my end so either I missed a change to the documentation or there's a bug. Any help would be greatly appreciated, thanks! Here's an example query that is returning items priced over $10: https://api.ebay.com/buy/browse/v1/item_summary/search q=("criterion collection", criterion) blu ray limit=200 category_ids=617 filter= price:[..10.00], priceCurrency:USD, buyingOptions:{BEST_OFFER|FIXED_PRICE|AUCTION} aspect_filter= categoryId:617, Format:{Blu-ray|Ultra HD|4K UHD Blu-ray|4K HD|Unspecified} offset=0
1 month ago
0
given2sell
Support Ticket: 260503-000026 Assistance
Hi, I have had a ticket open since May 3rd. Does anyone know how I can inquire about the status of the ticket besides posting on the ticket itself which I have done various times.
1 month ago
0

SDKs
0 members · 81 discussions
Talk to your fellow developers
0 members · 463 discussions