Category search
Category search for resale research.
Retrieve structured eBay listing observations with explicit limits and source context.
Why it matters
Stable context makes eBay data usable.
Listing prices need context. Compare condition, shipping, currency, and product identity before treating an observation as a comparable.
POST /api/graphql
operation: category
variables: {
"categoryId": "112529",
"ebaySite": "ebay.com",
"count": 200
}Built in
The useful parts ship with the contract.
1. Bounded requests
One upstream page, up to 200 results. Each successful request consumes one unit.
2. Explicit price meaning
Prices represent displayed listings. Hidden accepted-offer amounts remain unknown.
3. Source context
Keep condition, shipping, currency, source URL, and observation time with the record.
Production workflow
Start with the contract, then verify with live data.
Use the docs or the public playground for a bounded call, inspect cache and request metadata, then move the same operation into production with an organization key.
FAQ
Questions about category search
Does this use the same API as the dashboard playground?
+
Yes. Public pages, customer playgrounds, REST, MCP, and the agent Skill resolve through the same canonical operation services.
How is freshness represented?
+
Endpoint-specific cache windows are explicit, and successful responses surface cache state, fetched-at time, request ID, and usage metadata.
Do retries cost additional units?
+
No. Customer units follow successful operations. Provider retries and internal fan-out are SoldFetch implementation details.
Next step
Start building with Category search
Open the documentation, choose a known-good sample, and move the same typed operation into your product.