API Overview

The LawnLedger CRM API is a RESTful JSON API that allows you to integrate with your LawnLedger data programmatically. All endpoints are prefixed with /api/ and return JSON responses.

Base URL

https://api.lawnledgercrm.com

For local development:

http://localhost:3000

Authentication

Most API requests use cookie-based session authentication - the same session your browser holds after signing in.

There is a second path: API keys, for server-to-server integrations that have no browser session. API keys require the apiAccess feature (Business plan). New API keys are coming soon: for now no one can create one, and keys that already exist keep working. The Zapier integration is coming soon too: it opens once Zapier has its own set of key permissions. The mobile app and the customer portal each authenticate differently again, with their own tokens.

API keys

Each key carries its own permissions, picked when it was created - Read-only, or Custom from the permissions its creator holds - and the key is shown once. Send it as a bearer token:

curl https://api.lawnledgercrm.com/api/customers \
  -H "Authorization: Bearer llk_live_..."

A key reaches these endpoints, each with the permission named:

Anything else answers 403 with API_KEY_ROUTE_NOT_ALLOWED, and a listed endpoint without its permission answers 403 with API_KEY_SCOPE_MISSING (the required field names the permission). A key never does more than the person who created it can do today, and never anything an admin does - settings, your team, billing, integrations, or moving money.

Logging In

To authenticate, send a POST request to the auth endpoint:

curl -X POST https://api.lawnledgercrm.com/api/auth/sign-in/email \
  -H "Content-Type: application/json" \
  -c cookies.txt \
  -d '{
    "email": "you@example.com",
    "password": "your-password"
  }'

The -c cookies.txt flag saves the session cookie to a file. Use -b cookies.txt on subsequent requests to include it.

Authenticated Requests

curl https://api.lawnledgercrm.com/api/customers \
  -b cookies.txt

Response Format

All successful responses follow a consistent envelope format:

{
  "data": { ... }
}

The data field contains the response payload (an object, array, or primitive).

Error Responses

Errors return an error object with a message and code:

{
  "error": {
    "message": "Customer not found",
    "code": "NOT_FOUND"
  }
}

HTTP status codes:

Multi-Tenancy

LawnLedger is a multi-tenant application. All data is scoped to your organization automatically based on your session. You do not need to pass an organization ID in most requests.

Rate Limiting

API requests are rate-limited to prevent abuse. If you exceed the rate limit, you will receive a 429 response. Wait and retry after the indicated period.

Available Endpoints