How to Integrate Appliance Data into Housecall Pro Using API + Webhooks
Turn every Housecall Pro job into a "smart job." When a job is created, webhooks trigger ApplianceAPI to enrich it with verified model data, specs, manuals, and recall status — before the technician arrives.
Most appliance repair workflows break at one point: missing or incomplete appliance data. A job gets scheduled, a model number is typed in (sometimes incorrectly), and the technician arrives without specs, diagrams, or parts context. This guide shows you how to fix that using Housecall Pro webhooks and ApplianceAPI for real-time job enrichment.
From Job Creation to Technician Ready
Here is the workflow you are building:
- Job is scheduled — CSR creates a job in Housecall Pro with customer info and an appliance model number.
- Webhook fires instantly — Housecall Pro sends a
job.createdevent to your webhook endpoint. - ApplianceAPI enriches the job — Your integration calls ApplianceAPI with the model number and gets back brand, specs, dimensions, manuals, parts references, and recall status.
- Job is updated — Enriched data is pushed back into the Housecall Pro job: notes updated, attachments added, custom fields populated.
- Technician opens the job — Instead of guessing, the tech sees exact appliance specs, service manual links, likely parts, and dimensional constraints.
Result: fewer callbacks, faster diagnostics, higher first-time fix rate.
Housecall Pro API Overview
Housecall Pro provides three integration mechanisms:
| Method | Access | Use Case |
|---|---|---|
| API Key | MAX or XL plans | Direct integration, job CRUD |
| OAuth | Official partners only | Marketplace integrations |
| Webhooks | MAX or XL plans | Real-time event triggers |
ApplianceAPI acts as a data enrichment layer between webhook events and your job records. No OAuth partnership required — API key authentication works for most integrations.
Step-by-Step Integration Guide
1. Generate API Key in Housecall Pro. Navigate to the App Store / Developer section in Housecall Pro settings. Generate an API key and store it securely. Confirm your plan supports API access (MAX or XL).
2. Set Up ApplianceAPI Access. Join the ApplianceAPI waitlist and get your API key. Review the available endpoints: model lookup, specs, serial decoding, recall checking.
3. Create a Webhook Listener. Build a simple endpoint (POST /webhooks/housecallpro) on your server. This receives job events, extracts the appliance model data, and triggers the enrichment logic.
4. Configure Webhooks in Housecall Pro. Set webhook triggers for: job.created, job.updated, job.started, estimate.created, and invoice.created. Each event type unlocks different automation opportunities.
5. Connect the Pipeline. Housecall Pro Webhook → Your Server → ApplianceAPI → Housecall Pro Update. This creates a closed loop where every job becomes data-rich automatically.
Webhook Use Cases
| Trigger | Action | Impact |
|---|---|---|
job.created | Fetch specs, manuals, diagrams via ApplianceAPI | Technicians start with full context |
job.started | Surface parts breakdown and likely failure components | Pre-diagnosis before opening the unit |
estimate.created | Attach dimensions, electrical requirements, compatibility | More accurate estimates, fewer revisions |
invoice.created | Append appliance details to invoice | Better documentation, reduced liability |
Advanced: Sync Parts into Pricebook
Once the basic integration is running, you can extend it to map appliance parts into Housecall Pro's Materials/Pricebook system:
- Job created, model number detected
- ApplianceAPI returns parts list (part numbers, descriptions)
- Integration checks if each part exists in your pricebook
- Missing parts are created as new material entries
- Parts are attached to the job or estimate
This evolves your system from technicians guessing parts to system-assisted diagnostics with structured parts data. Common auto-suggested parts: dryer heating elements, refrigerator ice makers, washer drain pumps.
Who Benefits Across Your Business
- CSR team: Faster job intake, model validation at entry, fewer incorrect model numbers in the system.
- Dispatch: Smarter scheduling and job prioritization based on appliance type and complexity.
- Technicians: Better first-time fix rates, reduced on-site research time, pre-loaded specs and manuals.
- Management: Cleaner job data, better reporting, fewer callbacks, measurable ROI from reduced truck rolls.
Example: Webhook → ApplianceAPI → Response
{
"brand": "Whirlpool",
"model": "WRS325SDHZ",
"category": "Side-by-Side Refrigerator",
"image_url": "https://cdn.applianceapi.com/img/...",
"confidence": "HIGH",
"dimensions": {
"height_in": 69.75,
"width_in": 35.5,
"depth_in": 34.63
},
"recall_status": "none",
"manual_available": true,
"age_estimate": {
"manufactured": 2021,
"confidence": "high"
}
}Frequently Asked Questions
What Housecall Pro plans support API access?
API key access is available on MAX and XL plans only. Lower tiers do not support direct API integrations or webhooks.
Do I need OAuth to integrate with Housecall Pro?
No. You can use API key authentication for most integrations. OAuth is only required for official partner-level marketplace integrations.
Are webhooks required for real-time enrichment?
Yes. Webhooks are what enable instant job enrichment when events happen in Housecall Pro. Without webhooks, you would need to poll the API on a schedule, which is slower and less efficient.
What data can ApplianceAPI return for each job?
Model validation, verified product photos, specs and dimensions, manuals and diagrams, parts references, CPSC recall status, serial number age estimation, and confidence scoring.
Can I use Zapier or Make.com instead of custom code?
Yes. You can route Housecall Pro events through Zapier or Make.com to ApplianceAPI. However, direct API integration provides better performance, more flexibility, and lower per-event cost.
How fast is the enrichment process?
Near real-time. From webhook event to enriched job data typically takes 1-3 seconds, depending on your server location and ApplianceAPI cache status.