How is eBay Item Details 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.
Use the eBay Item Details API to retrieve public eBay item details by item ID. Call one documented GET endpoint across 3 eBay marketplaces with the same API key, normalized JSON, and production metadata.
TL;DR
The eBay Item Details 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
Run the allowlisted eBay item details preset against the real SoldFetch backend. Parameters are predefined and validated before an upstream request is made.
Run the predefined request before writing a single line
{
"itemId": "377534750427",
"title": "Example eBay listing",
"price": "37.00",
"currency": "USD",
"ended": true,
"endedDate": "2026-10-07T22:10:49Z"
}The eBay item details operation is available through every SoldFetch interface and resolves through the same validation and normalized output contract.
Use /v1/item/{itemId} to retrieve eBay item details data without maintaining marketplace-specific acquisition, parsers, retry rules, or response adapters.
Use this API alongside 2 other SoldFetch operations without changing authentication or the documented JSON format.
Every response includes request, cache, freshness, rate-limit, and usage metadata for production decisions.
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/item/377534750427',
params={'ebaySite': 'ebay.com'},
headers={'API-KEY': 'soldfetch_live_YOUR_API_KEY'}
)
data = response.json(){
"itemId": "377534750427",
"title": "Example eBay listing",
"price": "37.00",
"currency": "USD",
"ended": true,
"endedDate": "2026-10-07T22:10:49Z"
}eBay storefronts vary by host, currency, locale, delivery context, and available fields. SoldFetch keeps those differences behind one versioned item details contract.
3 eBay storefronts use one marketplace code, validation layer, and output contract.
Marketplace, currency, delivery context, request ID, cache state, and fetch time travel with the normalized response.
Keep one server-side API key while application code and agents use the interface that fits their workflow.
This endpoint uses a 5 min cache policy so volatility and request cost stay explicit.
curl 'https://soldfetch.com/v1/item/377534750427?ebaySite=ebay.com' \
-H 'API-KEY: soldfetch_live_YOUR_API_KEY'{
"itemId": "377534750427",
"title": "Example eBay listing",
"price": "37.00",
"currency": "USD",
"ended": true,
"endedDate": "2026-10-07T22:10:49Z"
}SoldFetch packages eBay item details acquisition, validation, normalization, caching, errors, and request metadata behind one server-side key.
Successful normalized operations consume the units defined by the active plan. Request headers make usage and rate-limit state visible to your backend.
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
Answers about this eBay API, its parameters, interfaces, freshness, and production use.
Current eBay item details details generated from SoldFetch's versioned operation catalog.
3
eBay marketplaces
5 min
cache policy
2
interfaces
Create a key, keep it server-side, and run the predefined eBay request in minutes.
Get an API key