Your records, machine-readable

Read your own jobs, customers, and invoices from the tools you already run. Read-only today - the API never writes, never moves money, and only ever answers for the company whose key you send.

Authentication

Mint a key under Settings, API keys (it rides the Scale and Enterprise plans). Send it on every request:

curl https://flpermitpay.com/api/v1/jobs \
  -H "Authorization: Bearer flpp_pat_..."

Keys are shown once at mint, stored only as a fingerprint, and die the moment you revoke them - or the moment the plan no longer includes the API.

Endpoints

• GET /api/v1/jobs

  Your job records: name, client, address, trade, status, dates.

• GET /api/v1/customers

  Your customer records: name, contact, phone, email, addresses.

• GET /api/v1/invoices

  Your invoices: label, status, payment status, amount in integer cents.

Lists take ?limit= (up to 100) and ?offset=, return newest first, and carry a pagination object with the exact total. Rate limit: 60 requests a minute per key.

What it is not, yet

No writes, no webhooks, no Zapier app - those stay on the roadmap and nothing here claims otherwise. When they ship, this page says so.

Everything else the product does