API access is an account capability
A custom website flow needs permission to read and create the right records in your FieldRoutes account. The account owner requests credentials from FieldRoutes. A vendor does not receive one universal key that works for every company; credentials and authorized offices must be handled separately. FieldRoutes: API Overview (page updated Oct 16, 2026)
During an initial conversation, you only need to identify your account, office and intended workflow. Do not put a key or token in a general inquiry form. A provider should arrange a secure handoff after agreeing the scope and explain who can access the credentials.
Confirm the tier and the actual limits
The published access guide lists these per-office tiers. They are request budgets, not customer-count guarantees. Your returned API limits and FieldRoutes account team are the authority for your account. FieldRoutes: API Access (page updated Oct 13, 2026)
| Tier | Reads / day | Writes / day | Requests / minute |
|---|---|---|---|
| Free | 50 | 250 | 20 |
| Premium | 3,000 | 3,000 | 60 |
Premium also includes Trigger Rules, described as webhooks. Ask which events are available for your setup and whether the required access is already part of your subscription. Our pricing does not include a new FieldRoutes subscription or an API upgrade fee, and we have not established a universal price for either.
Map the workflow before estimating capacity
An anonymous visitor adjusting the size of a house should not require a fresh FieldRoutes request for every slider movement. A website can use an approved local pricing rulebook. Reading schedule availability, matching an existing customer and writing an enrollment require different calls and different failure handling.
Illustrative read budget · not a measured benchmark
That arithmetic ignores traffic bursts, other integrations and the variation between a short visit and a full checkout. The per-minute limit can matter long before the daily allowance is exhausted. Ask for a measured request budget, caching strategy and monitoring after a real pilot rather than a promise of unlimited users.
Check three dependencies early
- Payments: identify the actual gateway and its supported tokenization flow. A documented payment endpoint does not make every website payment method compatible.
- Scheduling: confirm which routes allow API bookings, what service durations apply and how the office wants conflicts handled.
- Agreements: choose an approved template and signing path, and verify that the completed document can be retrieved.
FieldRoutes documents gateway-dependent payment profiles, appointment creation with occupancy controls, and signed PDF uploads. Each still needs a test against the intended account and configuration. See payment profiles, appointment creation and contract creation.
Ask about failure, access and exit
An enrollment has several steps. A customer record might be created before a later payment or appointment step fails. Your provider should explain how it avoids duplicates, flags uncertain charges and gives the office a recoverable work item. Repeating every failed request automatically is not a sufficient recovery plan.
For a branded customer portal, ask how a verified visitor is authorized to see only the correct records. Shared emails and multiple properties need explicit handling. Company API credentials are not a customer login system, and we have not established a supported way to reuse FieldRoutes customer passwords.
Ask FieldRoutes about endpoint restrictions, expiration and credential replacement. Confirm what records remain in your account, what supporting data the provider keeps and how a handoff works if the relationship ends. These are practical operating questions for the written scope.
Your first conversation checklist
Bring the number of offices, existing website, API entitlement if known, gateway name, recurring plans, service coverage, agreement format and the person who handles exceptions. That is enough to begin a fit review without sharing secrets. Compare the capability map, read the native-option guide and tell us about your setup.