Browse API production scope for an existing Production keyset, and exemption semantics
Hello eBay Developer Support,
I could not open a Developer Technical Support ticket: the support page shows only My Tickets,
AI-Assisted Support and Application Growth Check, with no form for a general technical ticket,
and my Primary Contact already shows "Support for this contact is activated". Posting here
instead, as advised for free support.
Developer username: maher4you
Production App ID (Client ID): MaherAhm-AIONpriv-PRD-b82977cdf-2ce86cbf
Application: "AION private evidence tool"
API License Agreement: signed 12 September 2026
The application is a private, internal research and record-keeping tool. It is not a consumer
shopping site, it does not resell eBay inventory, it has no end users other than myself, it
performs no checkout, and it displays nothing publicly. I have made no production call yet.
Four questions.
1. Production scope of my keyset
Which Buy API methods, if any, may this Production keyset call without a separate eBay Partner
Network Buy API approval? Specifically GET /buy/browse/v1/item_summary/search.
The Buy APIs requirements page states that production use of the Buy APIs is intended for eBay
partners and requires an eBay Partner Network application. The eBay Partner Network developer
questionnaire page states that access to the EDP Browse API does not require additional
approval. These two statements appear to conflict; please confirm which applies to a keyset
like mine.
2. The exact refusal if I am not eligible
If this keyset may not call that method, what HTTP status and errorId will my client receive?
I want to record the refusal correctly and not retry against it.
3. Rate-limit visibility
Does Developer Analytics getRateLimits report per-API limits for this keyset before any Buy API
call has been made, and would buy.browse appear there if the keyset is eligible? I would rather
read my own limits than assume documented defaults.
4. Exemption semantics and future access
My application carries the marketplace account deletion/closure exemption on the basis that it
does not persist eBay data.
(a) Is this consistent with that exemption: holding an API response in process memory for the
duration of a single request, writing no response field to disk, and persisting only a SHA-256
digest of the response body together with the HTTP status and response headers?
(b) The Partner Network developer questionnaire states that an application must be subscribed
to marketplace account deletion/closure notifications before extended data access is requested.
If I later apply for extended access, must I first disable the exemption and implement a
notification endpoint, or can the exemption coexist with an extended-access request?
Thank you.
