FieldRoutes API Guide for Pest Control Operators

One-line verdict: A documented API with real reads and writes — sized for one office at a time unless you ask for the bigger key. Openness: 3 / 5 — rated 3 because FieldRoutes publishes developer documentation with key-and-token access and documented limits, but keys are office-scoped by default, results are capped, and the entity-level detail could not be verified from the vendor’s own pages.

The connection that works

Rung 1 — Direct connection. FieldRoutes (the platform formerly known as PestRoutes, now a ServiceTitan company) publishes API documentation at its developer site, covering individual endpoints, examples, and FAQs. Sign-in uses an authentication key and token passed with each request — no OAuth flow is documented. Two scoping facts from the vendor’s own docs shape every build: each key belongs to one office by default, with an implied office filter on reads and an office stamp on writes; a global key that can see every office exists, but you have to be given one. And each key carries its own distinct read/write limits — keys can be grouped into a shared pool, again by request.

The documented shape of the API is search-and-get: search endpoints return up to 50,000 IDs at a time (you page by filtering past the last key), and get endpoints return up to 1,000 entities per call. Reads and writes both exist at that pattern level — the vendor docs describe read requests and write requests with office scoping on both.

Now the honest limit of this page: FieldRoutes’ endpoint-level documentation is published in a format our review tools could not extract page by page, so the entity-by-entity table — which of customers, appointments, subscriptions, invoices, and payments can be read or written — is UNVERIFIED below rather than filled in from third-party integration clients, which this directory does not count as evidence. What is verified comes from the vendor’s documentation front door and pricing page: the vendor lists “Premium API” as a feature on both its Growth and Corporate packages.

Bridge apps: no native FieldRoutes app was found on Zapier or Make. The direct API is the only verified road in or out.

Can automate

• Office-by-office data pulls — a builder can search and retrieve records under a key scoped to one office, sized within the documented caps, for reporting, syncing, or a customer-data cleanup.
• Writes back into the same office — write requests exist in the documented pattern, stamped with the key’s office, so updates land in the right branch’s books.
• Multi-location coverage — with the right key — a global key removes the one-office filter for chains that ask for it on purpose.

Can’t automate

• An entity-level promise — UNVERIFIED. Which specific objects (customers, appointments/service visits, subscriptions, tickets, invoices, payments) can be read or written, endpoint by endpoint, could not be verified from the vendor’s extractable documentation. Any builder quoting you a FieldRoutes invoice or payment automation should show you the endpoint page first.
• Any numeric rate limit — UNVERIFIED. The vendor documents that per-key read/write limits exist, but not their values, and no per-day call allowance is vendor-verified. Figures in third-party articles were deliberately not used.
• Instant alerts — UNVERIFIED. No webhook or event catalog was extracted from the vendor’s API documentation; plan on polling-style checks.
• How you get credentials — UNVERIFIED. Whether keys are self-serve or issued by support is not stated in the vendor documentation we could read. Ask FieldRoutes directly before scoping a timeline.
• Zapier or Make automations — no native app was found on either bridge.

Hidden gate: The API key only sees one office unless FieldRoutes gives you a global key — a multi-location shop has to ask for the wider key on purpose, or its “company-wide” automation quietly covers one branch.

Build fit — what this platform supports well

• Reporting and data sync — the documented search/get pattern with generous ID caps suits scheduled pulls for dashboards and cleanup work.
• Speed-to-Lead / Estimate Follow-Up / Invoice Chase — UNVERIFIED at the entity level: the objects those builds need (leads, quotes, invoices, payments) have no verified endpoint table yet, so these stay flagged until the endpoint pages are confirmed.
• Review Engine — like every platform here, FieldRoutes has no verified reviews API (its customer portal lets customers leave a review — a product feature, not an API), so the review ask runs on our system triggered by a job-completion signal.

What this means for your shop

If you run FieldRoutes, the API is real and the shape is documented — that already puts you ahead of several platforms in this directory. The discipline is scope: confirm which office your key sees, get the global key in writing if you have more than one location, and make any builder prove the specific endpoints your automation needs against FieldRoutes’ own documentation before money changes hands.