130point API130point.com ↗
Search sold trading card prices across eBay, Goldin, Heritage Auctions, and more. Get price history, trends, and auction results via 3 endpoints.
What is the 130point API?
The 130point.com API gives developers access to sold trading card data across 6 marketplaces — eBay, Goldin, Heritage Auctions, Pristine Auction, MySlabs, and Fanatics Collect — through 3 endpoints. Use search_sold_items to retrieve card sale records including price, currency, sale type, and listing URL, or call get_price_history to pull aggregate statistics like average, median, high, and low prices alongside a directional trend indicator for any card query.
curl -X GET 'https://api.parse.bot/scraper/28d873f5-47d5-4c01-a275-e80c6b3fc610/search_sold_items?sort=EndTimeSoonest&limit=10&query=Michael+Jordan&marketplace=all' \ -H 'X-API-Key: $PARSE_API_KEY'
Full-text search over sold trading card items across multiple marketplaces. Returns card sale records with price, date, sale type, and listing URL. Results are sorted by the chosen order and optionally filtered to a single marketplace. Paginates as a single page up to the requested limit.
| Param | Type | Description |
|---|---|---|
| sort | string | Sort order for results. |
| limit | integer | Maximum number of items to return (max 1000). |
| queryrequired | string | Search query for card name/description (e.g., 'Michael Jordan', 'Pokemon Charizard PSA 10'). |
| marketplace | string | Filter by marketplace. |
{
"type": "object",
"fields": {
"sort": "string - sort order applied",
"items": "array of CardSale objects with id, price, currency, image_url, sold_via, title, url, sale_type, date",
"query": "string - the search query used",
"marketplace": "string - marketplace filter applied",
"total_found": "integer - total items found",
"items_returned": "integer - number of items in this response"
}
}About the 130point API
What the API Returns
The API aggregates sold trading card data across multiple marketplaces into a consistent response structure. Each sale record from search_sold_items includes id, price, currency, image_url, sold_via, title, url, sale_type, and date. You can filter results to a single marketplace using the marketplace parameter and control result count with limit (up to 1,000 items). Results carry a total_found count alongside the actual items_returned, so you know the full scope of matches even when limiting the response.
Price History and Trend Analysis
get_price_history computes statistics over up to 200 recent sales for any query: avg_price, median_price, high_price, low_price, and num_sales. It also returns a price_trend field — 'up', 'down', or 'stable' — derived by comparing the average price of recent sales against older ones, along with a trend_percentage showing the magnitude of that shift. An optional grade parameter (e.g. 'PSA 9', 'BGS 9.5') narrows results to a specific graded population. Each entry in the results array carries date, price, title, and source.
Auction Results with Structured Grading Metadata
search_auction_results targets auction house sales specifically and returns structured fields including card_id, title, sale_price, currency, sale_date, auction_house, grade, grading_company, and listing details. Grade and grading company are extracted from listing titles when present. You can pre-filter using the grade, grading_company (e.g. 'PSA', 'BGS', 'SGC', 'CGC'), and sport parameters before the results are paginated client-side at 25 per page across up to 8 pages from a 200-record backend pool.
The 130point API is a managed, monitored endpoint for 130point.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when 130point.com changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official 130point.com API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Building a card valuation tool that shows median and average sold prices for graded PSA or BGS cards using
get_price_history. - Tracking price trends over time for specific cards by monitoring
price_trendandtrend_percentageacross repeated queries. - Comparing auction house realized prices against eBay sold listings for the same card using
search_auction_resultsandsearch_sold_items. - Populating a portfolio tracker with current market values by querying recent sold prices per card in a collection.
- Filtering sold results by grading company (PSA, BGS, SGC, CGC) and grade to compare how certification affects sale price.
- Aggregating sport-specific auction results — basketball, baseball, football — using the
sportfilter insearch_auction_results. - Alerting users when a card's
price_trendshifts to 'up' or 'down' based on pollingget_price_history.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 200 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
| Team | $300/mo | 20,000 | 300 req/min |
| Company | $1,000/mo | 100,000 | 500 req/min |
Each endpoint has a fixed posted price per successful call — most fall between 1 and 10 credits — shown on this API's page before you run it. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does 130point.com have an official developer API?+
What does the `get_price_history` endpoint return beyond raw sale records?+
get_price_history returns both individual sale records (each with date, price, title, and source) and computed aggregate statistics: avg_price, median_price, high_price, low_price, and num_sales. It also includes price_trend ('up', 'down', or 'stable') and trend_percentage, which measure the direction and magnitude of price movement between recent and older sales within the dataset of up to 200 records.How does pagination work for `search_auction_results`?+
page parameter controls which slice you receive, with a maximum of 8 pages (pages 1–8). The total_results field in the response reflects the capped maximum of 200 available records, not the total universe of matching sales.Does the API cover active listings or upcoming auctions?+
search_sold_items returns completed sales with sold_via and sale_type fields; search_auction_results returns realized auction prices; get_price_history aggregates historical sale records. Active or upcoming listings are not included. You can fork this API on Parse and revise it to add an endpoint targeting active listing data if that fits your use case.Can I retrieve seller information or buyer details for a sale?+
title, price, currency, date, url, sold_via, and sale_type — transactional metadata about the card itself, not the parties involved. You can fork this API on Parse and revise it to surface additional listing details if the source exposes them.