Every endpoint, written out.
Generated from the live API, so it is exactly what the API accepts today: 299 operations in 42 groups, each with its parameters, request body and the permission it needs.
Groups
| Group | What it is for | Operations |
|---|---|---|
| API keys | Keys for your own systems and what each may do. | 5 |
| Ad routing | Whose campaign is whose, and the leads waiting for an owner (agencies). | 12 |
| Ad spend | What was spent per channel and campaign. | 5 |
| Agency | Clients, their teams and agency-wide views. | 27 |
| Areas | Localities leads are interested in. | 2 |
| Attribution | How leads from each channel turn into customers. | 4 |
| Automation rules | Rules that act when something happens. | 6 |
| Automations | Automation runs. | 6 |
| Billing | Plan, usage and invoices of a workspace. | 9 |
| Campaigns | Which campaign, ad set and ad each lead came from. | 4 |
| Contacts | The people behind leads: one person, one record, however many enquiries. | 11 |
| Custom fields | Extra fields on leads. | 4 |
| Dashboard | Numbers for the dashboard. | 3 |
| Files | Pictures and documents. | 2 |
| Home | What needs attention now. | 1 |
| Invitations | Inviting people to a workspace. | 2 |
| Lead sources | Where leads come from (Meta, Google, websites, WhatsApp, your own systems), their Facebook Pages, and the delivery log. | 15 |
| Leads | Create, find, assign and move leads, and log what happens on them. | 29 |
| Live updates | What changed since you last looked. | 1 |
| Message templates | Reusable messages. | 5 |
| Messaging | WhatsApp and e-mail from inside the CRM. | 6 |
| Monitor | Health and audit information for a workspace. | 6 |
| Notifications | In-app notifications. | 3 |
| Outgoing webhooks | Signed notifications of what happens in a workspace. | 10 |
| Pipelines | Stages, transitions and the board. | 15 |
| Projects | Developments and the kinds of home in them (real estate). | 12 |
| Properties | Units and listings (real estate). | 13 |
| Property matching | Properties that suit a lead. | 1 |
| Public | Endpoints that need no sign-in. | 1 |
| Push notifications | Notifications on a phone or computer. | 5 |
| Reports | Numbers for dashboards and exports. | 4 |
| Reservations | Offers, reservations and sales on units. | 9 |
| Saved views | Saved list filters. | 4 |
| Search | One box for leads, contacts and properties. | 1 |
| Shortlist | Properties shortlisted for a lead. | 4 |
| Sign-in | Sign-up, sign-in and password reset (for the app, not for API keys). | 9 |
| Tasks | Follow-ups, calls and meetings. | 10 |
| Team | People in a workspace and their roles. | 6 |
| Unit types | Kinds of home in a project. | 4 |
| Viewings | Site visits and their feedback. | 10 |
| Workspace | The workspace itself. | 2 |
| Your account | The signed-in person. | 11 |
The basics
The base URL is https://crm.anibrosdesign.com/api/v1. Send an API key as Authorization: Bearer crm_live_…. Every response is { "data": … }; lists add page.next. Errors are RFC 9457 problem documents. Read the guide for authentication, pagination, errors, idempotency, lead intake and webhooks.
Each operation names the permission it needs. A key can do only what its scopes allow, and only inside its own workspace.
Download
The same description as an OpenAPI 3.1 file (https://crm.anibrosdesign.com/api/v1/openapi.json). Import it into Postman, Insomnia or Bruno, or generate a client library for your language with any OpenAPI generator.
Something missing or unclear? Tell us.