Littleton Coin APIlittletoncoin.com ↗
Search and retrieve coin, currency, and collectible listings from Littleton Coin Company. Products, prices, SKU variants, grades, and category trees via 3 endpoints.
What is the Littleton Coin API?
The Littleton Coin Company API provides 3 endpoints to search, browse, and retrieve detailed product data from littletoncoin.com's catalog of coins, currency, and collectibles. The search_products endpoint returns paginated product summaries including price, thumbnail, part number, and attributes. The get_product endpoint exposes full SKU variant arrays with per-variant grades, prices, and images. The list_categories endpoint returns the navigable category tree used to scope product searches.
curl -X GET 'https://api.parse.bot/scraper/97b96f2d-4788-4187-bc2b-9bd39e130861/search_products?sort=0&limit=24&query=morgan+dollar&offset=0' \ -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 littletoncoin-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: LittletonCoin SDK — bounded, re-runnable; every call capped."""
from parse_apis.littletoncoin_com_api import LittletonCoin, Sort, ProductNotFound
client = LittletonCoin()
# Browse the category tree
for category in client.categories.list(limit=3):
print(category.name, category.id)
# Search for Morgan dollars sorted by price
for coin in client.product_summaries.search(query="morgan dollar", sort=Sort.PRICE_LOW_TO_HIGH, limit=3):
print(coin.name, coin.price, coin.part_number)
# Drill into full product details via the summary's navigation method
item = client.product_summaries.search(query="quarter", limit=1).first()
try:
full = item.details()
print(full.name, full.description, full.buyable)
except ProductNotFound as e:
print("not found:", e.part_number)
# Browse products within a category
cat = client.categories.list(limit=1).first()
for product in cat.products(sort=Sort.NAME, limit=2):
print(product.name, product.price)
print("exercised: categories.list / product_summaries.search / details / category.products")
Search or browse products by keyword and/or category. Returns paginated results with total count. Combine query and category_id to narrow results within a category.
| Param | Type | Description |
|---|---|---|
| sort | string | Sort order for results. |
| limit | integer | Number of results per page (max 96). |
| query | string | Free-text search term (e.g. 'morgan dollar', 'quarter'). At least one of query or category_id is required. |
| offset | integer | Number of results to skip for pagination. |
| category_id | string | Category ID to browse products within a specific category. Obtain from list_categories. |
{
"type": "object",
"fields": {
"limit": "current page size",
"total": "total number of matching products",
"offset": "current offset",
"products": "array of product summaries with id, name, part_number, price, thumbnail, url, attributes"
},
"sample": {
"data": {
"limit": 4,
"total": 227,
"offset": 0,
"products": [
{
"id": "3074457345617008264",
"url": "https://www.littletoncoin.com/shop/1921-morgan-silver-dollar-a4200ez-wc",
"name": "1921 Morgan Silver Dollar",
"type": "product",
"price": "130.0",
"buyable": true,
"currency": "USD",
"thumbnail": "https://www.littletoncoin.com/shop/api/assets/LCCCatalogAssetStore/images/catalog/products/300x300/A4200EZ_A.png",
"attributes": {
"Select a Grade": "Average Circulated or Better"
},
"part_number": "A4200EZ-wc"
}
]
},
"status": "success"
}
}About the Littleton Coin API
Searching and Browsing Products
The search_products endpoint accepts a query string (e.g. morgan dollar, quarter), a category_id obtained from list_categories, or both. Results are paginated using offset and limit (up to 96 per page), and the response includes total for calculating page counts. Each product summary in the products array carries an id, name, part_number, price, thumbnail, url, and an attributes object covering fields like year, mint, and grade. At least one of query or category_id is required per request.
Product Detail and SKU Variants
The get_product endpoint takes a part_number from search results and returns the full product record. Key response fields include description (HTML), images (full-size array), full_image, thumbnail, price, and attributes. The skus array is where per-variant data lives: each SKU entry has its own part_number, name, price, and attributes, letting you compare different grades or packaging options for the same coin within a single response.
Navigating the Category Tree
The list_categories endpoint returns categories with id, name, identifier, and a children array. Called without a parent_id, it returns the full top-level tree with immediate children. Pass a parent_id to drill into subcategories. The id values from this response feed directly into search_products as the category_id parameter, allowing you to scope product searches to specific collecting areas such as U.S. coins, world coins, or paper currency.
The Littleton Coin API is a managed, monitored endpoint for littletoncoin.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when littletoncoin.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 littletoncoin.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 coin price tracker by polling
get_productfor specific part numbers and recording thepricefield over time. - Construct a category-browsable storefront by walking the
list_categoriestree and feedingcategory_idvalues intosearch_products. - Compare grades and prices across SKU variants for a single coin using the
skusarray returned byget_product. - Feed coin catalog data into a collection management app, pulling
attributesfields like year and mint for each product. - Aggregate thumbnail images and names from
search_productsresults to build a visual coin gallery or reference guide. - Monitor new product availability within a specific category by paginating
search_productswithoffsetand trackingtotalcount changes. - Cross-reference Littleton's part numbers and prices against other numismatic sources using
part_numberas a stable identifier.
| 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 Littleton Coin Company offer an official developer API?+
What does `get_product` return beyond what `search_products` includes?+
search_products returns lightweight summaries: id, name, part_number, price, thumbnail, url, and attributes. get_product adds the full description (HTML), a complete images array, full_image, and the skus array with per-variant part_number, name, price, and attributes — useful when a single product is sold in multiple grades or sets.How does pagination work in `search_products`?+
offset and limit (max 96) parameters. The response includes a total field representing the full count of matching products, so you can calculate the number of pages and iterate using successive offset values.