FieldAware API

Name: FieldAware API API
Brand: FieldAware API
Availability: InStock

✓ Official Vendor SpecProductivityTask ManagementapiKey54 EndpointsREST

For Agents

Manage field service jobs, customers, contacts, assets, quotes, and invoices for dispatching mobile workforces using a token-authenticated REST API.

Quickstart

Get started with FieldAware API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"create a field service job"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with FieldAware API 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

GET STARTED

Start building with FieldAware API API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use FieldAware API 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 though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

FieldAware tokens are stored encrypted in the Jentic MAXsystem vault. Agents receive scoped access — the raw Authorization header value never enters the agent's context.

Intent-based discovery

Agents search by intent (e.g., 'create a field service job') and Jentic returns the matching FieldAware POST /job/ operation with its schema, so the agent calls it without reading the developer reference.

Time to first call

Direct FieldAware integration: 2-3 days for auth, ref-based ID handling, and time-window filtering. Through Jentic: under 1 hour — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Fergus API

Trades-focused job management alternative for smaller plumbing and electrical businesses

Choose Fergus for SMB trades; choose FieldAware for larger field workforces with assets.

Alternative

UpKeep API

Maintenance management alternative oriented toward facilities and equipment

Pick UpKeep when the workflow is asset-led maintenance; FieldAware leans more job-led service dispatch.

Complementary

Asana API

Project management for back-office tasks supporting field service operations

Pair with FieldAware to track non-field workflows like procurement or onboarding.

FAQs

Specific to using FieldAware API 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 MAXsystem 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.