Aim — application preparation draft
Subtitle: Aim for eBay
Prepared: 2026-09-24 | NOT SUBMITTED | Production API access not verified

Keyset status: AIM Sandbox and Production keysets have been created. On 2026-09-24 the developer portal showed the Production keyset disabled pending marketplace account deletion compliance. Production credentials have not been installed in Vercel. This does not establish approval of the proposed use case.

Applicant information to complete before submission
- Legal business / trading name: JIYUJIN Co.,Ltd (confirmed by the owner on 2026-09-24)
- Contact name: [TO BE COMPLETED BY OWNER]
- Notification contact email: [CONFIRMED IN THE PRIVATE OPERATOR RECORD; INSERT IN THE EBAY SUBMISSION]
- Business country and address: [CONFIRMED IN THE PRIVATE OPERATOR RECORD; INSERT IN THE EBAY SUBMISSION]
- Existing ordinary eBay user ID: [TO BE COMPLETED BY OWNER]
- Application name: Aim (subtitle: Aim for eBay)
- Developer account ID / application ID: [REGISTERED; ADD TO THE PRIVATE EBAY SUBMISSION, NOT THIS PUBLIC DRAFT; DO NOT INCLUDE CLIENT SECRET]
- EPN account, if required for this use case: [NOT CONFIRMED]
- Privacy policy and contact URL: [TO BE FINALISED]
- Sandbox test URL: https://ebay-delta-henna.vercel.app/api-setup
- Operator access: a separate operator code is required; provide secure reviewer access separately, never in this public document.

Proposed use case
We are preparing Aim, a paid, multi-user product and seller research application for sellers sourcing inventory in Japan. An authenticated member explicitly enters a product keyword, searches current listings either across available item locations or with an explicit Japan item-location filter, reviews the seller accounts returned, selects seller checkboxes, and requests the selected sellers' current listings. Item location is not treated as seller registration country or nationality. The service is category-neutral and supports research across all available product categories. The planned membership fee is JPY 2,980 per month.

We are seeking confirmation that this commercial member research use is eligible, which API access route applies, and which written permissions are required for seller-level grouping, feedback display, product/price comparisons and CSV/JSON exports. We do not claim an approved affiliate or checkout business model. Please advise whether the standard Buy API/EPN route applies to this application or a different route is required.

Requested interfaces and data
- Browse API item_summary/search: current listing ID, title, condition, price and currency, available shipping information, item location, listing URL, seller identifier and feedback fields when returned.
- Taxonomy API: marketplace category tree information for EBAY_US.
- OAuth application token using client_credentials and the api_scope scope. No buyer checkout or order processing is implemented.
- Search results are grouped by seller identity. The app adds retrieval timestamps. Selected listing exports currently retain the returned source payload; we seek approval for the allowed fields and export scope before production use.
- Browse current-listing data will not be represented as verified sale price, period sales volume or a complete census of sellers.

Current implementation and requested operating model
Application: https://ebay-delta-henna.vercel.app/
Preparation page: https://ebay-delta-henna.vercel.app/api-setup
The public application exposes a base research dataset with source links and evidence limitations. It also has synthetic operation samples, separately labelled when used. Account-specific sourcing candidates, plans and notes require sign-in. The existing research records and price-summary/profit-calculation screens are separate from the new Browse integration and should be included in the use-case review. Sandbox credentials and operator access have been configured. On September 24, 2026, the operator reported completion of the connection test and supplied a screenshot showing Sandbox test-user seller results for a camera search. The structured connection report and selected-listing extraction evidence remain to be collected. Production API access has not been verified.

All new eBay API requests require an authenticated entitled member (or an authorized app operator) and explicit action. There is no scheduled collection or automatic retry. The application follows result pages and stops with an incomplete status when the provider limits/errors prevent completion. No application-specific total seller cap is imposed; eBay limits still apply.

Credentials and application tokens stay on the server. Sandbox and Production use separate credentials and endpoints. Production calls are disabled until the operator records actual use-case approval and completes the data-handling launch requirements. These settings do not constitute eBay approval.

Newly fetched research results and in-progress work are retained in tab-scoped browser session storage with a 24-hour read validity window; a reload can restore that work and does not itself clear it. Expired work is not restored; this is not a claim of physical deletion from browser storage or backups. The app does not automatically ingest newly fetched listings into the shared research database. Explicitly saved seller bookmarks persist in browser local storage for guests or private account notes for signed-in members. Personal sourcing candidates, plans and notes are saved separately by authenticated account. CSV/JSON exports can be initiated by the user, subject to the permissions requested for production. Existing seller/product research records remain in a dedicated database. We therefore do not assert that the application qualifies for an account-deletion notification exemption. A disabled notification ingress now supports challenge verification, ECC signature checks, encrypted durable receipt and retry deduplication. It does not yet perform erasure. Deletion processing, immutable-user-ID matching, export/backup handling and the final privacy notice remain pending. These will be completed and tested before notification subscription and Production use, in accordance with the approved use and retention requirements.

User experience / data flow
1. Member signs in with the application account; the server verifies an active entitlement and available request budget.
2. Browser sends a keyword research command to the application server.
3. Server obtains/reuses the appropriate eBay application token and calls Browse; credentials never go to the browser.
4. Browser shows available seller identity, feedback, item-location evidence and source links.
5. Member selects sellers and requests extraction. Server uses the selected seller filter with marketplace categories and validates returned seller identities.
6. Browser shows the selected listings and the retrieval/source details. The user can explicitly save seller bookmarks and export permitted data. Reloading or returning to a workflow can restore in-progress work within the 24-hour read validity window. No background API collection resumes.

Questions for the eligibility / access review
1. Is a paid multi-user seller/product research service for inventory sourcing permitted through Browse for this business, and which application route should we use?
2. What written permission is needed for seller-specific data, grouped seller lists, feedback sorting, product price summaries and CSV/JSON exports, considering the API License Agreement?
3. Which fields, retention periods, refresh/removal requirements and export restrictions apply to the approved use?
4. Which stable user identifiers can this app receive and match for marketplace account deletion notifications? Existing records primarily use listing usernames; this is not yet a complete immutable-ID mapping.
5. Please confirm applicable API licensing, fees (if any), initial rate limits and the process for any required increase.

Review attachments to prepare after Sandbox setup
- Screenshots: keyword input and explicit execution; seller checkboxes; selected listing results with sources.
- Data flow above, actual Sandbox test URL and step-by-step test instructions.
- Successful connection test evidence with date/environment; no tokens or secrets.
- Data-handling and privacy notice after applicant details and permission conditions are confirmed.

Official references checked
https://developer.ebay.com/develop/guides/sell/get-started-with-ebay-apis
https://developer.ebay.com/api-docs/buy/static/buy-requirements.html
https://developer.ebay.com/join/api-license-agreement
https://developer.ebay.com/develop/guides/sell/marketplace-user-account-deletion