Fatfingers APIfatfingers.com ↗
Discover misspelled product listings on eBay across multiple domains to find bargains with less competition from other bidders. Get direct search URLs for common typos of items you're looking for, giving you an edge in finding deals that others miss.
curl -X GET 'https://api.parse.bot/scraper/170d8bd8-13da-4742-9406-09b6841744f3/find_typo_bargains?ebay_site=us&product_name=iphone' \ -H 'X-API-Key: $PARSE_API_KEY'
Given a product name, generates common misspellings and typos that sellers make on eBay listings, and returns search URLs for those misspellings across one or all supported eBay regional domains. Each domain may produce different typo variations. The endpoint makes one request per queried domain (up to 16 if no site filter is specified), so specifying ebay_site reduces latency. Results include the full typo search query and the individual misspellings extracted from it.
| Param | Type | Description |
|---|---|---|
| ebay_site | string | eBay regional site to query. When omitted, returns results for all 16 supported eBay domains. |
| product_namerequired | string | The product name to find misspellings for (e.g. 'iphone', 'nintendo', 'samsung'). Max 50 characters. |
{
"type": "object",
"fields": {
"results": "Array of typo search results per eBay domain, each containing site key, domain, search_url, typo_query, and misspellings array",
"total_sites": "Number of eBay domains that returned results",
"product_name": "The queried product name"
},
"sample": {
"data": {
"results": [
{
"site": "us",
"domain": "www.ebay.com",
"search_url": "https://www.ebay.com/sch/i.html?_nkw=(i+phone,+phone)+-iphone&mkcid=1&mkrid=711-53200-19255-0&siteid=0&campid=5338784378&customid=&toolid=10001&mkevt=1",
"typo_query": "(i phone, phone) -iphone",
"misspellings": [
"i phone",
"phone"
]
}
],
"total_sites": 1,
"product_name": "iphone"
},
"status": "success"
}
}About the Fatfingers API
The Fatfingers API on Parse exposes 1 endpoint for the publicly available data on fatfingers.com. Calls return JSON over HTTPS and are billed per successful response.
Pin a release with the API-Snapshot-Version header so canonical updates don't silently change your contract.