MechanicalKeyboards APImechanicalkeyboards.com ↗
Access mechanical keyboard switch specs, keyboard listings, prices, availability, and customer reviews from mechanicalkeyboards.com via 7 structured endpoints.
What is the MechanicalKeyboards API?
The mechanicalkeyboards.com API exposes 7 endpoints covering the site's full catalog of keyboard switches and complete keyboards, including specs, pricing, availability, variants, and customer reviews. The get_switch_detail endpoint returns granular switch specs — actuation force, pretravel, total travel, and feel type — alongside variant-level pricing and image arrays. search_products lets you query the entire catalog by keyword across both switches and keyboards.
curl -X GET 'https://api.parse.bot/scraper/9a982982-bc27-4674-af7e-385a0e781685/get_switches?page=1' \ -H 'X-API-Key: $PARSE_API_KEY'
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 mechanicalkeyboards-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: Mechanical Keyboards Catalog — browse switches, search, drill into details and reviews."""
from parse_apis.mechanical_keyboards_catalog_api import MechanicalKeyboards, ProductNotFound
client = MechanicalKeyboards()
# Browse available switch brands
for brand in client.brands.list(limit=5):
print(brand.name)
# List switches from the catalog and inspect specs
switch_summary = client.switchsummaries.list(limit=1).first()
if switch_summary:
print(switch_summary.name, switch_summary.price, switch_summary.specs.actuation_force)
# Drill into full detail from the summary
switch = switch_summary.details()
print(switch.feel, switch.brand, len(switch.variants), "variants")
# Read customer reviews for this switch
for review in switch.reviews.list(limit=3):
print(review.author, review.rating, review.title)
# Search the catalog by keyword
result = client.searchresults.search(query="gateron", limit=3).first()
if result:
print(result.name, result.vendor, result.price)
# Get a keyboard by handle with typed-error handling
try:
keyboard = client.keyboards.get(handle="ducky-origin-vintage")
print(keyboard.name, keyboard.price, keyboard.available)
for variant in keyboard.variants[:2]:
print(variant.title, variant.sku, variant.available)
except ProductNotFound as exc:
print(f"Keyboard not found: {exc.handle}")
print("exercised: brands.list / switchsummaries.list / details / reviews.list / searchresults.search / keyboards.get")
Retrieve a paginated list of keyboard switches from the keyboard-switches collection. Each page returns up to 30 products with basic info, tags, and parsed specs (actuation force, pretravel, total travel). Use page parameter to advance through the catalog.
| Param | Type | Description |
|---|---|---|
| page | integer | Page number for pagination. |
{
"type": "object",
"fields": {
"page": "integer indicating current page number",
"products": "array of switch product objects with id, name, brand, handle, price, available, thumbnail, tags, and specs"
},
"sample": {
"data": {
"page": 1,
"products": [
{
"id": 8928336806188,
"name": "Greetech Blue 55g Clicky Switch",
"tags": [
"55g",
"blue",
"clicky"
],
"brand": "Greetech",
"price": "0.09",
"specs": {
"actuation_force": "55g actuation force"
},
"handle": "greetech-blue-55g-clicky",
"available": true,
"thumbnail": "https://cdn.shopify.com/s/files/1/0835/9706/6540/files/5298-MFPII-Greetech-Blue-Switch.png?v=1707268208"
}
]
},
"status": "success"
}
}About the MechanicalKeyboards API
Switch Data
get_switches returns a paginated list of switches from the keyboard-switches collection. Each product object includes id, name, brand, handle, price, available, thumbnail, and tags. The handle field is the slug you pass to get_switch_detail for full spec data. get_switch_detail expands that record with a specs object containing parsed fields like actuation_force, pretravel, and total_travel, plus a feel string (linear, tactile, or clicky), multiple images, and a variants array with per-variant id, title, price, sku, and available status. get_switch_brands returns an alphabetically sorted list of all vendor names currently in the switches collection — useful for building filters without iterating through paginated results.
Keyboard Data
get_keyboards returns a paginated list of complete keyboard products with name, brand, handle, price, available, and thumbnail. Passing a handle to get_keyboard_detail fetches the full record: id, tags, images, variants, and a specs object (which may be sparse for some keyboard listings). The available boolean on the detail response reflects overall in-stock status, while the variants array breaks down availability at the configuration level (e.g., layout or color variant).
Search and Reviews
search_products accepts a query string — such as 'gateron' or 'linear switch' — and an optional limit, returning matching products across the entire catalog with name, handle, price, available, image, url, and vendor. This is the fastest way to locate a handle before calling detail endpoints. get_switch_reviews accepts a handle and returns an array of review objects — each with id, author, rating, title, body, and date — plus an aggregate object containing the mean rating and total review count.
The MechanicalKeyboards API is a managed, monitored endpoint for mechanicalkeyboards.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when mechanicalkeyboards.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 mechanicalkeyboards.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?+
- Build a switch comparison tool using
actuation_force,pretravel, andtotal_travelfromget_switch_detail. - Track in-stock status for specific switches or keyboards by polling the
availablefield on detail endpoints. - Aggregate customer sentiment by collecting
ratingandbodyfields fromget_switch_reviewsacross multiple switch handles. - Populate a brand-filtered switch browser using the alphabetical list from
get_switch_brands. - Cross-reference variant-level pricing from the
variantsarray to compare per-unit switch costs across pack sizes. - Index the full catalog for search using
search_productswith brand-name queries like'cherry'or'kailh'. - Monitor price changes over time by periodically calling
get_switchesand recording thepricefield per productid.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does mechanicalkeyboards.com offer an official developer API?+
What does `get_switch_detail` return that `get_switches` does not?+
get_switches returns summary fields: id, name, brand, handle, price, available, thumbnail, and tags. get_switch_detail adds the parsed specs object (with actuation_force, pretravel, total_travel), the feel classification string, a full images array, and the variants array with per-variant sku, price, and available status.Are keycaps, cables, or other accessories covered by the API?+
get_switches and get_switch_detail) and complete keyboards (via get_keyboards and get_keyboard_detail). search_products may surface accessories as part of keyword results, but there are no dedicated listing or detail endpoints for keycaps, cables, or cases. You can fork this API on Parse and revise it to add collection-specific endpoints for those product types.How does pagination work across list endpoints?+
get_switches and get_keyboards accept an optional page integer parameter. The response includes a page field confirming the current page returned. There is no total-page-count or cursor field in the response, so you iterate by incrementing page until the products array is empty or shorter than a full page.Does `get_switch_reviews` include review filtering by rating or date?+
get_switch_reviews returns all available reviews for a given handle in a single response, along with the aggregate object. Filtering by rating or sorting by date would need to be done client-side against the returned reviews array. You can fork this API on Parse and revise it to add server-side filter parameters if needed.