LawnBoss API · unofficial, by Cotlet

Create your own LawnBoss API

LawnBoss: no public API or developer docs found on lawnboss.app (checked 20 Nov 2026). With Cotlet you can build your own. Do a job once with your AI agent in your LawnBoss 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 LawnBoss session and returns only what your login can see.

Try it free now

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

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

curl
curl -X POST "https://cotlet.dev/api/v1/custom/jobs-for-day" \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"date": "2026-11-25"}'
Node.js
const url = "https://cotlet.dev/api/v1/custom/jobs-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-25" }),
});
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/jobs-for-day",
    headers={"Authorization": f"Bearer {key}"},
    json={"date": "2026-11-25"},
)
data = res.json()["data"]
Response 200 OK · JSON
{
  "data": [
    {
      "time": "08:00",
      "customer": "Hendricks",
      "address": "18 Birch Ln",
      "service": "Weekly mow",
      "crew": "Crew A"
    },
    {
      "time": "11:00",
      "customer": "Maple Court HOA",
      "address": "200 Maple Ct",
      "service": "Common areas",
      "crew": "Crew B"
    }
  ]
}

01 Build

How do you build a LawnBoss endpoint with Cotlet?

  1. Sign in to LawnBoss in your Cloud Browser.

    You type your password yourself. Cotlet keeps the signed-in session, encrypted, never the password.

  2. Do the job once with your agent.

    For example: "List the day's jobs with the customer, address, service and crew."

  3. Save it as an endpoint.

    Give it a name, choose its inputs, such as a date or a crew, and the fields it returns.

  4. 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 LawnBoss session.

02 Endpoints

Example endpoints you could build for LawnBoss

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

  • POST /api/v1/custom/jobs-for-day

    Jobs for a day

    Time, customer, address, service and crew for each job

  • POST /api/v1/custom/past-due

    Past-due invoices

    Customer, amount and days unpaid for each invoice

  • POST /api/v1/custom/crew-hours

    Crew hours

    Hours and overtime per crew member for a week

  • POST /api/v1/custom/unbilled-jobs

    Finished jobs not invoiced

    Completed jobs with no invoice yet

  • POST /api/v1/custom/add-job-note writes

    Add a job note

    A note on a customer's job, such as a gate code

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

Request

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

The answer is JSON, with your fields under data:

Response · 200 OK

{
  "data": [
    {
      "time": "08:00",
      "customer": "Hendricks",
      "address": "18 Birch Ln",
      "service": "Weekly mow",
      "crew": "Crew A"
    },
    {
      "time": "11:00",
      "customer": "Maple Court HOA",
      "address": "200 Maple Ct",
      "service": "Common areas",
      "crew": "Crew B"
    }
  ]
}

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 LawnBoss endpoints for?

  • Schedule Cotlet endpoint Text or chat

    Tomorrow's jobs for each crew.

    Each crew lead gets the jobs for tomorrow by text or chat.

  • Schedule endpoint Slack

    Unpaid invoices in Slack.

    Invoices more than 30 days unpaid, posted for the office every Monday.

  • Schedule endpoint Google Sheets

    Crew hours in a sheet.

    Hours and overtime pulled into Google Sheets for payroll each week.

  • Voice agent endpoint next job

    Your own AI receptionist.

    A phone agent that reads a caller's next job and balance before it answers.

04 Access

What can an endpoint see and change?

An endpoint works in your own LawnBoss session, so it can read and change only what your LawnBoss 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 adding a job note, 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.

05 Official API

Does LawnBoss have an official API?

LawnBoss: no public API, developer docs or webhooks found on its features page (checked 20 Nov 2026). Its named integrations are a two-way QuickBooks sync for invoices, payments and expenses, and Stripe payments. The full picture with sources: Does LawnBoss have an API or MCP server?

Want ChatGPT or Claude to work in LawnBoss instead of code? See the LawnBoss MCP server.

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.

LawnBoss API with Cotlet: questions

Is this an official LawnBoss API?

No. Cotlet is independent and not affiliated with LawnBoss. The endpoints you build run in your own signed-in LawnBoss 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 LawnBoss changes its screens?

An endpoint works while LawnBoss works the way it did when you built it. If LawnBoss 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.

Build your first LawnBoss endpoint

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

Try it free now

No card. Takes about 5 minutes.