quickref APIquickref.me ↗
Access hundreds of developer cheatsheets from quickref.me. List all, search by keyword, or fetch full syntax, commands, and examples for any technology.
What is the quickref API?
The quickref.me API exposes 3 endpoints for browsing and retrieving developer cheatsheets covering languages, tools, and frameworks. Call list_cheatsheets to get the full catalog with titles, slugs, categories, and tags in a single response, search_cheatsheets to filter by keyword, or get_cheatsheet to pull complete reference content — including code blocks, syntax tables, and usage notes — for any specific technology.
No input parameters required.
curl -X GET 'https://api.parse.bot/scraper/db82383b-d1e0-48e4-8697-9b32643219a9/list_cheatsheets' \ -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 quickref-me-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.
"""QuickRef.ME — browse and retrieve developer cheatsheets."""
from parse_apis.quickref_me_technology_cheatsheets_api import QuickRef, CheatsheetNotFound
client = QuickRef()
# List all available cheatsheets (capped to 5 for demo).
for sheet in client.cheatsheets.list(limit=5):
print(sheet.title, sheet.slug, sheet.categories)
# Search for a specific technology, take the first match, then drill into details.
result = client.cheatsheets.search(query="docker", limit=1).first()
if result:
detail = result.details()
print(detail.title, detail.intro)
for section in detail.sections[:2]:
print(section.title)
for sub in section.subsections[:2]:
print(sub.title, len(sub.content))
# Direct fetch by slug with typed error handling.
try:
bash = client.cheatsheets.get(slug="bash")
print(bash.title, bash.slug, len(bash.sections))
except CheatsheetNotFound as exc:
print(f"not found: {exc.slug}")
print("exercised: cheatsheets.list / cheatsheets.search / details / cheatsheets.get")
Get all available technology cheatsheets from quickref.me. Returns metadata for every cheatsheet including title, slug, intro, categories, and tags. No pagination — the full catalog is returned in one response.
No input parameters required.
{
"type": "object",
"fields": {
"count": "integer total number of cheatsheets available",
"cheatsheets": "array of cheatsheet metadata objects with title, slug, intro, categories, and tags"
},
"sample": {
"data": {
"count": 154,
"cheatsheets": [
{
"slug": "bash",
"tags": [
"script",
"shell",
"sh"
],
"intro": "This is a quick reference cheat sheet to getting started with linux bash shell scripting.",
"title": "Bash",
"categories": [
"Programming"
]
}
]
},
"status": "success"
}
}About the quickref API
Catalog and Search
list_cheatsheets returns the complete catalog in one response: an integer count and an array of cheatsheet metadata objects, each carrying title, slug, intro, categories, and tags. There is no pagination — every available entry arrives in a single call. search_cheatsheets accepts a required query string matched against cheatsheet titles, slugs, and tags. Results share the same metadata shape as the full catalog. An unmatched query returns count: 0 and an empty results array, so you can safely check the count before processing.
Full Cheatsheet Content
get_cheatsheet takes a slug — such as bash, python, docker, git, or vim — and returns the complete reference content for that technology. The response includes title, intro, slug, and a sections array. Each section has a title and a subsections array containing typed content blocks: code, text, list, or table. This lets you render or index a cheatsheet programmatically with clear structural boundaries between commands, explanations, and examples.
Data Coverage
Slugs are stable identifiers tied to specific technologies. You can discover valid slugs either from the slug field in list_cheatsheets results or by running a keyword through search_cheatsheets before calling get_cheatsheet. The categories and tags fields on each metadata object let you group cheatsheets by technology domain (e.g., databases, shell tools, web frameworks) without fetching full content for every entry.
The quickref API is a managed, monitored endpoint for quickref.me — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when quickref.me 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 quickref.me 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 an in-editor command lookup tool that fetches Git or Vim syntax blocks from
get_cheatsheeton demand - Index all cheatsheet
tagsandcategoriesfromlist_cheatsheetsto power a technology taxonomy browser - Implement a documentation search widget that queries
search_cheatsheetsand surfaces matchingintropreviews - Generate static reference pages for internal wikis by iterating the full catalog and fetching each cheatsheet's
sections - Filter the catalog by
categoriesto surface only database or DevOps cheatsheets in a focused developer portal - Power a CLI tool that accepts a technology name, resolves it via
search_cheatsheets, and prints relevantcodeblocks
| 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 quickref.me have an official developer API?+
What does `get_cheatsheet` actually return beyond the intro text?+
sections array where each section has a title and a subsections array of typed content blocks. Block types include code, text, list, and table, matching the structured layout of the reference page for that technology. This makes it straightforward to extract only code examples or only tabular data from a cheatsheet.Does `list_cheatsheets` support filtering or pagination?+
categories, tags, or title fields. If you need server-side keyword filtering, search_cheatsheets covers that with its query parameter.Can I retrieve individual subsections or content blocks without fetching the entire cheatsheet?+
get_cheatsheet returns the full sections array for a technology in one response; there is no endpoint to request a single section or block by name. You can fork this API on Parse and revise it to add a scoped endpoint that filters sections by title or block type.Are user-contributed or community cheatsheets covered, and how current is the content?+
list_cheatsheets results once the catalog is updated; there is no change-notification or diff endpoint. You can fork the API on Parse and revise it to add a polling or versioning mechanism if freshness tracking is a requirement.