Appliance Data API for Repair Software Platforms
Give your dispatch platform appliance intelligence. Model lookup, serial decoding, specs, manuals, images, and recall data — one API, clean JSON, built for FSM and field service software.
Field service software platforms handle millions of repair dispatches every year. Most of them still ask technicians to identify appliances manually — describing makes and models over the phone, looking up specs in manufacturer PDFs, checking CPSC recall pages by hand. ApplianceAPI replaces all of that with a single REST API call.
Model & Serial Lookup
Return structured appliance data from any model or serial number at job intake. Eliminate manual lookups and misidentified units.
Pre-Dispatch Enrichment
Attach verified appliance photos, specs, and recall alerts to service tickets before the truck rolls. Reduce callbacks from wrong-part dispatches.
Serial Intelligence
Decode manufacture date from serial numbers across 60 brands. Show technicians and customers how old the appliance is — critical for repair vs. replace decisions.
Manuals & Diagrams
Surface the correct service manual and parts diagram by model number. Reduce time technicians spend hunting for documentation.
Recall Alerts
Flag recalled appliances at ticket creation automatically. Protect technicians and customers without manual CPSC checking.
Normalized Across Brands
One API format for GE, Samsung, Whirlpool, LG, and 46 more brands. No per-brand parsing or special-casing in your integration layer.
The Problem Repair Software Platforms Face
Repair software platforms manage jobs, dispatch techs, and track parts — but they have a persistent data gap: appliance identification. When a customer calls in, they describe the appliance in whatever terms they know. The model number on the label gets misread, mistyped, or left blank. Technicians arrive without knowing what they are walking into.
This gap costs real money. Industry estimates put the average callback rate at 15-25%, with each failed dispatch costing $150-250 in wasted labor and truck roll. For a platform running thousands of jobs per month, that is tens of thousands of dollars in monthly waste your customers absorb — and blame on their software.
Solving this requires structured appliance data, indexed by model number, that your platform can query at job intake. That is exactly what ApplianceAPI provides.
What You Can Build With ApplianceAPI
ApplianceAPI gives your platform the data layer to build features your competitors cannot easily replicate:
- Smart job intake — validate model numbers as customers enter them, flag typos before they reach dispatch
- Technician-facing appliance cards — photo, specs, age, and manual link on the work order before arrival
- Automated recall screening — flag safety recalls at intake, document them on the job record
- Repair vs. replace guidance — show appliance age alongside repair cost estimates
- Parts pre-loading workflows — surface dimensions and spec data so parts are loaded correctly before dispatch
- Customer communication enrichment — include appliance photo and name in confirmation emails so customers trust the booking
Integration Pattern
ApplianceAPI is a REST API. The integration follows a simple webhook or on-demand pattern:
- Trigger: Job created or model number updated in your platform
- Call:
GET /api/v1/images?brand={brand}&model={model} - Store: Attach photo URL, specs, recall status, and serial data to the job record
- Display: Render enriched appliance card in the technician-facing and customer-facing views
No SDK required. Standard REST with JSON responses. Typical integration time: 2-4 hours. Works with any platform that supports HTTP calls or webhooks.
API Coverage
ApplianceAPI indexes 10,000+ models across 50+ brands including all major US market share leaders: GE (21%), LG (18%), Samsung (16%), Whirlpool (13%), and 46 additional brands. Serial number decoding covers 60 brands across 22 algorithm families.
Data is sourced from manufacturer sites, retailer pages, and government databases. Product photos are human-reviewed and confidence-scored before entering production. Missing models are automatically queued for enrichment — your coverage improves over time without additional integration work.
Before vs. After ApplianceAPI
| Capability | Without ApplianceAPI | With ApplianceAPI |
|---|---|---|
| Appliance identification | Customer describes it over the phone | Validated at model number entry |
| Technician prep | Arrives without appliance context | Photo, specs, age on work order |
| Recall screening | Manual CPSC check (rarely done) | Automatic at job creation |
| Serial intelligence | Not available | Manufacture date from serial |
| Manual lookup | Technician searches manufacturer PDF | Linked from work order |
| Coverage gaps | No fallback | Missing models auto-queued |
Frequently Asked Questions
Does ApplianceAPI work with ServiceTitan or Housecall Pro?
ApplianceAPI is a REST API that works with any platform supporting HTTP calls or webhooks. ServiceTitan, Housecall Pro, Jobber, FieldEdge, and any custom FSM platform can integrate via standard REST calls or workflow tools like Zapier and Make.
How do I get appliance photos into service tickets?
Call the ApplianceAPI images endpoint with a brand and model number when a ticket is created. The API returns a verified photo URL you can store on the job record and render in your UI.
Can I decode serial numbers via API?
Yes. The age-estimate endpoint accepts a brand and serial number and returns manufacture year, month, and confidence score. Supports 60 brands across 22 algorithm families.
What data does ApplianceAPI return?
Depending on the endpoint: product photos (confidence-scored), specifications and dimensions, model verification status, serial number decode (manufacture date), recall status from CPSC, and manual/diagram links.
Is there a free tier for testing?
Yes. A free tier is available for evaluation and development. Production access requires a paid plan. Pricing is finalized at launch — join the waitlist for early access pricing.
How quickly does the API respond?
Cached responses return in under 50ms. Uncached lookups vary by source availability. The API returns a miss status with an automatic queue entry when data is not yet available.