Short answer
The Housecall Pro API is a REST API for customers, jobs, estimates, leads and the price book. A single company uses an admin-generated API key, and Housecall Pro's help center says the API is available only on the MAX plan; OAuth is reserved for official integration partners. Housecall Pro does not build, maintain or support API-key integrations. If the goal is an AI assistant working with field service data rather than a system-to-system integration, an MCP server is the faster route.
Authentication
An API key for a single company (Authorization: Token), generated by an admin in the app with full or read-only permission. OAuth 2.0 is available only to official integration partners, approved by email.
Getting access
- Housecall Pro's Help Center states the API is available only on the MAX plan, and only admins can generate keys.
- Apps serving many companies need verified Integration Partner status.
- Housecall Pro does not build, maintain or give dedicated support for API-key integrations.
- Partner fees: not published.
What you can reach
- Customers and addresses
- Jobs: line items, schedule, dispatch to employees, appointments, notes, attachments
- Estimates: options, approve or decline, schedule
- Invoices (read)
- Leads and lead sources
- Employees (read)
- Price book: materials, services, price forms
- Schedule and booking windows, service zones, routes, tags, job types, checklists
Webhooks, rate limits and test environment
| Housecall Pro | |
|---|---|
| Webhooks | Yes, signed with HMAC-SHA256: job events (created, scheduled, on my way, started, completed, paid, canceled), appointment, customer, estimate, lead and invoice events. |
| Rate limits | Not published as a number; single line-item writes are rate limited and the bulk endpoint is recommended. |
| Sandbox / test environment | Not published. |
Known limitations
From Housecall Pro's published documentation:
- OAuth is partner-only; everyone else uses per-company API keys
- Invoices, employees, routes, service zones and checklists are read-only in the published reference
- No delete endpoints for customers or jobs in the published reference
Building on the API versus connecting AI through MCP
If you want an integration (syncing Housecall Pro with another system), the API is the route. If you want your team to ask an AI assistant about jobs, schedules and invoices, or have it do the work, you would be building and hosting that yourself on top of the API.
Fieldproxy takes the other route: its official MCP server gives Claude, ChatGPT and Microsoft Copilot 145 field service tools directly, with scoped access and a confirm step before every change, and it can also change the software itself (fields, screens, automations) in a sandbox.
| Build on the Housecall Pro API | Fieldproxy MCP server | |
|---|---|---|
| Time to first answer in ChatGPT or Claude | Build, host and maintain a server | Add a connector and sign in |
| Auth and permissions | You implement them | Per-person sign-in, scopes, row and column limits |
| Changes to data | Raw API writes | Proposed, confirmed by a person, undoable |
| Changing the software itself | Not available through an API | Fields, screens, automations, in a sandbox |
Sources
Read from the vendor's own developer documentation on September 27, 2026. Anything the docs do not publish is marked "not published".
Fieldproxy facts on this page come from the Fieldproxy MCP reference. Competitor details are from each vendor's own documentation as of September 27, 2026; see the comparison table and sources.