AllPoints FPS APIallpointsfps.com ↗
Search AllPoints Foodservice Parts & Supplies catalog via API. Retrieve product listings, pricing, images, compatibility, and stock status for parts procurement.
What is the AllPoints FPS API?
The AllPoints FPS API provides 2 endpoints for querying the AllPoints Foodservice Parts & Supplies catalog, returning product listings with pricing, images, and availability. The search_products endpoint supports keyword queries, manufacturer filtering, and model-based browsing, while get_product_details delivers full product records including equipment compatibility strings, all image variants, MPN, SKU, and stock status.
curl -X POST 'https://api.parse.bot/scraper/ede2d3fd-29f0-4c10-9846-b0ad10712c7d/search_products' \
-H 'X-API-Key: $PARSE_API_KEY' \
-H 'Content-Type: application/json' \
-d '{
"page": "1",
"sort": "scoreandvelocity",
"model": "6210",
"query": "spaceman belt",
"brand_url": "/spaceman/",
"page_size": "24",
"manufacturer": "spaceman"
}'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 allpointsfps-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: AllPoints FPS Product API — search parts, get details, filter by model."""
from parse_apis.AllPoints_FPS_Product_API import AllPoints, Sort, ProductNotFound
client = AllPoints()
# Search for belt parts with a keyword, capped at 5 results
for product in client.products.search(query="spaceman belt", sort=Sort.BEST_MATCH, limit=5):
print(product.name, product.sku, product.list_price)
# Drill into one product for full details including images and custom fields
product = client.products.search(query="drive belt", limit=1).first()
if product:
detail = client.products.get(entity_id=str(product.entity_id))
print(detail.name, detail.mpn, detail.list_price)
print("Images:", [img.url for img in (detail.images or [])])
print("Fits:", detail.fits)
# Filter by manufacturer and model
for part in client.products.search(manufacturer="spaceman", model="6210", limit=3):
print(part.sku, part.name, part.availability)
# Handle a missing product gracefully
try:
missing = client.products.get(entity_id="999999999")
print(missing.name)
except ProductNotFound as exc:
print(f"Product not found: entity_id={exc.entity_id}")
print("exercised: products.search / products.get / Sort enum / ProductNotFound error")
Search and browse products on AllPoints FPS. Supports keyword search, brand page browsing, and filtering by manufacturer or model. Returns paginated product listings with pricing, images, and availability. Use brand_url to browse a specific brand's catalog (e.g. '/spaceman/') or query for keyword search.
| Param | Type | Description |
|---|---|---|
| page | integer | Page number for pagination (1-based). |
| sort | string | Sort order for results. |
| model | string | Filter by equipment model number (e.g. '6210', '6228 (rev. 102-01-00)'). Value should be lowercase. |
| query | string | Search keyword (e.g. 'spaceman belt', 'drive belt'). When omitted, results default to browsing the brand_url page. |
| brand_url | string | Brand category URL path to browse (e.g. '/spaceman/'). Used when query is not provided. |
| page_size | integer | Number of results per page. Accepted values: 24, 48, 96. |
| manufacturer | string | Filter by manufacturer name (e.g. 'spaceman', 'berkel'). Value should be lowercase. |
{
"type": "object",
"fields": {
"products": "array of product summaries",
"page_size": "integer",
"total_pages": "integer",
"current_page": "integer",
"total_results": "integer"
},
"sample": {
"data": {
"products": [
{
"mpn": "V-A1067",
"sku": "8193511",
"url": "https://www.allpointsfps.com/8193511-belt-spaceman/",
"fits": [
"Spaceman 6455-CL (Rev. 103-01-00)"
],
"name": "Spaceman - V-A1067 - Belt",
"brand": "Spaceman",
"entity_id": 503452,
"image_url": null,
"categories": [
"General Equipment Hardware",
"Equipment Hardware",
"Equipment Parts"
],
"list_price": 39.99,
"sale_price": null,
"availability": "preorder",
"member_price": "39.99000",
"unit_of_measure": "Each",
"manufacturing_type": "OEM"
}
],
"page_size": 24,
"total_pages": 5,
"current_page": 1,
"total_results": 114
},
"status": "success"
}
}About the AllPoints FPS API
Searching the Catalog
The search_products endpoint accepts a query string for keyword searches (e.g. 'spaceman belt', 'drive belt') or a brand_url path (e.g. '/spaceman/') to browse a specific brand's catalog directly. Results can be narrowed further with manufacturer and model filters — both expect lowercase values — and paginated using page, page_size (24, 48, or 96), and an optional sort parameter. Each call returns products (an array of product summaries), alongside total_results, total_pages, current_page, and page_size for cursor management.
Product Detail Records
Once you have an entity_id from search results, pass it to get_product_details to retrieve the full product record. This includes name, brand, sku, mpn, url, in_stock status, specials, all images (each with url and alt_text), and a fits array listing compatible equipment models. The fits field is particularly useful for parts procurement workflows where you need to confirm a component matches a specific piece of commercial kitchen equipment.
Coverage and Scope
The API covers the full AllPoints FPS parts catalog accessible via their public storefront. Data spans multiple manufacturers and equipment categories in the foodservice and restaurant supply space. The manufacturer and model filters make it practical to build targeted lookups for specific equipment lines — for example, filtering on manufacturer: 'berkel' and a specific model to return only compatible parts for that unit.
The AllPoints FPS API is a managed, monitored endpoint for allpointsfps.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when allpointsfps.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 allpointsfps.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 parts lookup tool that filters by manufacturer and model to find compatible replacement components
- Sync AllPoints product listings, pricing, and stock status into an internal procurement database
- Generate equipment-specific parts catalogs using the
fitscompatibility field from product detail records - Monitor price changes for specific SKUs by polling
get_product_detailson tracked entity IDs - Power a foodservice maintenance app that surfaces in-stock parts for a technician's equipment list
- Aggregate product images and descriptions from multiple brands for a consolidated parts reference tool
| 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 AllPoints FPS have an official developer API?+
What does the `fits` field in `get_product_details` contain?+
fits field is an array of equipment compatibility strings indicating which machine models or product lines the part is designed for. It is populated per-product and can be used to verify a part applies to a specific piece of equipment before purchasing.How does model filtering work in `search_products`, and are there formatting requirements?+
model parameter filters results to parts compatible with a specific equipment model number (e.g. '6210' or '6228 (rev. 102-01-00)'). Both the model and manufacturer values must be lowercase. Passing an incorrectly cased value may return no results.