# Builder Prime > All-in-one CRM and business management software for home improvement contractors and remodelers — > lead and client management, appointment setting, estimating and price books, proposals and > e-signature contracts, project and production scheduling, invoicing and payments, SMS and email, > and sales reporting. Each customer works from its own subdomain of builderprime.com. This file was generated by API Evangelist from the publicly reachable Builder Prime surface on 2026-08-08. Builder Prime does not publish an llms.txt of its own (/llms.txt returned 404). ## What the API is Builder Prime exposes a REST "Open API" for pushing leads in and reading CRM data out. It is tenant-scoped: the host is the customer's own Builder Prime subdomain, and the key is issued inside that customer's account. - Base URL pattern: https://{subdomain}.builderprime.com - Auth: a per-tenant secret key in the `x-api-key` request header - Keys are generated at Admin > Integrations > Open API, are shown exactly once, and carry named permissions (for example `clients.create`, `employees.read`) - Versioning: a `/v1` segment on each resource collection ## Resources observed on the live API Confirmed by unauthenticated probes against a live Builder Prime host on 2026-08-08. Each returned a 401 "Unauthorized: Invalid key" or a 405 with an `Allow` header, while an unknown path returned a structurally different 404 — so these routes are real. - POST /api/clients/v1 — create clients / leads - POST /api/client-activities/v1 — create client activities - GET /api/employees/v1 — list and read employees - GET, POST /api/projects/v1 — projects - /api/meetings/v1 — appointments - /api/meeting-types/v1 — appointment types - /api/meeting-results/v1 — appointment results ## Important: fields matched by name, not by id Several optional lead fields are matched by exact string against values configured in the tenant, and a mismatch fails the whole request: `leadStatusName`, `leadSourceName`, `salesPersonFirstName`, `salesPersonLastName`, `leadSetterFirstName`, `leadSetterLastName`, `className`, `projectTypeName`. ## Docs - Open API documentation: https://www.builderprime.com/blog/open-api-documentation - Knowledge base: https://help.builderprime.com/bp-knowledgebase - Integrations: https://www.builderprime.com/integrations - Zapier app: https://www.builderprime.com/integrations/zapier - Pricing: https://www.builderprime.com/pricing - Sign up: https://app.builderprime.com/register - Status: https://builderprime.statuspage.io/ - Terms: https://www.builderprime.com/terms-of-service - Privacy: https://www.builderprime.com/privacy-policy ## What Builder Prime does not publish An agent should not expect to find these — they were probed for and are absent: - No OpenAPI/Swagger definition at any location on the marketing, docs or API hosts - No public endpoint reference — the knowledge-base API articles now return 404, and the surviving documentation page refers to an attached document that is not present in the served page - No published permission/scope list, error-code reference, rate limits, or pagination contract - Webhooks are advertised on the integrations page but no event catalog or payload schema is published - No AsyncAPI, GraphQL, MCP server, agent card, security.txt, or any /.well-known/ document - No first-party SDK in any package registry; the GitHub org (Builder-Prime) has no public repos ## API Evangelist artifacts - Authentication: authentication/builder-prime-authentication.yml - Conventions: conventions/builder-prime-conventions.yml - Errors: errors/builder-prime-problem-types.yml - Lifecycle: lifecycle/builder-prime-lifecycle.yml - Conformance: conformance/builder-prime-conformance.yml - Webhooks: asyncapi/builder-prime-webhooks.yml - Packages: packages/builder-prime-packages.yml - Well-known probe log: well-known/builder-prime-well-known.yml