API Docs

Every request is authenticated with an API key from Settings → API & Developers, sent asAuthorization: Bearer sk_live_.... Requests are scoped to your organization only — a key can never see another org's data.

GET/api/v1/customers?limit=50 (max 200)

List your customers.

curl https://your-domain/api/v1/customers \
  -H "Authorization: Bearer sk_live_..."

POST/api/v1/customers

Create a customer.

curl -X POST https://your-domain/api/v1/customers \
  -H "Authorization: Bearer sk_live_..." \
  -H "Content-Type: application/json" \
  -d '{"name":"Jane Doe","email":"jane@example.com","phone":"555-0100"}'

GET/api/v1/jobs?limit=50&status=COMPLETED

List jobs, optionally filtered by status.

curl https://your-domain/api/v1/jobs?status=COMPLETED \
  -H "Authorization: Bearer sk_live_..."

GET/api/v1/appointments?limit=50

List appointments, most recent first.

curl https://your-domain/api/v1/appointments \
  -H "Authorization: Bearer sk_live_..."

This is a first, read-heavy pass at the public API (customers, jobs, appointments). More resources will be added over time — nothing here is a fabricated/planned-but-not-real endpoint.