Discover/Fat Fingers API
live

Fat Fingers APIfatfingers.com

Find misspelled eBay listings across 16 regional domains. The Fat Fingers API returns typo variations and direct search URLs to surface low-competition deals.

Endpoint health
verified 2d ago
find_typo_bargains
1/1 passing latest checkself-healing
Endpoints
1
Updated
16d ago

What is the Fat Fingers API?

The Fat Fingers API exposes a single endpoint, find_typo_bargains, that accepts a product name and returns an array of common seller misspellings alongside direct eBay search URLs across up to 16 regional domains. Each result object includes the site key, domain, search_url, typo_query, and a misspellings array, giving you everything needed to query under-indexed eBay listings programmatically.

This call costs10 credits / call— charged only on success
Try it
eBay regional site to query. When omitted, returns results for all 16 supported eBay domains.
The product name to find misspellings for (e.g. 'iphone', 'nintendo', 'samsung'). Max 50 characters.
api.parse.bot/scraper/170d8bd8-13da-4742-9406-09b6841744f3/<endpoint>
Ready to send
Fill in the parameters and hit sign in to send to see live response data here.
Call it over HTTPgrab a free API key at signup
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'
Python SDK · recommended

Typed, relational, agent-ready

A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.

  • Fully typed · autocompletes
  • Objects link to objects
  • Typed errors & pagination

Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:

uv add parse-sdk
uv run parse init
uv run parse add --marketplace fatfingers-com-api

uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.

"""Walkthrough: FatFingers eBay Typo Finder — find misspelling bargains."""
from parse_apis.fatfingers_com_api import FatFingers, EbaySite, InputFormatInvalid

client = FatFingers()

# Find typo bargains for a product across all eBay domains.
report = client.typo_reports.find(product_name="nintendo")
print(f"Product: {report.product_name} — {report.total_sites} site(s) returned results")

for result in report.results:
    print(f"  [{result.site}] {result.domain}")
    print(f"    Typo query: {result.typo_query}")
    print(f"    Misspellings: {', '.join(result.misspellings)}")
    print(f"    Search URL: {result.search_url}")

# Narrow to a single eBay region for faster results.
try:
    uk_report = client.typo_reports.find(product_name="samsung", ebay_site=EbaySite.UK)
    if uk_report.results:
        first = uk_report.results[0]
        print(f"\nUK typo search for samsung: {first.typo_query}")
except InputFormatInvalid:
    print("Invalid site or product name format")

print("\nexercised: typo_reports.find (all sites / single site)")
All endpoints · 1 totalmissing one? ·

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.

Input
ParamTypeDescription
ebay_sitestringeBay regional site to query. When omitted, returns results for all 16 supported eBay domains.
product_namerequiredstringThe product name to find misspellings for (e.g. 'iphone', 'nintendo', 'samsung'). Max 50 characters.
Response
{
  "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 Fat Fingers API

What the API Returns

The find_typo_bargains endpoint takes a product_name string (up to 50 characters) and generates common typographical variations that sellers make when listing items on eBay. For each eBay regional domain, the response includes a search_url you can open directly, a typo_query string, and a misspellings array enumerating each individual variant. The top-level response also contains total_sites, indicating how many domains returned results, and echoes back the original product_name.

Regional Coverage

The optional ebay_site parameter lets you target a specific eBay domain. Omit it and the API queries all 16 supported regional eBay domains in a single call, returning one result block per domain. Different domains can produce different typo variations, so the same product name may yield distinct misspellings arrays depending on the site. The results array groups everything by domain, so you can iterate over regions or filter down to the ones relevant to your market.

Practical Behavior

Each entry in results contains a ready-to-use search_url pointing to an eBay search filtered to the generated typos. This means you can drive a browser, monitoring script, or deal-alert pipeline directly from the API response without any additional URL construction. The endpoint is stateless — every call recomputes typo variants fresh for the given product_name.

Reliability & maintenanceVerified

The Fat Fingers API is a managed, monitored endpoint for fatfingers.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when fatfingers.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 fatfingers.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.

Last verified
2d ago
Latest check
1/1 endpoint passing
Maintenance
Monitored & self-healing
Will this API break when the source site changes?+
It's built not to. Every endpoint is health-checked on a schedule with automated test probes. When the source site changes and a check fails, the API is automatically queued for repair and re-verified — that's the self-healing layer. Each API page shows when its endpoints were last verified. And because marketplace APIs are shared, any fix reaches everyone using it.
Is this an official API from the source site?+
No — Parse APIs are independent, managed REST wrappers over publicly available data. That is the point: where a site has no official API (or only a limited one), Parse gives you a maintained, monitored endpoint for that data and keeps it working as the site changes — so you get a stable contract over a source that never promised one.
Can I fix or extend this API myself if I need a new endpoint or field?+
Yes — and you don't have to wait on us. This API was generated by the Parse agent, which stays attached. Describe the change in plain English ("add an endpoint that returns reviews", "fix the price field") in the revise box on the API page or via the revise_api MCP tool, and the agent rebuilds it against the live site in minutes. Contributing the change back to the public API is free.
What happens if I call an endpoint that has an issue?+
Errors are machine-readable: a bad call returns a clean status with the list of available endpoints and a repair hint, so an agent (or you) can recover or trigger a fix instead of failing silently. Confirmed failures feed the automatic repair queue.
Common use cases
  • Build a deal-alert bot that monitors misspelled eBay listings for a watchlist of product names across multiple regional domains.
  • Aggregate search_url results from all 16 eBay domains into a dashboard for cross-regional bargain hunting.
  • Filter the misspellings array to feed into a keyword research tool tracking how often typo listings appear.
  • Power a browser extension that surfaces Fat Fingers typo links alongside standard eBay search results.
  • Automate periodic checks of typo_query variations for collectibles or rare electronics with historically low listing counts.
  • Generate a report comparing typo-listing density across eBay regional sites for a given product category.
Pricing & limitsSee full pricing →
TierPriceCredits/monthRate limit
Free$0/mo2005 req/min
Hobby$30/mo1,00020 req/min
Developer$100/mo5,000100 req/min
Team$300/mo20,000300 req/min
Company$1,000/mo100,000500 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.

Frequently asked questions
Does Fat Fingers have an official developer API?+
Fat Fingers (fatfingers.com) does not publish an official developer API or documented public endpoints. The Parse API is the structured programmatic interface available for this functionality.
What does the `find_typo_bargains` endpoint return for each eBay domain?+
For each domain, the response includes a site key, the domain string, a search_url linking directly to the eBay typo search, a typo_query string representing the combined query, and a misspellings array listing each individual variant generated for that domain.
Does the API return actual eBay listing data such as prices, item titles, or bid counts?+
No. The API returns typo-variant search URLs and misspelling strings, not eBay listing content. It does not expose item prices, titles, sold prices, or bid counts. You can fork this API on Parse and revise it to add an endpoint that fetches and returns listing data from those search URLs.
Are all 16 eBay regional domains guaranteed to return results for every product name?+
Not necessarily. The total_sites field in the response indicates how many domains actually returned results for a given query. Domains that produce no typo variants for a product name will not appear in the results array. The ebay_site parameter lets you narrow the query to a single domain if you only need one region.
Can I retrieve historical typo data or track how misspellings change over time?+
The endpoint is stateless and does not store or return historical typo data. Each call recomputes variants for the current query. Historical tracking and change detection are not currently covered. You can fork this API on Parse and revise it to add persistence or a diff endpoint against stored snapshots.
Page content last updated . Spec covers 1 endpoint from fatfingers.com.
Related APIs in MarketplaceSee all →
ebay.co.uk API
Search eBay UK listings and sold items to find products, compare prices, and view seller feedback and ratings. Access detailed item information, explore categories, and discover daily deals all in one place.
ebay.com API
Search and monitor eBay listings across any category, with support for active and completed/sold listings. Retrieve item details, pricing history, seller profiles and feedback, and category data. Filter by keyword, category, condition, seller, and sort order to support price research, market analysis, and inventory monitoring.
folksy.com API
Search and browse handmade products on Folksy by category, subcategory, or shop, and access detailed product information including pricing and availability. Discover sales and special offers while exploring artisan shops and their complete listings.
shpock.com API
Search and browse products listed on Shpock.com, view detailed listing information and seller profiles, and explore all available marketplace categories. Find what you're looking for by searching inventory, checking seller histories, and discovering related items from individual merchants.
flippa.com API
Search and browse digital assets like websites, domains, and SaaS businesses listed on Flippa's marketplace, with detailed filtering by country and listing details. Access comprehensive information on thousands of digital business listings to find investment opportunities or monitor the market.
ebay.de API
Search eBay.de listings with flexible filters to find the products you want, view detailed item information, and check seller feedback ratings to make informed buying decisions. Track sold items and monitor pricing trends across any category.
etsy.com API
Discover what shoppers are searching for on Etsy by accessing real-time trending keywords and popular search terms that can help you identify market demand and optimize your product listings. Get instant access to autocomplete suggestions and "Popular right now" trends to stay ahead of customer interests and improve your shop's visibility.
ebay.com.au API
Search active and sold eBay Australia listings to research products, analyze competitors, and view detailed listing information like pricing and performance metrics. Get market insights including demand trends and pricing data to inform your selling strategy.