Deliver a real endpoint and authentication flow instead of spreadsheets, ad hoc SQL dumps, or manual syncs.
Public API infrastructure for field service teams
Give every customer their own API endpoint.
Client API turns your field service platform into a clean, customer-ready integration layer. Instead of pushing customers toward sync tools or brittle exports, you can hand them a secure endpoint that exposes only the company data you intend to share.
Customer-scoped
Every endpoint is tied to one provider account and one company.
Read or write
Choose read-only access or enable controlled write workflows.
Shown once
API keys are issued once, stored hashed, and can be re-issued on demand.
GET /api/public/83f2.../query/?resource=job
Authorization: Bearer sk_live_••••••
Provider: ServiceM8
Company scope: Acme Facilities
What your customer gets
One stable endpoint, one API key, and results filtered to their assigned company.
What your team keeps
OAuth control, provider ownership, scoped credentials, and centralized visibility.
{
"provider": "servicem8",
"company_external_id": "company-uuid",
"count": 24,
"data": [ ...scoped records... ]
}
Why it exists
Built for customers who need direct access without a third-party integration stack.
Your customers still want data in their finance tools, internal dashboards, dispatch workflows, and custom reporting. This gives them a supported API surface without exposing your full provider account or forcing your team to manage one-off exports.
Each client sees only the records tied to their assigned company, reducing accidental cross-customer exposure.
Provider OAuth, token refresh, and scoped filtering stay under your control while customers build on a consistent endpoint.
How it works
Provision access in three clean steps.
Your internal team authenticates the field service platform once through OAuth.
Choose the exact company record your downstream customer should be able to query.
Share a customer-ready URL and one-time API key that powers their internal systems.
Use cases
Designed for real operational workflows.
Customers can use their endpoint to power finance reconciliations, service reporting, back-office dashboards, automation rules, and custom portals without waiting on another vendor to normalize data.
The result is a more credible platform story: your product remains the source of truth, while your customers get the flexibility to build where they already work.
Controls
Modern security posture
Scoped endpoints
One endpoint per customer company keeps access narrow and auditable.
Hashed credentials
Keys are displayed once and stored securely instead of being retrievable later.
Re-issue on demand
Rotate compromised keys without reconnecting the provider account.
Ready to launch
Turn your field service data into a customer-facing API product.
Start from the dashboard, connect your provider account, and issue the first scoped endpoint.