FieldCampFieldCamp API Reference | FieldCamp
Build integrations with FieldCamp — create clients, jobs, and visits programmatically from your booking, scheduling, or ERP system.
The FieldCamp API lets your systems create clients, schedule jobs, and manage visits programmatically. If your booking engine, marketing site, or ERP needs to push work into FieldCamp, this is the API you integrate with.
The basics
- Base URL:
https://api.fieldcamp.ai - Authentication: JWT bearer token issued by FieldCamp support. See Authentication.
- Webhooks: not currently emitted — see Webhooks for the polling pattern.
Object model
The person or company the job is for. Created once, referenced from every job.
A unit of work scheduled on a date, assigned to a team, with line items that drive billing.
A scheduled on-site appearance for a job. A job may have one or more visits.
A product or service. Appears as a line item on jobs.
A typical integration flow:
- Create a client (or find an existing one by email).
- Create the items you'll bill (one-time setup; reuse item IDs thereafter).
- Create a job pointing at the client, with the items as line items.
- Create visits for the job (or rely on auto-generated visits from the job's start/end times).
Start here
Zero to a created job in five copy-paste steps.
Get an API key and make your first authenticated request.
Envelope format, HTTP status codes, retry policy.
Make retries safe with client-generated jobNumber values.
Things to know before you build
Three things that catch most first-time integrators:
POST /api/jobsusesmultipart/form-data, not JSON.- All datetimes are UTC ISO-8601 strings; the job's
timezoneis a display hint only. jobNumberis client-generated and must be unique. See Idempotency.