Clients
Find, create, and keep customer records current, including addresses, tags, lead status, and service preferences.
- Search and filter
- Addresses
- Tags
Autopilot API v1
Securely read and write the core records that run your operation, then react when they change with signed webhooks.
/v1/jobs?status=Completed&limit=3{
"data": [
{ "job_number": 2048, "status": "Completed",
"totals": { "total": 1480, "amount_due": 0 } },
{ "job_number": 2047, "status": "Completed",
"totals": { "total": 875, "amount_due": 875 } }
],
"has_more": false,
"next_cursor": null
}Seventy-five documented operations cover the business records most integrations need, without turning this page into the documentation.
Find, create, and keep customer records current, including addresses, tags, lead status, and service preferences.
Create complete jobs with line items, discounts, schedule windows, and crew assignments in one request.
Build itemized estimates, schedule appointments, assign technicians, and track approval status.
Create and update invoices, inspect computed totals, and record payments collected outside the API.
React when clients, jobs, estimates, or invoices are created, updated, or deleted.
Create the job, line items, schedule window, crew assignments, and discounts together. Either the complete job is created, or nothing is.
An admin opens Settings, then API Keys.
Use the key as a Bearer token from your server.
Start with live examples, fields, filters, and errors.
curl https://app.autopilotapp.io/api/v1/jobs \
-H "Authorization: Bearer $AUTOPILOT_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"client_id": "...",
"status": "Open",
"items": [ ... ],
"schedules": [ ... ]
}'Subscribe to clients, jobs, estimates, and invoices. Each delivery is signed, carries a dedupe key, and retries when your endpoint is unavailable.
X-Autopilot-Event-Id: 67b7f6f6-4a7e-4e7f-9a20-...The boring details are handled, so your developer can focus on the workflow that makes your business better.
An admin creates each key in Settings. It is shown once, stored as a hash, records last-used activity, and is revocable.
Each company gets 100 requests per minute across its credentials, with cursor pagination up to 100 records per page.
Every non-success response follows the same error envelope with clear codes for validation, conflicts, limits, and more.
Webhook deliveries carry an event ID and HMAC-SHA256 signature, then retry on a backoff schedule when needed.
Browse every endpoint, field, filter, response, webhook event, and error before you write a line of production code.
Start with Autopilot, then connect the systems and automations that make it yours.
Want to talk to Autopilot through an AI agent? Meet Autopilot for Agents.