Developers · API Docs

Reference docs that live alongside the API itself

Reference documentation, worked examples and a changelog live alongside the API itself, so a developer integrating against CRMLeaf isn't working from a wiki page that's fallen out of date.

Start Free Trial →Book a 30-min Demo
  • ✓Free trial
  • ✓No credit card
  • ✓Free onboarding
API reference · LeadsWorked example
  • GET/api/leads
  • POST/api/leads
  • GET/api/deals/{id}
{
  "data": [
    { "id": 2291, "name": "Priya Shah",
      "status": "qualified" }
  ],
  "meta": { "page": 1, "total": 148 }
}

Changelog

  • Sep 2026Added stage filter to deals list
  • Aug 2026Leads endpoint returns owner details

What's included

Everything you need to integrate

Endpoint reference

Reference documentation with worked examples for each endpoint.

See how it works

Changelog

A changelog tracking API changes over time, so breaking changes don't surprise you.

See how it works

Kept alongside the API

Docs live next to the API itself rather than in a separate wiki that can drift out of date.

See how it works

In detail

Getting started

Start with a personal access token, scoped to read-only if you're just exploring, then work through the endpoint reference and worked examples here.

  • REST API
  • Sanctum
  • Changelog

Built in

  • Endpoint reference with worked examples
  • A changelog tracking API changes over time
  • Kept current alongside the API itself
FAQ

Frequently asked questions

Related

Explore further

API Tokens

Scoped credentials for API & MCP

Webhooks

Outbound & inbound event delivery

Public API (mTLS)

Machine-to-machine access

Developers hub

All developer & API surfaces

Start building against the CRMLeaf API

Issue a token and work through the reference docs and worked examples.

Start Free Trial →Book a 30-min Demo