FieldRoutes APIUnofficial reference
The FieldRoutes API, documented end to end and testable in the browser.
40 resources, 171 endpoints, and every documented parameter and response field, harvested from the official reference and paired with a request playground that runs without a backend.
curl -X POST 'https://acme.pestroutes.com/api/customer/search' \
-H 'Content-Type: application/x-www-form-urlencoded' \
--data-urlencode 'dateUpdated={"operator":">","value":"2026-03-01 00:00:00"}' \
--data-urlencode 'includeData=1' \
--data-urlencode 'authenticationKey=<your-key>' \
--data-urlencode 'authenticationToken=<your-token>'https://{subdomain}.pestroutes.com/api/{resource}/{operation}
Key and token, every call
Two long-lived credentials travel as parameters on each request. There is no OAuth handshake and no bearer header.
Search, then get
Search endpoints hand back primary keys. Get endpoints resolve those keys into full records, 1,000 at a time.
One host per tenant
Each account calls its own subdomain. The product is FieldRoutes; the API host is still pestroutes.com.
Office-scoped keys
A single-office key carries an implied officeIDs filter. Global keys may target any office explicitly.
Resource map
Grouped by the part of the business each resource belongs to.
Customers & Sales
Field Operations
Getting a keyset
Credentials are issued by FieldRoutes, not self-served. Ask your account contact or write to apisupport@fieldroutes.com for a key, a token, and confirmation of whether the key is office-scoped or global. Default throughput is 3,000 reads and 3,000 writes per office, capped at 60 per minute; higher limits are granted case by case.
This site is an independent reference built from the official documentation at fieldroutes.dev.