LawnPro API Documentation

This is the technical reference for developers building on LawnPro. If you’re the business owner, start with The LawnPro API and send this page to your developer.

Plan availability: the Developer API and webhooks are included on the Grow and Plus plans.

Download the OpenAPI 3.1 spec

The full machine-readable spec covers every endpoint and HTTP method, request and response fields, the scope each call needs, error codes, and every webhook event with its payload.

Download the LawnPro OpenAPI spec, version 1.23.0 (zip with openapi.yaml and openapi.json)

Import it into Postman, Swagger Editor or your code generator to build a client. It replaces the PDF guides we published in August 2026. Those described API version 1.1.0, when invoices, estimates, payments and the schedule were read-only. They aren’t anymore.

Base URL

https://secure.lawnprosoftware.com/api/v1

Every response uses the same envelope: { "data": ..., "meta": { "request_id": "req_..." }, "errors": [] }. Lists are paged with page and per_page.

Authentication: Log in with LawnPro (OAuth 2.1)

There are no API keys. Apps connect with OAuth 2.1 authorization code and PKCE (S256 only).

  1. The account owner registers your app in LawnPro under Settings > Developer apps and gives you the Client ID (lp_oauth_…) and Client Secret (lp_cs_…). Up to 10 apps per account and 10 return addresses per app.
  2. Send the owner to https://secure.lawnprosoftware.com/oauth/authorize with resource=https://secure.lawnprosoftware.com/api/v1, the scopes you need and your PKCE challenge. They sign in and click Allow.
  3. Exchange the code at https://secure.lawnprosoftware.com/oauth/token. Send the client secret in the body or with HTTP Basic.
  4. Call the API with Authorization: Bearer <access token>. Access tokens last 1 hour. Use the refresh token to get a new one. A refresh token stays good as long as it’s used at least every 90 days.

Discovery: https://secure.lawnprosoftware.com/.well-known/oauth-protected-resource/api/v1. Only the account owner can click Allow, and they can disconnect your app any time under Settings > MCP, API & Integrations.

What you can read and change

Each area has a :read scope and, where changes are allowed, a :write scope. Your app only gets the scopes it registered and the owner allowed.

AreaReadChange
CustomersList, getCreate, update, delete (restorable in LawnPro)
PropertiesList, getCreate, update, delete
Items & services, item packagesList, getItems: create, update, delete. Packages: read only
InvoicesList, getCreate, update, delete, send by email or text
EstimatesList, getCreate, update, delete, send, convert to an invoice
PaymentsList, getRecord a payment you already collected. No charge, edit or delete
Schedule (visits, including recurring)List, get, filter by date, crew, address or phoneAdd, update, complete, skip, reopen, move, assign crew. No delete
Crews, event categoriesList, getRead only
EmployeesList, getAdd, update, deactivate, reactivate. No delete
To-dosList, getAdd
Expenses, vendors, text messages, lookupsList, getRead only
WebhooksList, get, delivery logCreate, update, delete subscriptions

Update endpoints accept PUT and PATCH, and only the fields you send change. Every POST accepts an Idempotency-Key header, so a retry never creates a duplicate. Sending an invoice or estimate texts or emails your customer for real.

Webhooks

Webhooks push an event to your HTTPS address the moment something happens: invoices, estimates, payments, visits, customers, reviews, to-dos and more (69 events). Each delivery is signed with HMAC-SHA256 in X-LawnPro-Signature. Failed deliveries retry after 1 minute, 5 minutes, 30 minutes, 2 hours and 6 hours. The full event list and payloads are in the spec. Setup steps: Webhooks.

Limits

  • 120 requests per minute per connection. Over that you get a 429 with Retry-After. Treat a 503 the same way.
  • Every request is locked to the one LawnPro account that allowed your app.
  • Plan matters for the two customer-risk webhook events, which need the Plus plan. Everything else on this page is the same on Grow and Plus.

API or MCP?

The Developer API is for software: your own dashboard, a sync with another system, automations that run on their own. Calls take effect right away.

MCP is for AI assistants like Claude, ChatGPT and Cursor. It’s on Startup, Grow and Plus. The assistant can look up almost anything in the account and can queue changes like creating invoices, moving visits or texting a customer. Each change waits for the owner to click Allow unless they trust that connection. MCP is meant for a person working with an assistant, not for unattended software. See Connect an AI Assistant.

Questions? Message us on help chat. If a call fails, send us the request_id from the response and we’ll trace it.

Updated on November 15, 2026
Was this article helpful?

Related Articles