FieldAware API
Official vendor OpenAPI document · agent-readyProductivityTask ManagementapiKey54 EndpointsREST
For Agents
Manage field service jobs, customers, contacts, assets, quotes, and invoices for dispatching mobile workforces using a token-authenticated REST API.
Use for: Find jobs scheduled for a technician this week, Create a new job for an existing customer, Get customer details by reference ID, List all assets at a specific service location
Not supported: Does not handle GPS routing, payroll, or accounting ledgers - use for field service jobs, customers, assets, quotes, and invoicing only.
The FieldAware REST API powers field service management workflows, including jobs, customers, contacts, locations, users, invoices, assets, quotes, and tasks. It exposes 54 endpoints with token-based authentication via the Authorization header. Resource paths are organised under singular nouns such as /job/, /customer/, and /contact/ with reference IDs for nested operations.
Install Jentic One Beta
Connect the FieldAware API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the FieldAware API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Ffieldaware.com%2Ffieldaware" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Ffieldaware.com%2Ffieldaware" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with FieldAware API.
Schedule jobs across time windows and assign them to field technicians
Manage customer records linked to multiple service locations
Track field assets through service history and current location
Generate quotes for prospective work and convert them to jobs
Issue customer invoices for completed jobs and track payment status
Maintain custom fields and access permits scoped per group
Use Cases
Patterns agents use FieldAware API for, with concrete tasks.
★ Field Technician Dispatch
Build a dispatch agent that lists jobs in a date window, looks up the assigned customer and location, and confirms the visit with the technician. The FieldAware API exposes /job/ with time-window filtering plus /customer/ and /location/ endpoints for the related lookups. Replaces phone-and-spreadsheet dispatching common in mid-sized field service firms.
GET /job/ for the next 7 days, group by assigned user, and return each technician's schedule with customer name and location
Quote-to-Job Conversion
Convert accepted quotes into scheduled jobs without re-entering customer or location data. The API supports /quote/ for creating and retrieving quotes plus /job/ with the same customer reference, so an agent can spawn a job from a quote in one workflow. Cuts admin overhead from 10-15 minutes per quote down to seconds.
GET /quote/{quote_ref}, then POST /job/ with the same customer_ref and a scheduled date next Tuesday
Asset Service History Lookup
Surface the full service history of an asset by joining assets with the jobs that referenced them. FieldAware models assets as first-class resources separate from customers, so an agent can answer 'when was this HVAC unit last serviced' without scanning job records manually. Critical for warranty checks and recurring maintenance scheduling.
GET /asset/{asset_id}, then list all jobs referencing that asset_id and return the most recent completion date
AI Agent Dispatch Summaries via Jentic
Through Jentic, an agent can answer end-of-day questions like which jobs are still open and which customers had service today. Jentic exposes FieldAware's job, customer, and invoice operations as discoverable tools, letting a Claude or GPT agent generate operational summaries from natural-language requests. Removes the need for custom dashboards in mid-sized field service firms.
Search Jentic for 'list jobs', filter by status open and updated today, return a summary grouped by technician
Key Endpoints
54 endpoints — the fieldaware rest api powers field service management workflows, including jobs, customers, contacts, locations, users, invoices, assets, quotes, and tasks.
METHOD
PATH
DESCRIPTION
GET
/job/
List jobs in time window
POST
/job/
Create a new job
GET
/customer/
List customers
POST
/customer/
Create a customer
GET
/contact/
List contacts
GET
/job/
List jobs in time window
POST
/job/
Create a new job
GET
/customer/
List customers
POST
/customer/
Create a customer
GET
/contact/
List contacts
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the FieldAware API by hand means sending the token in the Authorization header, pointing at api.fieldaware.net, and mapping jobs, customers, and contacts across 54 endpoints yourself. Through Jentic you install once, import the FieldAware API from the API Directory, store the token once, and your agent calls it.
Permission scoping
FieldAware's job and customer targets travel in the request body rather than as owned-resource path ids, so limit the agent to the operations it needs, such as listing jobs or creating a customer, and leave the rest out. Because you choose the allowed operations, a write like creating a job runs only if you include it.
Credential isolation
Your FieldAware token is stored once, encrypted, by your own Jentic One instance and injected at execution time. The raw Authorization header value never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'create a field service job' or 'find a customer', and Jentic returns the matching FieldAware operation with its input schema, so the agent calls it without reading the developer reference.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using FieldAware API through Jentic.
What authentication does the FieldAware API use?
FieldAware uses a token sent in the Authorization header (tokenAuth scheme). Through Jentic the token is encrypted in your Jentic One instance and never enters agent context.
Can I list jobs in a specific time window?
Yes. GET /job/ accepts time-window query parameters so an agent can pull only the jobs scheduled within a given start and end date, suitable for daily dispatch loops.
What are the rate limits for the FieldAware API?
FieldAware does not publish per-second limits in the OpenAPI spec; consult the developer reference at api.fieldaware.net/doc/reference.html for plan-specific quotas.
How do I create a job from a quote through Jentic?
Search Jentic for 'create field service job', load the POST /job/ schema, and execute with the customer_ref from the accepted quote. Run pip install jentic to start.
Does FieldAware track assets separately from customers?
Yes. /asset/ endpoints model equipment as first-class resources distinct from customer and location records, so service history can follow the asset rather than the customer.
Can the API support custom fields per organisation?
Yes. The Custom Fields resource lets you define and read organisation-specific fields on jobs and customers, useful when industry-specific data must be captured.
Can I limit what my agent is allowed to do with the FieldAware API?
Yes. Because Jentic One is self-hosted and you define the rules, you decide which FieldAware operations the agent may call, so you can allow read-only lookups like listing jobs (GET /job/) or fetching a customer (GET /customer/) while leaving writes out. FieldAware passes job and customer targets in the request body rather than as owned-resource path IDs, so a write such as creating a job (POST /job/) or a customer (POST /customer/) runs only if you include that operation in the agent's allowed set. Your stored token is injected at execution time under those same limits, so the agent can never reach operations you did not grant.
GET STARTED