Discover/Fire Truck Mall API
live

Fire Truck Mall APIfiretruckmall.com

Access all fire truck listings from firetruckmall.com with pricing, year, specs, and image URLs. Two endpoints cover inventory and listing date approximation.

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

What is the Fire Truck Mall API?

The Fire Truck Mall API provides access to the full inventory of fire apparatus listings from firetruckmall.com across 2 endpoints, returning structured data for each truck including title, price, year, specs, image URL, and listing URL. The get_all_trucks endpoint aggregates all paginated results into a single response, filtering out non-numeric price entries so every record in the output carries a usable numeric price.

Try it

No input parameters required.

api.parse.bot/scraper/eee34a3d-ff36-46c8-83d0-b0e928e18d22/<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/eee34a3d-ff36-46c8-83d0-b0e928e18d22/get_all_trucks' \
  -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 firetruckmall-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: Fire Truck Mall SDK — browse listings and check dates."""
from parse_apis.Fire_Truck_Mall_Listings_API import FireTruckMall, InvalidImageUrls
import json

client = FireTruckMall()

# List all available trucks (internally paginated, single-page scheme).
for truck in client.trucks.list(limit=5):
    print(truck.title, truck.price, truck.year)

# Drill into one truck and use its image_url to fetch its listing date.
first_truck = client.trucks.list(limit=1).first()
if first_truck:
    # Fetch the listing date for this truck's image URL.
    try:
        result = client.truck_date_results.fetch(
            image_urls=json.dumps([first_truck.image_url]),
            max_workers=5,
        )
        print(result.total, result.dates)
    except InvalidImageUrls as exc:
        print(f"bad input: {exc}")

print("exercised: trucks.list / truck_date_results.fetch / InvalidImageUrls catch")
All endpoints · 2 totalmissing one? ·

Fetches all fire truck listings across all pages from firetruckmall.com. Returns only trucks with valid numeric prices greater than zero — skips listings with pricingType 'QUOTE' and zero-priced entries. Paginated internally (100 per page); the caller receives the full collected set. Each truck includes title, listing URL, image URL, price, year, and specs text.

Input

No input parameters required.

Response
{
  "type": "object",
  "fields": {
    "trucks": "array of Truck objects with title, listing_url, image_url, price, year, and specs",
    "total_found": "integer - number of trucks with valid numeric prices returned"
  },
  "sample": {
    "data": {
      "trucks": [
        {
          "year": 2005,
          "price": 199500,
          "specs": "Hale 1500 GPM Pump, 3000 Gallon Tank, Low Miles",
          "title": "2005 International Tandem-Axle Commercial Pumper Tanker",
          "image_url": "https://s3.amazonaws.com/00do0000000jlleea4/01t-product2/01tV100000DfglNIAR/medium_21077_9.jpg",
          "listing_url": "https://www.firetruckmall.com/AvailableTruck/21077/2005-International-Tandem-Axle-Commercial-Pumper-Tanker"
        }
      ],
      "total_found": 300
    },
    "status": "success"
  }
}

About the Fire Truck Mall API

Inventory Data via get_all_trucks

The get_all_trucks endpoint returns the complete set of fire truck listings available on firetruckmall.com at the time of the request. Each item in the trucks array includes title, listing_url, image_url, price (numeric, non-null), year, and specs. Listings priced as "Call For Custom Quote", "Held on Deposit", or any other non-numeric format are excluded — the total_found integer reflects only the count of records that passed this filter. No input parameters are required; pagination is handled internally with 100 listings per page.

Approximate Listing Dates via get_truck_dates

The get_truck_dates endpoint accepts a JSON-encoded array of S3 image URLs (the image_urls parameter) taken from get_all_trucks results, and returns a dates object that maps each URL to its Last-Modified HTTP date string, or null if the header is unavailable. The optional max_workers integer controls how many concurrent requests are issued, letting callers balance speed against resource usage. The total field confirms how many URLs were processed. This is the recommended way to approximate when a listing first appeared.

Coverage and Filtering Notes

Only listings with valid numeric prices appear in get_all_trucks output, so deposit-held or quote-only trucks are not represented in the returned count or array. The specs field surfaces the structured specification data shown on each listing. Listing dates are derived from image metadata rather than a dedicated timestamp field on the site, so they represent an approximation of when the listing was created rather than a guaranteed publish date.

Reliability & maintenanceVerified

The Fire Truck Mall API is a managed, monitored endpoint for firetruckmall.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when firetruckmall.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 firetruckmall.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
1d ago
Latest check
2/2 endpoints 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
  • Monitor new fire truck inventory by polling get_all_trucks and comparing listing URLs over time
  • Build a price-comparison tool across apparatus types using the numeric price and year fields
  • Identify recently posted listings by running get_truck_dates against image_url values from get_all_trucks
  • Filter available inventory by year range using the year field for fleet procurement research
  • Aggregate specs data across all listings to analyze common apparatus configurations on the market
  • Track price trends for specific truck types over repeated API calls using title and price fields
Pricing & limitsSee full pricing →
TierPriceCredits/monthRate limit
Free$0/mo1005 req/min
Hobby$30/mo1,00020 req/min
Developer$100/mo5,000100 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.

Frequently asked questions
Does firetruckmall.com offer an official developer API?+
No. Firetruckmall.com does not publish a public developer API or documented data feed.
What does get_all_trucks return for listings without a listed price?+
Listings with non-numeric price values — including 'Call For Custom Quote' and 'Held on Deposit' — are excluded entirely from the response. The trucks array and total_found count reflect only listings where a numeric price was available.
How accurate are the listing dates returned by get_truck_dates?+
The dates are derived from the Last-Modified header on each listing's S3 image URL, which approximates when the image file was last written. This correlates with listing creation in most cases but is not a guaranteed publish timestamp. If the header is absent, the value for that URL is null.
Does the API return sold or archived truck listings?+
Currently the API covers only active listings visible in the all-trucks inventory view on firetruckmall.com. Sold or archived vehicles are not included in the current endpoints. You can fork this API on Parse and revise it to target any sold/archive listing pages if the site exposes them.
Can I retrieve the full detail page data for an individual truck, such as extended description or contact information?+
The current endpoints return the summary-level fields available in the listing index: title, listing_url, image_url, price, year, and specs. Extended per-truck detail pages, dealer contact info, and additional description text are not currently covered. You can fork this API on Parse and revise it to add a detail-page endpoint using the listing_url values.
Page content last updated . Spec covers 2 endpoints from firetruckmall.com.
Related APIs in MarketplaceSee all →
auctiontime.com API
Search and browse equipment and truck auction listings from AuctionTime.com, view detailed information about specific auctions, filter by category and auctioneer, and track auction results by date. Access comprehensive auction data including listings, categories, and auctioneer information all in one place.
equipmenttrader.com API
Search and browse thousands of machinery listings with detailed pricing, specifications, and seller contact information. Find the right equipment for your needs by filtering inventory across Equipment Trader's marketplace.
autotrader.com API
Search Autotrader.com vehicle listings and access detailed information like pricing, specifications, and VIN data with flexible filtering options. Browse all available vehicle makes and models to refine your search across thousands of listings.
autotrader.ca API
Search vehicle listings on AutoTrader.ca and retrieve detailed information including specifications, pricing, mileage, and seller contact details. Compare listings across makes, models, and locations to support vehicle research and purchasing decisions.
autotrader.co.za API
Search and access comprehensive vehicle listings from South Africa's AutoTrader with pricing, specifications, location details, and seller information. Get everything you need to compare cars and make informed purchasing decisions, though direct seller phone numbers aren't available due to security protections.
bringatrailer.com API
Search live and historical Bring a Trailer auctions to find pricing trends, model comparisons, and detailed listing information for classic and collectible vehicles. Track auction results, compare price trends across models, and browse the complete directory of makes and models available on the platform.
tractordata.com API
Search and explore detailed tractor information including specifications, engine and transmission data, dimensions, photos, and attachments across farm and lawn tractor brands and models. Stay updated with the latest tractor news, industry shows, and test results all in one place.
autobidmaster.com API
Search and browse vehicle auction inventory with detailed lot information, filters by make, type, body style, and damage condition, plus discover featured items and auction locations. Find the perfect vehicle by accessing comprehensive inventory data and exploring popular makes and damage types across AutoBidMaster auctions.