A Pool Service API Built to Connect

Q: Is the PoolDial API secure?

PoolDial API keys are shown once, stored as hashes, and can be limited to read-only access, given an expiration date, or revoked at any time. Keys are designed for server-to-server use and should never be placed in browser or mobile app code.

Bring PoolDial into your accounting stack, reporting tools, custom automations, and AI workflows with a secure, versioned REST API.

Start Free Trial Explore API Docs

Trusted By

As Featured On

Your Operations Shouldn't Live in a Silo

Use PoolDial as your system of record while connecting the tools that make your business yours

Connect Your Stack

Move approved operational data between PoolDial and your accounting, inventory, point-of-sale, reporting, or internal systems.

Automate the Repetitive Work

Build workflows around customer updates, service logs, route stops, work orders, items needed, and other approved day-to-day actions.

Control Every Key

Create read-only or read/write keys, add an expiration date, and revoke access at any time. Full secrets are displayed only once.

Build AI Workflows

Connect approved PoolDial data to a secure server-side workflow powered by Claude, ChatGPT, or another AI platform you choose.

Secure Access

Control Every API Key

Create keys for individual integrations and see each key's access level, status, last use, and creation date in one place. Revoke access immediately when a connection is no longer needed.

PoolDial Developer settings showing scoped API keys, access levels, status, and usage

Permission Control

Set the Right Level of Access

Name the integration, choose read-only or read/write access, and optionally set an expiration date. PoolDial keeps destructive, financial, and communication actions outside the public contract.

Create API key dialog with read-only and read-write access controls

Developer Experience

Explore the Interactive Reference

Use the live OpenAPI documentation to inspect versioned endpoints for customers, properties, routes, service records, work orders, invoices, and more before writing your first request.

Open the API docs →

PoolDial Public API interactive OpenAPI documentation with customer and property endpoints

See the Public API in Action

A quick look at secure key management, access controls, and the versioned API reference

One Request. Useful Business Data.

Predictable JSON responses make it straightforward to build, test, and maintain your integration.

PoolDial API v1

Request

GET /public/v1/customers?limit=2

Authorization: Bearer
pd_live_••••••••••••••••

Response

{
  "data": [
    {
      "id": "cus_8f2a",
      "name": "Avery Rivera",
      "status": "active"
    }
  ],
  "pagination": {
    "hasMore": false,
    "nextCursor": null
  }
}

From Key to First Request

Owners and admins stay in control from the PoolDial dashboard

Create an API Key

Open Settings → Developer, name the integration, and choose read-only or read/write access.

Store It Securely

Copy the key when it appears and keep it in your server's secret manager. The complete key is never shown again.

Build Against the Docs

Use the interactive reference and OpenAPI document to make versioned requests, then revoke the key whenever access is no longer needed.

Designed for Production Connections

Operational Coverage

Work with customers, properties, equipment, technicians, route stops, service logs, work orders, items needed, services, invoices, payment records, quotes, and projects.

Predictable API Behavior

Versioned routes, consistent error objects, request IDs, cursor pagination, and idempotency support give integrations a stable contract.

Guardrails Around Sensitive Actions

Refunds, subscription management, customer deletion, outbound communications, provider credentials, and invoice or payment mutations stay outside the public API.

Room to Grow Without Breaking v1

PoolDial can add endpoints, optional fields, and filters inside v1 without renaming or removing the contract your integration relies on.

PoolDial API Questions

The practical details before you connect another system

Is the PoolDial API secure?

API keys are shown once, stored as hashes, and can be limited to read-only access, given an expiration date, or revoked at any time. They are for server-to-server use and should never be placed in browser or mobile app code.

What data can I access through the API?

The API covers approved account, customer, property, equipment, technician, route-stop, service-log, work-order, items-needed, service, invoice, payment-read, quote, and project data. See the interactive documentation for the current endpoints.

Can I connect PoolDial to ChatGPT or Claude?

Yes, through a server-side integration you control. The REST API can provide approved PoolDial data and actions to an AI workflow. Native one-click ChatGPT, Claude, and MCP connectors are not included yet.

Does the API replace Cody?

No. Cody remains PoolDial's built-in assistant in the dashboard, mobile app, and SMS. The API is for external systems and custom integrations; both use the same PoolDial business data.

Can an API key change data?

Read/write keys can perform approved operational actions. High-risk actions such as refunds, subscription management, customer deletion, outbound communications, and invoice or payment mutations are not exposed.

How often will I need to update my integration?

The v1 contract is additive: existing fields and endpoints will not be renamed or removed inside v1. You can adopt new optional fields and endpoints when they are useful to you rather than rebuilding whenever PoolDial ships a product update.

Make PoolDial Fit Your Business

Start with the complete pool service platform, then connect the systems and workflows your company already depends on.

Start Free Trial