The Housecall Pro API, Endpoint by Endpoint, for Owners Who Will Never Read It

One line on the pricing page, and everything hanging from it

Start with the gate. Housecall Pro's help center says "API is available only to Pros on a MAX plan," and its pricing page puts Max at $299 a month billed annually, $329 month to month, as of November 2026. Webhooks carry the same condition. If your shop is on Basic or Essentials, the rest of this page describes what you would gain by moving up, and our Housecall Pro integration hub describes what you can do without it.

The second fact is about people. Only Admin users can generate or delete keys, under My Apps, then All Apps, then API Key Management. Each key gets a name and one of two permissions: Full access or Read-only. Housecall Pro is blunt about the stakes, warning that a key is "essentially giving them access to _all_ of the data in your Housecall Pro account." It is equally blunt about support: it cannot build or maintain custom integrations created with API keys and does not give dedicated support on API requests. The developer you hire owns the result.

Keys, tokens and the header that has to be exactly right

Housecall Pro's authentication page describes two methods. A Pro, or a developer working for one, uses an API key. OAuth 2.0 is "available exclusively for official integration partners," the companies that build apps for many Housecall Pro customers. A website for one shop uses a key.

• Every request goes to https://api.housecallpro.com with the key in the Authorization header, written as the word Token followed by the key. The docs stress the exact format.
• A multi-location account can use one key across locations: GET /company lists the location IDs, and an X-Company-Id header picks the location for each request.
• A key reaches its own location and the locations beneath it, never a parent or a sibling, so a branch key cannot read headquarters.
• A key lives on a server. Put one in browser code and every visitor can read your whole customer list.

Can the API do this? Twelve questions, straight answers

These rows come from the operations listed in Housecall Pro's v1 reference as of November 2026. A yes means an operation exists; it does not mean every field you want is on it, so a real project checks the schema for each one.

The reference also covers checklists, employees, job types, materials and price forms, service zones, routes, pipeline statuses, tags and an events feed. Those matter more to dashboards than to websites. For the booking side in practice, see Housecall Pro online booking; for forms, the lead forms guide.

Signed webhooks from forty-one moments in a job's life

Polling, asking the API every few minutes whether anything changed, is the fallback when a platform cannot call you. Housecall Pro can. An Admin turns on the Webhooks app under My Apps, enters the address that should receive events, saves, and Housecall Pro returns a signing secret. Then you choose events. The help article lists 41 of them.

Every event carries Api-Timestamp and Api-Signature headers. The webhooks page says to join the timestamp, a period and the JSON payload, compute an HMAC with SHA256 using the signing secret, and compare. We do that on every event and drop anything that fails. Each payload also names its event, its company ID and when it occurred. The docs do not describe a retry schedule, a timeout or event ordering, so our listener answers at once, ignores repeats and does the real work afterward.

Gaps in the documentation, and how a careful build covers them

Every API has a back room nobody photographs. Here is Housecall Pro's, as far as its public pages show in November 2026, and what we do about each gap.

• No published rate limit. We found no number in the help center or the reference. We queue writes, pace bulk reads and back off on any refusal rather than guess a ceiling.
• No sandbox described. Testing runs in your live account under a test lead source and labeled test customers that a named person cleans up the same day.
• No messaging endpoint. A website text-back goes through your own provider, with consent captured on the form, and Housecall Pro's own texting stays separate.
• Invoices are read-only. The website can show or report on invoices but not create them; billing stays in Housecall Pro.

The changelog shows an API under active work. In 2026 alone it added pipeline status updates (February 3), real service durations in Booking Windows (February 18), a lost date on leads (March 3), totals and conversion links on leads (August 4), time zones on schedules (August 20) and an approval timestamp on estimate options (August 26). An integration should be written to tolerate new fields, because they keep arriving.

Getting a key and scoping an API project in six steps

1. 1

   Confirm the plan

   Check that the account is on Max, or decide whether the website work justifies moving up. Ask Housecall Pro about anything plan-related in writing.

2. 2

   Write down the jobs to be done

   Create leads from forms, read booking windows, react to paid jobs. Each item becomes a list of operations and events.

3. 3

   Pick the permission

   Full access if the site writes anything; Read-only for a reporting project. Ask for the narrower one whenever it will do.

4. 4

   Generate the key as an Admin

   My Apps, All Apps, API Key Management, Generate API Key. Name it for the project so you know what to delete later.

5. 5

   Deliver it safely

   Send the key through a password manager or a one-time secret link, never in plain email. It goes straight into server settings.

6. 6

   Agree the field map and the test plan

   Which form field fills which Housecall Pro field, which lead sources exist, and how test records are labeled and removed.

How we build on it, and what it costs

Our API integrations method is the same on every platform: the field map comes before code, every lead is checked on the server, keys never reach the browser, failed sends are queued and retried, writes are idempotent so a retry never doubles a record, and the log is written for the office, not the developer. On Housecall Pro that means searching customers before creating them, verifying every webhook signature, and storing Housecall Pro IDs beside the website's own records.

The same discipline runs through HomeService WebApp, a contractor command center whose API layer syncs jobs and estimates both ways with ServiceTitan; it shows the work, though it does not touch Housecall Pro. API work on an existing site starts at $575, depending on complexity, after a free review, and a two-system connection typically goes live the same day. A new site with one custom integration included starts at $1,500 on our pricing page, with 0% financing and hosting and maintenance from $55 a month.

If you are comparing platforms first, our ServiceTitan, Housecall Pro and Jobber comparison covers the website side of all three, and the Jobber API guide is this page's counterpart. When the question is attribution, read the Housecall Pro marketing attribution guide. Or start with a free site audit and a call to (210) 346-0848.