June ships the Public API out of preview, a checklist change that came straight from field feedback, and a batch of fixes. Nothing here changes how you work day to day — it removes friction from things you already do.
Public API — generally available
The API is out of preview and available with the API Access add-on. Once the add-on is active, Admins create keys in Settings → API Keys.
- Read and write clients, properties, jobs, catalog, routes and invoices.
- Route-aware job creation — jobs created through the API use the same routing intelligence as the app, so each stop lands in the right place on a tech’s route.
- Live interactive docs at developers.poolservice.software, with ready-to-use samples in Shell, Ruby, Node.js, PHP and Python.
- Keys scoped per company and encrypted at rest.
Full walkthrough in the Public API guide.
Checklist items — required every N days
Until now, marking a checklist item as Required in a Custom View meant the tech had to complete it on every single visit. Some tasks don’t work that way. Backwashing filters is a weekly job, not a daily one — and an item that isn’t due yet shouldn’t block a tech from submitting the visit.
Checklist items now take an optional interval. Set “Require every 7 days” on Backwashed Filters? and the item is only required when it’s actually due.
How it works
- Open Settings → Visit Tasks & Costs → Checklist Items and click the gear icon on an item.
- Set Require every ___ days. Leave it blank or 0 to require the item on every visit.
- The interval only applies when the item is marked Required in a Custom View.
- On a visit, if the item was completed on that same property within the last N days, it is no longer required. It still shows on the checklist — the tech simply isn’t blocked from submitting if it’s unchecked.
- A brand-new property with no prior completions requires the item regardless of interval.
Two things deliberately did not change. The per-view Required checkbox behaves exactly as it did. And Require photo is unchanged and remains independent of the interval — an item can require a photo whether or not it’s due.
Fixes
- Route optimization no longer reorders stops that were manually pinned to a position.
- Offline visits captured across a date boundary now sync with the correct visit date.
- Invoice drafts created from a visit with zero billable items no longer generate an empty invoice.
- Notification preferences saved on mobile now persist correctly to the web app.
- Calendar Heatmap capacity percentages recalculate immediately after a job is reassigned, rather than on refresh.
- Photo uploads over slow connections retry instead of failing silently.
What to do
- If you’ve wanted PSS data in a dashboard or accounting tool, generate an API key and read the docs.
- Review your checklists — set an interval on any item that isn’t genuinely a every-visit task.
- Nothing else needs action. Fixes are already applied to your account.
June ships the Public API out of preview, a checklist change that came straight from field feedback, and a batch of fixes. Nothing here changes how you work day to day — it removes friction from things you already do.
Public API — generally available
The API is out of preview and available with the API Access add-on. Once the add-on is active, Admins create keys in Settings → API Keys.
- Read and write clients, properties, jobs, catalog, routes and invoices.
- Route-aware job creation — jobs created through the API use the same routing intelligence as the app, so each stop lands in the right place on a tech’s route.
- Live interactive docs at developers.poolservice.software, with ready-to-use samples in Shell, Ruby, Node.js, PHP and Python.
- Keys scoped per company and encrypted at rest.
Full walkthrough in the Public API guide.
Checklist items — required every N days
Until now, marking a checklist item as Required in a Custom View meant the tech had to complete it on every single visit. Some tasks don’t work that way. Backwashing filters is a weekly job, not a daily one — and an item that isn’t due yet shouldn’t block a tech from submitting the visit.
Checklist items now take an optional interval. Set “Require every 7 days” on Backwashed Filters? and the item is only required when it’s actually due.
How it works
- Open Settings → Visit Tasks & Costs → Checklist Items and click the gear icon on an item.
- Set Require every ___ days. Leave it blank or 0 to require the item on every visit.
- The interval only applies when the item is marked Required in a Custom View.
- On a visit, if the item was completed on that same property within the last N days, it is no longer required. It still shows on the checklist — the tech simply isn’t blocked from submitting if it’s unchecked.
- A brand-new property with no prior completions requires the item regardless of interval.
Two things deliberately did not change. The per-view Required checkbox behaves exactly as it did. And Require photo is unchanged and remains independent of the interval — an item can require a photo whether or not it’s due.
Fixes
- Route optimization no longer reorders stops that were manually pinned to a position.
- Offline visits captured across a date boundary now sync with the correct visit date.
- Invoice drafts created from a visit with zero billable items no longer generate an empty invoice.
- Notification preferences saved on mobile now persist correctly to the web app.
- Calendar Heatmap capacity percentages recalculate immediately after a job is reassigned, rather than on refresh.
- Photo uploads over slow connections retry instead of failing silently.
What to do
- If you’ve wanted PSS data in a dashboard or accounting tool, generate an API key and read the docs.
- Review your checklists — set an interval on any item that isn’t genuinely a every-visit task.
- Nothing else needs action. Fixes are already applied to your account.