BuilderMate exposes its CRM data over a JSON REST API at https://crm.bldrmate.com/api, authenticated with an organization API key, and pushes events to your systems through webhooks.
API: the same endpoints the BuilderMate web app uses. A key acts inside one organization only and can read and change clients, projects, quotes, invoices, tasks, appointments and more.
Webhooks: BuilderMate sends an HTTPS POST to a URL you register whenever a subscribed event happens, such as a lead being created or a client signing a contract.
Who can set this up: organization admins, under Settings → Integrations (tabs: API Keys, Webhooks).
Creating a key. An organization admin opens Settings → Integrations → API Keys and creates a key with a name and an optional expiry date. Keys look like crm_ followed by 64 hex characters. The full key is shown once, at creation; store it in a secrets manager.
Where the key can go (checked in this order):
Location
Format
Use
Header
X-API-Key: crm_...
Recommended
Header
Authorization: Bearer crm_...
Supported
What a key can access. A key belongs to the organization it was created in and to the admin who created it. Every request is limited to that organization's data.
Requests and responses are JSON; send Content-Type: application/json on every POST, PUT and PATCH. Bodies can be up to 50 MB.
IDs and paths. Every record has a numeric id, used in paths such as /api/clients/42. Fields are camelCase. Dates are ISO 8601 strings (2026-10-13T15:00:00Z) and money amounts are numbers in your organization's currency.
Pagination. Paginated lists take page (starting at 1) and limit query parameters. Most default to 10 items per page; tasks default to 5. Items are always in data, but the page counts sit in different places by endpoint:
Errors. Failures return an HTTP status and a JSON body carrying error (most endpoints) or message:
Status
Meaning
400
Missing or invalid input; the body says which field
401
No key, or an unrecognized key
403
Key inactive, expired or missing a required scope
404
The record doesn't exist in your organization (records from other organizations also return 404)
500
Server error. Some endpoints also report validation failures this way, with the details in message
Rate limits. No per-key rate limit is enforced today. For bulk loads, use the batch endpoints (projects take up to 50 per request; appointments and employees up to 100) instead of one request per record. Retry 5xx responses with exponential backoff.
The API covers 14 resource groups with 86 endpoints, all under https://crm.bldrmate.com. Paths take numeric IDs, PUT updates send only the fields being changed, and DELETE is permanent.
An organization admin opens Settings → Integrations → Webhooks and adds an endpoint with:
URL: must be https://, must resolve to a public address (private, loopback and cloud-metadata addresses are rejected) and can't contain credentials.
Events: any events from the catalog below, or * for all of them.
Headers: up to 10 custom headers sent with every delivery, typically an Authorization or API-key header your receiver checks.
Active: turn an endpoint off without deleting it.
Use Send test to deliver a webhook.test event right away and see the status your server returned. Only admins can manage endpoints, from the web app; API keys can't create or change them.
Event name from the catalog (also in the X-BuilderMate-Event header)
occurredAt
When BuilderMate sent the event (ISO 8601, UTC)
organizationName
The BuilderMate account the event came from, for receivers that serve several accounts
data
A snapshot of the record, loaded at send time
X-BuilderMate-Delivery is a unique ID per delivery; log it for support requests.
What's in data. The full record as the API returns it, with three changes:
Signatures, file contents and credentials are removed.
Internal fields (organizationId, accounting and payment-provider IDs) are removed.
Person IDs become names: createdById becomes createdByName, assignedToId becomes assignedToName, salesperson1id becomes salesperson1Name, and so on. Client and project IDs stay, so you can fetch related records through the API.
Deliveries are not signed. Authenticate them with a secret custom header (for example Authorization: Bearer <long random value>), and reject any request where it doesn't match. Keep the endpoint on HTTPS so the header can't be read in transit.
Not guaranteed; use occurredAt and the record's updatedAt
Duplicates
Possible for some business events; dedupe on the event name plus the record's id and status
Monitoring
The settings page shows each endpoint's last delivery time, status code and error
Because failures aren't retried, treat webhooks as a prompt to act and use the API to reconcile. For example, list records updated since your last sync on a schedule.
28 events are delivered today. Another 8 appear in the event picker but are never sent yet, so don't build on those. Unless noted, data is the full record named in the Data column.