Free tier · no payment method required

eBay Category Sold Listings API

Use the eBay Category Sold Listings API to browse sold listings in an eBay category. Call one documented GET endpoint across 3 eBay marketplaces with the same API key, normalized JSON, and production metadata.

Get an API key View Documentation

TL;DR

The eBay Category Sold Listings API returns structured eBay JSON as a flat JSON object. It is available through REST and MCP, with a 5 min cache policy and explicit request, freshness, rate-limit, and usage metadata.

Use this eBay operation through

REST API OpenAPI MCP and agent Skill

Live demo

Try the eBay Category Sold Listings API in your browser

Run the allowlisted eBay category sold listings preset against the real SoldFetch backend. Parameters are predefined and validated before an upstream request is made.

Try the Category search API

Run the predefined request before writing a single line

example response · ready

{
  "keyword": "",
  "page": 1,
  "totalItems": 1,
  "totalResults": "1",
  "hasNextPage": false,
  "autoSelectedCategory": null,
  "items": [
    {
      "itemId": "123456789012",
      "title": "Illustrative listing \u2014 not live data",
      "soldPrice": "120.00",
      "soldCurrency": "USD",
      "endedAt": "2026-10-07",
      "quality": {
        "priceBasis": "displayed_listing_price",
        "saleDateVerified": false
      }
    }
  ]
}

Endpoint

What does the eBay Category Sold Listings API return?

The eBay category sold listings operation is available through every SoldFetch interface and resolves through the same validation and normalized output contract.

REST responseavailable

GET /v1/scrape/category returns a flat JSON object.

OpenAPI contractavailable

Inspect the versioned input parameters and response schemas before integrating.

MCP toolavailable

search_ebay_category exposes the allowlisted operation to compatible AI agents.

Developer First

How do you call the eBay Category Sold Listings API in seconds?

Use /v1/scrape/category to retrieve eBay category sold listings data without maintaining marketplace-specific acquisition, parsers, retry rules, or response adapters.

One schema, every operation

Use this API alongside 2 other SoldFetch operations without changing authentication or the documented JSON format.

Metadata, not guesswork

Every response includes request, cache, freshness, rate-limit, and usage metadata for production decisions.

See the contract before coding

Copy a request in Python, TypeScript, or cURL and inspect the example JSON before moving into production.

example response · ready

import requests

response = requests.get(
    'https://soldfetch.com/v1/scrape/category',
    params={'categoryId': '112529', 'ebaySite': 'ebay.com', 'count': '60'},
    headers={'API-KEY': 'soldfetch_live_YOUR_API_KEY'}
)
data = response.json()

[ .JSON ]

{
  "keyword": "",
  "page": 1,
  "totalItems": 1,
  "totalResults": "1",
  "hasNextPage": false,
  "autoSelectedCategory": null,
  "items": [
    {
      "itemId": "123456789012",
      "title": "Illustrative listing \u2014 not live data",
      "soldPrice": "120.00",
      "soldCurrency": "USD",
      "endedAt": "2026-10-07",
      "quality": {
        "priceBasis": "displayed_listing_price",
        "saleDateVerified": false
      }
    }
  ]
}

Browse all 3 APIs

One eBay API, 3 marketplaces

How does SoldFetch normalize eBay category sold listings data across marketplaces?

eBay storefronts vary by host, currency, locale, delivery context, and available fields. SoldFetch keeps those differences behind one versioned category sold listings contract.

One schema, every marketplace

One documented contract.

3 eBay storefronts use one marketplace code, validation layer, and output contract.

ebaySite: ebay.com fetchedAt: ISO timestamp

Currency and locale included

Context stays attached.

Marketplace, currency, delivery context, request ID, cache state, and fetch time travel with the normalized response.

cache: HIT fetched_at: 2026-08-16T12:00:00Z usage_units: 1

REST and MCP

One key, every interface.

Keep one server-side API key while application code and agents use the interface that fits their workflow.

REST: /v1/scrape/category MCP: search_ebay_category

Operation-level freshness

Caching fits the data.

This endpoint uses a 5 min cache policy so volatility and request cost stay explicit.

cache_ttl: 300 rate_limit: documented request_id: soldfetch_...

Get an API key

SoldFetch eBay API3 request examples

View docs

GET/v1/scrape/category?categoryId=112529&ebaySite=ebay.com&count=60

categoryId112529ebaySiteebay.comcount60

curl 'https://soldfetch.com/v1/scrape/category?categoryId=112529&ebaySite=ebay.com&count=60' \
  -H 'API-KEY: soldfetch_live_YOUR_API_KEY'

example response · ready

{
  "keyword": "",
  "page": 1,
  "totalItems": 1,
  "totalResults": "1",
  "hasNextPage": false,
  "autoSelectedCategory": null,
  "items": [
    {
      "itemId": "123456789012",
      "title": "Illustrative listing \u2014 not live data",
      "soldPrice": "120.00",
      "soldCurrency": "USD",
      "endedAt": "2026-10-07",
      "quality": {
        "priceBasis": "displayed_listing_price",
        "saleDateVerified": false
      }
    }
  ]
}

Compare

How does SoldFetch's eBay Category Sold Listings API compare to a self-managed integration?

SoldFetch packages eBay category sold listings acquisition, validation, normalization, caching, errors, and request metadata behind one server-side key.

FeatureSoldFetchSelf managed

AuthenticationOne API-KEY headerSource-specific credentials or sessions

Setup requiredCreate a key and call the endpointBuild acquisition, parsing, retries, and adapters

Marketplace support3 stores through one contractSeparate host and locale handling

Response schemaFlat JSONSource-specific page structures

Freshness5 min policy with metadataYour team owns caching and observation time

InterfacesREST, MCP, and SkillYour team maintains each adapter

How is eBay Category Sold Listings API usage measured?

Successful normalized operations consume the units defined by the active plan. Request headers make usage and rate-limit state visible to your backend.

Can I use eBay category sold listings data in production?

Use public data, respect source rules and third-party rights, keep keys server-side, and match retention and downstream processing to your approved use case.

FAQ

eBay API questions, answered

Answers about this eBay API, its parameters, interfaces, freshness, and production use.

How do I call the eBay Category Sold Listings API?

Create a SoldFetch key, send a GET request to /v1/scrape/category with one of the documented identifier or query presets, and read the flat JSON response.

What does the eBay Category Sold Listings API return?

Browse sold listings in an eBay category. Optional fields remain optional, and every eBay API response includes request and freshness metadata needed for production handling.

Which eBay marketplaces support category sold listings?

Use the same operation across 3 supported eBay marketplaces by passing the documented ebaySite value.

How fresh is eBay category sold listings data?

This operation uses a 5 min cache policy. Read the cache-state and data-fetched-at headers instead of inferring freshness from when your application received the response.

Can I use the eBay Category Sold Listings API with an AI agent?

Yes. The search_ebay_category MCP tool and generated documentation expose the same allowlisted eBay operation and validation rules.

Can I use the eBay Category Sold Listings API in production?

Yes. Keep keys server-side, validate optional fields, store request IDs, use bounded retries for temporary failures, and review source rules and third-party rights for your use case.

Contract statistics

eBay API contract at a glance

Current eBay category sold listings details generated from SoldFetch's versioned operation catalog.

eBay marketplaces

5 min

cache policy

interfaces

Ready to call the eBay Category Sold Listings API?

Create a key, keep it server-side, and run the predefined eBay request in minutes.

Get an API key