Affiliate disclosure: DealBench participates in affiliate programs including the eBay Partner Network, Amazon Associates, and retailer programs through CJ Affiliate and Awin. We may earn a commission on qualifying purchases, at no cost to you. Commissions never influence how a deal is scored or ranked, and we don't verify sellers or product authenticity. Learn more.

Developer

eBay API integration

This page documents how DealBench uses the eBay APIs, for eBay reviewers and anyone evaluating our integration. Last updated July 2026.

What DealBench is

DealBench is a tool deal aggregator. We collect current listings from retail and used marketplaces, benchmark each listing against recent market prices, and alert users when a tool they are tracking drops below the price they set. Every deal links out to the original seller — DealBench does not process transactions.

How we use eBay data

  • Browse API — we retrieve active power tool listings in a narrow set of categories and surface them in the deal feed with the seller's title, price, condition, and photo.
  • Market benchmarking — we aggregate comparable listings into a single price baseline so a user can see whether a deal is actually below market. We publish the derived baseline, not bulk eBay data.
  • Outbound links — the primary action on every eBay deal sends the user to the eBay listing, through the eBay Partner Network where applicable.

We do not resell, redistribute, or republish bulk eBay data, and we do not cache listings beyond what is needed to display and re-check an active deal.

Authentication

DealBench authenticates exclusively with OAuth client-credentials application tokens. Tokens are requested server-side and cached in memory until shortly before expiry, so we do not re-mint a token on every call. We never collect, request, or store eBay user credentials or user access tokens, and no DealBench account is linked to an eBay account.

Rate-limit and error handling

All eBay traffic passes through a single server-side gateway that enforces:

  • Retries on 5xx responses only, capped at a maximum of 2 retries, with exponential backoff and jitter.
  • No retries on 4xx responses — a client error is treated as a permanent failure and logged.
  • On HTTP 429 or errorId 2001 ("Application request limit reached"), we stop calling eBay entirely and enter a global cooldown until the daily quota resets at midnight UTC, rather than continuing to retry.
  • Remaining Browse quota is polled from the Developer Analytics rate-limit API and logged, so consumption is measured rather than estimated.

Marketplace account deletion compliance

DealBench operates a verified marketplace account deletion / closure notification endpoint:

https://dealbench.app/api/public/hooks/ebay-account-deletion

  • GET challenge requests return the required SHA-256 hash of the challenge code, verification token, and endpoint URL. The endpoint is verified and saved in the eBay Developer Portal.
  • POST notifications are acknowledged immediately with a 200, and unsigned requests are rejected.
  • Because DealBench ingests listings with an application token and stores no eBay user identity, there is no eBay user data to erase. Each notification is logged for audit purposes without recording the identifier.

Call volume

  • Ingestion runs on an hourly schedule against a narrow category and keyword set — not continuous polling.
  • Market benchmarks are cached for 7 days per tool model, so repeated views and repeated alert checks do not generate new eBay calls.
  • Current steady-state usage is roughly 300–600 calls per day during private beta.
  • We are requesting a ceiling of 100,000 calls per day to support user growth, broader category coverage, and per-alert benchmark refreshes as the tracked tool set expands.

Recent eBay API notices

eBay periodically publishes API change notices. The ones below have no operational impact on DealBench, but we document them here for transparency:

  • Immutable user IDs — DealBench authenticates with application tokens and never stores eBay user IDs or links to eBay accounts, so this change does not affect our integration.
  • Standardized condition details for coins — this applies to collectibles/coins. DealBench is focused exclusively on power tools, so the new condition taxonomy is not relevant to our category set.
  • Size standardization for apparel this applies to clothing and footwear. Tools are not subject to apparel size standards, so this notice is out of scope.
  • EU return reasons — this relates to post-purchase returns and order management. DealBench is read-only and does not process orders, returns, or seller transactions, so we do not consume this API.

Affiliate participation

DealBench is a participant in the eBay Partner Network. Outbound eBay links carry EPN tracking parameters when a campaign ID is configured; otherwise we link to the plain eBay item URL. In both cases the user always lands on the original eBay listing on ebay.com.

We do not rehost, reframe, resell, or redistribute eBay listing content. Cached listing data is used only to determine current availability and to compute price benchmarks, and is refreshed or discarded on our normal ingest cadence.

Commissions never influence how a deal is scored or ranked. A plain-language affiliate disclosure is shown on every public page and documented at dealbench.app/legal.

Current status

DealBench is live in invite-only beta: all marketing, legal, and documentation pages are public, while the deal feed and account area require a beta invite code. The eBay integration is running against production. This page is intentionally accessible without an invite code.

Contact

Questions about this integration? Send us a support request and we will respond directly.