Finding API EOL in February 2025 – Delays in Limit Adjustments for Browse API Migration

[esagu]

Hello eBay Developer Community,

As the Finding API is scheduled for deprecation in February 2025, we are facing significant challenges due to unresolved delays from the eBay Developer Support team in approving the necessary API limit adjustments for the Browse API.

Our application, an established "eBay Compatible Application," has relied on elevated request limits (~3,000,000 requests/day) with the Finding API to provide competitive pricing insights for our customers. The standard limit of 5,000 requests/day on the Browse API is drastically insufficient to maintain our operations at scale.

We opened a ticket with eBay Developer Support (241106-000007) on November 6, 2024, requesting a limit increase to align the Browse API with our existing limits under the Finding API. Despite providing detailed documentation, following up multiple times, and emphasizing the urgency of this matter, we have only received vague assurances that the issue is being reviewed by the business team. To date, no resolution or timeline has been provided.

This delay is particularly frustrating because the technical migration from the Finding API to the Browse API was trivial. Both APIs use HTTP, JSON, and OAuth, with only minor changes to the JSON structure and query parameters. The data is 95% identical, and as a verified eBay Compatible Application, we did not expect the need for another lengthy approval process.

Without the necessary API limit adjustments, we are deeply concerned that, come February 2025, we will no longer be able to make the required API calls to support our customers’ operations. This would severely impact not only our business, but also the eBay sellers who rely on our application for competitive pricing and listing optimization.

Has anyone else encountered similar delays or challenges with API limit adjustments during their migration to the Browse API? Are there any effective escalation channels to address this issue more directly with the eBay Developer team?

We appreciate any guidance or advice the community can provide.

Thank you for your support.

[esagu]

We recently received an increase in our Browse API call limit to 100,000 requests/day (Ticket: 241106-000007). While this is a step forward, it is still far below what we need to match the capacity we previously had with the Finding API, which was 3,000,000 requests/day (Ticket: 180827-000003).

Our goal is simple: we are not asking for more than we had before—just enough to maintain the existing functionality for our customers during this migration.

Has anyone experienced similar issues with API limits during migration, or does anyone have advice on how to escalate further?

Thank you for your insights!