[Cotlet](https://cotlet.dev/index.md) · [All integrations](https://cotlet.dev/integrations.md) · [MCP servers](https://cotlet.dev/integrations/mcp.md) · [APIs](https://cotlet.dev/integrations/api.md) · [API & MCP status](https://cotlet.dev/api-status.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Security](https://cotlet.dev/security.md) · [Custom API](https://cotlet.dev/custom-api.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# Create your own PestPac API

> PestPac: API access from WorkWave with a setup fee and usage costs. With Cotlet you build your own: do a job once with your AI agent, save it as an endpoint and call it from n8n or code.

Source: https://cotlet.dev/integrations/api/pestpac

PestPac: WorkWave sells API access with a one-time setup fee and costs by data access and daily calls (checked 20 Nov 2026). With Cotlet you can build your own. Do a job once with your AI agent in your PestPac account, save it as an endpoint, and call it from n8n, Make, Zapier or your own code. Each endpoint runs in your own signed-in PestPac session and returns only what your login can see.

[Try it free now](https://cotlet.dev/app/signup?app=pestpac)

Free 7-day trial, 2,000 credits, no card

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by PestPac. PestPac is a trademark of its owner. If PestPac's own integrations cover what you need, use them first.

curl Node.js Python

curl

```
curl -X POST "https://cotlet.dev/api/v1/custom/service-orders-for-day" \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"date": "2026-11-21"}'
```

Node.js

```
const url = "https://cotlet.dev/api/v1/custom/service-orders-for-day";
const res = await fetch(url, {
method: "POST",
headers: {
Authorization: `Bearer ${process.env.COTLET_API_KEY}`,
"Content-Type": "application/json",
},
body: JSON.stringify({ date: "2026-11-21" }),
});
const { data } = await res.json();
```

Python

```
import os
import requests

key = os.environ["COTLET_API_KEY"]
res = requests.post(
"https://cotlet.dev/api/v1/custom/service-orders-for-day",
headers={"Authorization": f"Bearer {key}"},
json={"date": "2026-11-21"},
)
data = res.json()["data"]
```

Response 200 OK · JSON

```
{
"data": [
{
"time": "08:00",
"technician": "Mike",
"location": "Oak St",
"service": "Quarterly pest",
"status": "scheduled"
},
{
"time": "10:00",
"technician": "Mike",
"location": "Hill Rd",
"service": "Termite inspection",
"status": "scheduled"
}
]
}
```

01 Build

## How do you build a PestPac endpoint with Cotlet?

1. 01  
login.pestpac.com  
Signed in  
### Sign in to PestPac in your Cloud Browser.  
You type your password yourself. Cotlet keeps the signed-in session, encrypted, never the password.
2. 02  
List tomorrow's service orders with the technician, time, location and service.  
### Do the job once with your agent.  
For example: "List tomorrow's service orders with the technician, time, location and service."
3. 03  
Save endpoint  
Name  
service-orders-for-day  
Input  
date  
Returns  
time, technician, location, service, status  
### Save it as an endpoint.  
Give it a name, choose its inputs, such as a date or a technician, and the fields it returns.
4. 04  
$ POST /api/v1/custom/service-orders-for-day  
200 OK  
### Call it with your Cotlet API key.  
Each endpoint gets its own address, `POST https://cotlet.dev/api/v1/custom/<name>`. You send JSON in and get JSON back, from the same signed-in PestPac session.

02 Endpoints

## Example endpoints you could build for PestPac

Cotlet ships no fixed list of PestPac endpoints. You decide which endpoints you build and what each one returns.

- POST `/api/v1/custom/service-orders-for-day`  
### Service orders for a day  
Time, technician, location, service and status for each order
- POST `/api/v1/custom/unscheduled-orders`  
### Unscheduled orders  
Orders without a date, with the location and service
- POST `/api/v1/custom/overdue-invoices`  
### Overdue invoices  
Invoice, customer, amount and days overdue
- POST `/api/v1/custom/location-details`  
### Location details  
Contacts, notes and last service for a location
- POST `/api/v1/custom/move-service-order` writes  
### Move a service order  
The order you name, moved to another technician or time
- POST `/api/v1/custom/<name>`

A call to an endpoint you built could look like this:

Request

```
curl -X POST "https://cotlet.dev/api/v1/custom/service-orders-for-day" \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"date": "2026-11-21"}'
```

The answer is JSON, with your fields under `data`:

Response · 200 OK

```
{
"data": [
{
"time": "08:00",
"technician": "Mike",
"location": "Oak St",
"service": "Quarterly pest",
"status": "scheduled"
},
{
"time": "10:00",
"technician": "Mike",
"location": "Hill Rd",
"service": "Termite inspection",
"status": "scheduled"
}
]
}
```

When you save an endpoint, Cotlet gives you its curl example and an OpenAPI description to paste into n8n, Make or your code.

03 Uses

## What can you use your PestPac endpoints for?

- Schedule Cotlet endpoint Slack or email  
### A morning dispatch list in n8n or Make.  
Today's routes and unscheduled orders, sent to Slack or email before the trucks leave.
- Website form endpoint service order  
### A booking form on your website.  
A new inspection request saved as a service order for the office to confirm.
- Schedule endpoint Google Sheets  
### A collections sheet.  
Overdue invoices pulled into Google Sheets each week.
- Voice or chat agent endpoint next visit  
### Your own AI receptionist.  
A voice or chat agent that checks a customer's next visit before it answers a call.

04 Access

## What can an endpoint see and change?

An endpoint works in your own PestPac session, so it can read and change only what your PestPac login can. An owner login sees the whole business. A team login sees what its permissions allow. You choose what each endpoint does when you build it.

An endpoint that changes something, such as moving a service order, first runs as a dry run: Cotlet shows you each request it would send, and nothing is sent. You allow the writes once in the Cotlet console and set a daily cap. A call over the cap fails whole, never half done.

DRY RUN · nothing sent

$ POST /api/v1/custom/move-service-order

would POST login.pestpac.com/... move the Oak St order from Mike to Dan

`move-service-order`writes

Allow writes

Daily cap 20 writes

05 Official API

## Does PestPac have an official API?

WorkWave offers a PestPac API to customers and approved developers, with a one-time setup fee and costs "dependent on data access and API calls per day" (checked 20 Nov 2026). No webhooks or MCP server were found. The full picture with sources: [Does PestPac have an API or MCP server?](https://cotlet.dev/api-status/pestpac.md)

Want ChatGPT or Claude to work in PestPac instead of code? See the [PestPac MCP server](https://cotlet.dev/integrations/pestpac-api-mcp-server.md).

1/3

Official API

Setup fee

[Full API & MCP report](https://cotlet.dev/api-status/pestpac.md)

06 Pricing

## What does it cost?

per successful call

 10 credits

when a call fails

 0

in the smallest pack

≈ 500 calls

free trial, no card

 7 days

A call to your endpoint costs 10 credits when it succeeds and nothing when it fails, with no browser minutes on top. Credits come in one-time packs from $29 for 5,000 credits, so a pack covers about 500 successful calls. The free trial gives you 2,000 credits for 7 days, no card.

## PestPac API with Cotlet: questions

### Is this an official PestPac API?

No. Cotlet is independent and not affiliated with PestPac. The endpoints you build run in your own signed-in PestPac account.

### Do I need to code?

Not to build an endpoint: you do the job once with your agent and save it. To call it, you need a tool that sends HTTP requests, such as n8n, Make, Zapier or a script.

### What happens when PestPac changes its screens?

An endpoint works while PestPac works the way it did when you built it. If PestPac changes and a call fails, you get an email. After 3 failures in a row the endpoint turns off until you rebuild it with your agent or in the console. A failed call costs nothing.

### How long can a call take?

Up to 90 seconds, and the answer can be up to 1 MB of JSON.

POST /api/v1/custom/<name>

## Build your first PestPac endpoint

Sign in once, do the job with your agent and save it as an endpoint.

[Try it free now](https://cotlet.dev/app/signup?app=pestpac)

No card. Takes about 5 minutes.

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [MCP servers](https://cotlet.dev/integrations/mcp.md) · [APIs](https://cotlet.dev/integrations/api.md) · [API & MCP status](https://cotlet.dev/api-status.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md) · [Custom API](https://cotlet.dev/custom-api.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. [About us](https://cotlet.dev/about.md)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.
