URGENT: Growth Check #260705-000024 overdue; paid acquisition and sellers impacted
Summary: fidemasterdavid reports delays in processing Growth Check #260705-000024, submitted for increasing API call limits for their seller-productivity application on eBay. Despite multiple requests and inquiries, there was no progress, causing significant disruptions and financial losses due to inadequate API capacity. The company requested immediate interim relief and a permanent increase in API calls but faced persistent quota failures impacting their operations. Eventually, some increases were approved, but not all requests met the required capacity, leaving the issue partially unresolved. fidemasterdavid continues to seek a firm decision date and mitigation for the remaining constraints.
Hello eBay Developer Support,
ListForge submitted Application Growth Check #260705-000024 on July 5, 2026 for a live seller-productivity application. eBay's selling-application guide says applicants should hear back within 3–5 business days and that the process should finish within 5–7 business days. As of July 22, 13 business days have elapsed.
Our current Trading API allocation is 50,000 calls/day. We are requesting a permanent increase to at least 500,000 calls/day (10x), or eBay's highest available tier; proportional increases for every other constrained production API; and immediate interim relief to at least 250,000 Trading calls/day while the review is completed.
This is now a paid-acquisition and production incident. Active ad campaigns are sending new sellers into eBay connection and onboarding, but insufficient capacity is contributing to connection, full-store ingestion, and synchronization problems. We are wasting ad spend, losing conversions, impairing existing sellers, and taking direct revenue damage.
We supplied our use case, Trading call inventory, and volume controls. Support replied on July 5, 10, and 15 only that it was checking with the business team. We still have no accountable owner, substantive status, missing-information request, decision, or timeline. Recent production evidence showed 12,000–20,000 calls/day before a completed efficiency fix, with a protective guard exhausting around 13:00 UTC and several large connected stores receiving no further sync that day. We have already shipped efficiency improvements; they do not remove the need for growth capacity and onboarding headroom.
Similar May and June Growth Check threads in this forum remain unresolved, so this appears to be a broader escalation-path problem.
Could the official developer-support team please: (1) assign an accountable business-team owner; (2) identify any missing information immediately; (3) grant interim capacity; (4) provide a firm decision date; and (5) route ListForge to the Developer Loyalty/Partner team?
Please link every escalation to the existing application without restarting its place in queue. We can provide live getRateLimits data, forecasts, logs, architecture details, or a live walkthrough immediately.
fidemasterdavid
OP1 week agoNew restricted-access routing result — July 28, 15:09 UTC: Developer Support closed Browse bulk prerequisite case #260728-000031. It said getItems bulk access cannot currently be offered “without an increase in value driven,” may become possible as ListForge’s eBay business grows, and advised contacting an Account Manager. The response supplied no measurable value threshold, approved-partner criteria, owner, or route for an applicant without an Account Manager. This is useful direction but not an actionable access path. Please route #260725-000023/#260728-000031 to the accountable Browse API or partner-management owner and provide: (1) the objective GMV, seller, transaction, or other value criteria; (2) the required evidence and review window; (3) how ListForge obtains account-manager sponsorship or an equivalent intake; and (4) a firm eligibility-review date. The entitlement remains unresolved until the production bulk probe returns HTTP 200 and the onboarding hydration check passes.
fidemasterdavid
OP1 week agoVerified portfolio decision — July 28, 14:32 UTC: fresh production getRateLimits confirms Finances increased 15,000→100,000/day (#260727-000038), Fulfillment 100,000→500,000/day (#000041), and Notification to 50,000/day (#000044). Thank you for the movement. Fulfillment meets the requested tier; Finances remains below the 250,000 interim/500,000 permanent ask, and Notification below 100,000. Since today’s 07:00 UTC reset, CloudWatch shows zero eBay Finances quota 429s, so relief is helping. eBay closed Browse #000039 on “business policies,” Analytics #000040, Taxonomy #000043, and Metadata #000045 for low current usage, and Trading #000042 until more of the active 250,000 tier is used. We asked the private Developer Support route to assign owners for partial grants, state whether 100,000/50,000 are maximum current tiers, and provide objective reconsideration criteria/dates for Browse and next-tier Trading. Whole-keyset capacity remains open until limits are adequate for growth.
fidemasterdavid
OP1 week agoMaterial capacity update - July 27, 20:43 UTC: eBay approved Growth Check #260705-000024 and the 250,000/day Trading tier is verifiably active. Thank you for that relief. Whole-keyset capacity remains unresolved. Finances is now 14,490/15,000 used (96.6%), with only 510 calls left; the trailing 24 hours still show 434 order-financial 429s across 111 seller orders. We opened distinct Finances case #260727-000038 plus Browse #39, Analytics #40, Fulfillment #41, Trading next-tier #42, Taxonomy #43, Notification #44, and Metadata #45. Please route #260727-000038 to a named Finances owner, grant 250,000/day interim and 500,000/day or the highest tier permanently, and provide decision dates for the portfolio.
fidemasterdavid
OP1 week agoFresh verified production threshold — July 27, 14:39 UTC: CloudWatch found 434 exact eBay Finances “Too many requests” failures across 111 distinct seller orders in the trailing 24 hours, persisting from 01:00–07:00 UTC. Live getRateLimits still shows no relief: Finances remains 15,000/day and is already 61.5% used (9,220 calls); Trading remains 50,000/day (6,482 used); Browse remains 5,000/day and is 48.4% used (2,420 calls). We posted this evidence to Growth Check #260705-000024. The case still has no named owner or decision date. Required remedy remains coordinated whole-keyset capacity: 250,000 Trading/day immediately with proportional constrained-family relief, 500,000/day permanently or eBay’s highest tier, and a firm decision date.
fidemasterdavid
OP2 weeks agoEscalation-channel failure — July 24: We tried again to open a distinct live-production DTS incident. eBay's AI-Assisted Support Submit control returns no response and creates no ticket, even with a short description; the official eBay Inc. Contact Developers Program link returns 404. The Growth Check still displays Severity: Low despite 587 Finances 429s across 135 order messages. We added this to #260705-000024 and privately asked developer-support@ebay.com to open or route the DTS incident internally. Please assign a named owner, reclassify severity, grant interim relief, and provide a firm decision date.
fidemasterdavid
OP1 week agoNew verified production threshold — July 25, 12:34 UTC: ListForge recorded 601 actual eBay HTTP 429 responses in the rolling 24 hours, persisting from 04:06–07:00 UTC across five ECS streams while 65 distinct seller orders were being financially enriched. At 15:32 UTC there is still no capacity change: Trading remains 50,000/day (4,693 used) and Finances remains 15,000/day (4,080 used). eBay API Status shows no unresolved production outage. This is recurring quota failure, but the requested remedy is whole-keyset capacity: name an accountable owner and firm decision date; grant 250,000 Trading/day immediately with proportional constrained-family relief; approve 500,000/day permanently or the highest tier; and complete the coordinated Sell, Commerce, Buy, notification, post-order, research, marketing, analytics, recommendation, and legacy API review under #260705-000024.
fidemasterdavid
OP2 weeks agoCritical production incident evidence — July 24: ListForge logs now show 587 eBay Finances “Too many requests” failures across 135 distinct order messages in the last 24 hours. The failures persisted hourly from approximately 21:00 UTC until the 07:00 UTC quota reset, blocking real seller-order financial reconciliation. Only 6½ hours into today's quota window, Finances is already 72.8% consumed (10,920/15,000; 4,080 remaining). Trading remains unchanged at 50,000/day, so no Growth Check increase is active. We attached the evidence to #260705-000024. This is sustained customer production failure. We need an accountable owner, immediate 250,000/day Trading relief, at least 500,000/day permanent capacity or the highest tier, proportional Finances/other API increases, and a firm decision date without losing the July 5 queue position.
fidemasterdavid
OP2 weeks agoMaterial production update — July 23, 19:55 UTC: live eBay Developer Analytics still shows the Trading shared pool unchanged at 50,000/day (37,827 remaining after 12,173 calls today). Finances is already 97% exhausted — 14,550 of 15,000 calls used, with only 450 remaining. No substantive eBay response has arrived since July 15. We added this evidence to Growth Check #260705-000024 and are requesting an accountable owner, 250,000 Trading calls/day as immediate relief, at least 500,000/day permanently (or the highest available tier), and proportional increases for other constrained production APIs. If an eBay Developer Program owner sees this, please provide a firm decision date and keep the existing July 5 queue position.