The eBay product search engine

They search the web. SoldFetch searches eBay. Send one validated query to a selected marketplace, keep filters and placement explicit, and receive normalized products your application can reason about. The same contract spans every supported storefront.

Try a search Read the API docs

One discovery contract across SoldFetch's most-used eBay APIs

Sold and active search Category search Item details

The engine

One query in. One normalized result set out.

Watch a single product query move through the contract: scoped, validated, routed to the right storefront, acquired, normalized, and returned with explicit metadata.

Raw marketplace markup→volatile

SoldFetch→normalized

QUERY

mechanical keyboard

US · page 1 · limit 10

allowlisted request preset

SoldFetch Universal Search Contractbuilt to isolate marketplace volatilityPRODUCTION

Scope

A bounded query names the marketplace, page, limit, and filters.

Validate

Unsupported parameters stop before upstream work begins.

Route

The domain selects the eBay host, locale, and currency context.

Acquire

The relevant discovery surface is fetched under one cache policy.

Normalize

Products, placement, prices, and pagination enter one contract.

Respond

Data and request metadata return through the same envelope.

cache state, usage, and request metadata stay explicit

Normalized products

results

placement

pageInfo

requestMeta

Every result carries the marketplace facts needed downstream.

validatedsource-aware

How it works

How does one query work across supported eBay sites?

Three moves turn a bounded search phrase into comparable product data.

01 · Validate and scope

The contract trims ambiguity first

Search term, marketplace, sort order, price, condition, page, and count are checked before provider work begins.

02 · Route and acquire

One request enters the right storefront

The selected domain resolves the eBay host, locale, currency, and deterministic acquisition context for that request.

03 · Normalize and return

Products arrive in one stable shape

Item identity, displayed price, condition, pagination, and quality fields share one JSON format.

Every field here belongs to the public request or response contract. See the API reference for the complete schema.

Why it is hard to copy

No single trick. The whole contract.

The advantage is the integration: validation, marketplace routing, acquisition, normalization, and explicit freshness metadata behind one operation surface.

BOUNDED VALIDATION

Every parameter has an explicit type and range. Invalid work is rejected before it can consume provider capacity or usage.

MARKET ROUTING

Three enabled storefronts map to the correct host, locale, currency, and ranking context without leaking that branching into your app.

CANONICAL OUTPUT

Volatile source markup is translated into stable products, prices, condition, filters, and page metadata.

CACHE + OBSERVABILITY

Freshness policy, cache state, request metadata, logs, quotas, and consistent failures travel with the same operation contract.

“The moat is the contract: marketplace volatility goes in, predictable product data comes out.”

eBay vs open web

They search the web. SoldFetch structures eBay.

General search APIs are excellent at the open web. SoldFetch is a different data product: normalized commerce discovery with explicit marketplace context.

How they compare	SoldFetch	Open-web search
What it searches	eBay product and discovery surfaces	Public web pages and documents
What a result is	A normalized product card with marketplace context	A web page, snippet, or document
How results rank	Upstream search order with explicit price and condition filters	Links, text relevance, and page authority
Marketplace context	Host, locale, currency, and storefront stay explicit	No commerce-specific storefront model
Output	Validated products, pagination, cache state, and request metadata	A list of links or extracted text

What it searches

SoldFetch

eBay product and discovery surfaces

Open-web search

Public web pages and documents

What a result is

SoldFetch

A normalized product card with marketplace context

Open-web search

A web page, snippet, or document

How results rank

SoldFetch

Upstream search order with explicit price and condition filters

Open-web search

Links, text relevance, and page authority

Marketplace context

SoldFetch

Host, locale, currency, and storefront stay explicit

Open-web search

No commerce-specific storefront model

Output

SoldFetch

Validated products, pagination, cache state, and request metadata

Open-web search

A list of links or extracted text

Try it

Choose a query. Inspect the result.

Open one of SoldFetch's allowlisted eBay search examples, run the live request, then inspect the normalized response before you integrate.

example response · ready

{
  "success": true,
  "data": {
    "results": [
      {
        "asin": "B0EXAMPLE1",
        "title": "Example mechanical keyboard",
        "price": {
          "value": 89.99,
          "currency": "USD",
          "display": "$89.99"
        },
        "rating": 4.7
      }
    ],
    "pageInfo": {
      "currentPage": 1,
      "hasNextPage": true
    }
  }
}

Get an API key to run your own requests

presetvalidaterouteacquirenormalizeresponse

Inputs are selected from documented presets. Production calls use the same validation and normalized response contract.

Under the hood

Every marketplace returns a different page context.

eBay's hosts, currencies, locales, ranking surfaces, and page markup vary by storefront. Before your application sees a result, SoldFetch normalizes identity, price, rating, placement, sponsored state, pagination, and request metadata into one canonical contract.

See how the unified schema works

At a glance

One contract. Every storefront.

3Enabled marketplacesone explicit ebaySite

7Discovery operationsone auth model

4Public interfacesREST · REST · MCP · Skill

1Normalized contractsource-aware output

Numbers reflect the documented Universal Search surface and the marketplace context carried by every request.

Frequently asked questions

Can't find what you're looking for? Talk to our team.

How is Universal Search different from a web search API?

Web search APIs discover public pages. SoldFetch Universal Search reads eBay product and discovery surfaces in a selected marketplace, then returns normalized product cards, placement, filters, pagination, cache state, and request metadata. It is a commerce-data contract, not a general web index.

Does one request search all supported eBay sites at once?

No. Each request names one marketplace so host, locale, currency, and ranking context stay unambiguous. The same validated request and response contract works across all enabled marketplaces.

Which discovery operations use this contract?

Keyword search and category search share the same authentication, marketplace model, error conventions, and response envelope.

Can I distinguish sponsored and organic results?

No. This release does not expose verified sponsored placement or organic rankings.

Can I try a request without an API key?

Yes. The public examples use fixed, allowlisted parameters and run through the protected server-side playground proxy. Production requests require an organization-scoped API key.

Do REST, MCP, and the agent Skill use the same operation?

Yes. Every interface maps to the same search operation, validation, cache policy, usage ledger, and normalized eBay domain model.

Start searching

Search eBay like it's one stable surface.

Choose a marketplace and send one bounded request from your code. The same operation, validation, and normalized response across every supported storefront.

Get your API key Read the docs

cURL

curl "https://soldfetch.com/v1/scrape?keyword=mechanical%20keyboard&ebaySite=ebay.com&page=1&count=60" \
  -H "API-KEY: soldfetch_live_YOUR_API_KEY"