How is eBay 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.
Free tier · no payment method required
eBay sold listings API
Search sold listings by keyword with the eBay sold listings API. Get displayed prices, condition, shipping, and item IDs as JSON over REST or MCP. Use one server-side API key across 3 supported eBay marketplaces.
TL;DR
The eBay sold listings API returns structured eBay JSON as a flat JSON object. It is available through REST and MCP, with a 6 hours for sold results; 15 minutes for active results; 5 minutes for empty results cache policy and explicit request, freshness, rate-limit, and usage metadata.
Use this eBay operation through
API example
Explore the eBay sold listings API in your browser
Inspect the example request parameters and JSON response before integrating.
Explore the Active listings API
Inspect the example request and response before writing a single line.
GET/v1/scrape
keywordsony wh-1000xm5ebaySiteebay.comsoldfalsecount60
Example response
{
"keyword": "sony wh-1000xm5",
"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 sold listings API return?
The eBay sold listings operation is available through every SoldFetch interface and resolves through the same validation and normalized output contract.
Developer First
How do you call the eBay sold listings API in seconds?
Use /v1/scrape to retrieve eBay 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.
import requests
response = requests.get(
'https://soldfetch.com/v1/scrape',
params={'keyword': 'sony wh-1000xm5', 'ebaySite': 'ebay.com', 'sold': 'false', 'count': '60'},
headers={'API-KEY': 'soldfetch_live_YOUR_API_KEY'}
)
data = response.json()[ .JSON ]
{
"keyword": "sony wh-1000xm5",
"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
}
}
]
}One eBay API, 3 marketplaces
How does SoldFetch normalize eBay sold listings data across marketplaces?
eBay storefronts vary by host, currency, locale, delivery context, and available fields. SoldFetch keeps those differences behind one versioned sold listings contract.
One schema, every marketplace
One documented contract.
3 eBay storefronts use the same ebaySite hostname parameter, 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
MCP: search_ebay_sold
Operation-level freshness
Caching fits the data.
Cache duration: 6 hours for sold results; 15 minutes for active results; 5 minutes for empty results. Retrieval timestamps stay unchanged on cache hits.
maximum_cache_ttl: 21600
rate_limit: documented
request_id: soldfetch_...
SoldFetch eBay API3 request examples
View docs GET/v1/scrape?keyword=sony+wh-1000xm5&ebaySite=ebay.com&sold=false&count=60
keywordsony wh-1000xm5ebaySiteebay.comsoldfalsecount60
curl 'https://soldfetch.com/v1/scrape?keyword=sony+wh-1000xm5&ebaySite=ebay.com&sold=false&count=60' \
-H 'API-KEY: soldfetch_live_YOUR_API_KEY'Example response
{
"keyword": "sony wh-1000xm5",
"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 sold listings API compare to a self-managed integration?
SoldFetch packages eBay 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
Freshness6 hours for sold results; 15 minutes for active results; 5 minutes for empty results policy with metadataYour team owns caching and observation time
InterfacesREST, MCP, and SkillYour team maintains each adapter
Can I use eBay 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 sold listings API?
Create a SoldFetch key, send a GET request to /v1/scrape with one of the documented identifier or query presets, and read the flat JSON response.
What does the eBay sold listings API return?
Search eBay sold or active listings with price and condition filters. Optional fields remain optional, and every eBay API response includes request and freshness metadata needed for production handling.
Which eBay marketplaces support sold listings?
Use the same operation across 3 supported eBay marketplaces by passing the documented ebaySite value.
How fresh is eBay sold listings data?
This operation uses a 6 hours for sold results; 15 minutes for active results; 5 minutes for empty results 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 sold listings API with an AI agent?
Yes. The search_ebay_sold MCP tool and generated documentation expose the same allowlisted eBay operation and validation rules.
Can I use the eBay 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 sold listings details generated from SoldFetch's versioned operation catalog.
3
eBay marketplaces
6 hours for sold results; 15 minutes for active results; 5 minutes for empty results
cache policy
2
interfaces
Ready to call the eBay sold listings API?
Create a key, keep it server-side, and run the predefined eBay request in minutes.
Get an API key