Skip to main content

Your records, machine-readable

Start the 14-day trial or walk a real job in the demo

Read-only. 3 endpoints. On the Enterprise plan.

Read your own jobs, customers and invoices.

From the tools you already run. The API never writes, never moves money, and only ever answers for the company whose key you send.

Mint a key under Settings, API keys (it comes with the Enterprise plan). Keys are shown once, stored only as a fingerprint, and stop working the moment you revoke them, or the moment the plan no longer includes the API.

Send the key on every request

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

3 read endpoints.

  • GET /api/v1/jobsYour job records: name, client, address, trade, status, dates.
  • GET /api/v1/customersYour customer records: name, contact, phone, email, addresses.
  • GET /api/v1/invoicesYour 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 does not do 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.

See what connects today

Everything else the product does

Start on the app, add the API when you need it.

Ask about API access Start the 14-day trial