BuildOps

aid: buildops
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source: []
  generated: '2026-07-22'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/buildops.png
name: BuildOps
description: BuildOps is an AI-native, all-in-one commercial contractor management platform for multi-trade service and construction
  companies. It unifies project management, service operations, dispatch and scheduling, financials and invoicing, and sales/CRM
  into a single system used by 1,500+ contractors across HVAC, electrical, plumbing, fire safety, and refrigeration trades.
  Backed by Founders Fund, the company offers pre-built integrations with ERP and accounting systems (QuickBooks, Sage, Vista,
  Spectrum, NetSuite) plus field-intelligence, payroll, and procurement tools. BuildOps operates a public Dev Center that
  names a BuildOps Public API offering REST endpoints and webhook callbacks, but that API documentation is marked "Invite
  Required" and is reachable only through an implementation or customer-success manager. No OpenAPI, AsyncAPI, GraphQL SDL
  or Postman collection is published anywhere, and no first-party SDK exists in any public registry. The only public Dev Center
  project is a Data Dictionary describing BuildOps datasets on the Dashboard module and a Snowflake private share. BuildOps
  does publish a security policy and a Vanta-hosted Trust Center carrying SOC 2 Type I.
url: https://raw.githubusercontent.com/api-evangelist/buildops/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- founders-fund
x-tier: stub
x-tier-reason: portfolio-lead
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-08-10'
tags:
- Company
- Construction Software
- Field Service Management
- Contractor Management
- Commercial Services
- HVAC
- ERP Integration
- CRM
apis:
- aid: buildops:public-api
  name: BuildOps Public API
  description: The BuildOps Public API, named by the BuildOps Dev Center as the REST + webhook-callback integration surface
    for customers, software partners and vendors. The Dev Center gates its reference behind "Invite Required"; the production
    host is live and answers unauthenticated health checks but publishes no OpenAPI. Recorded here as a real but undocumented
    API surface.
  humanURL: https://developer.buildops.com/docs/buildops-public-api
  baseURL: https://public-api.live.buildops.com
  tags:
  - Field Service Management
  - Contractor Management
  - Construction Software
  properties:
  - type: Documentation
    url: https://developer.buildops.com/docs/buildops-public-api
  x-access: gated
  x-evidence:
    fetched: '2026-08-10'
    humanurl_status: 404
    humanurl_note: '"Invite Required - Reach out to your IM or CSM to get access to the documentation above." The doc node
      is not published to the public Stoplight project, so the link on the Dev Center landing page 404s.'
    baseurl_discovery: Host read from the production host map in BuildOps' own public web-client bundle at https://live.buildops.com/static/js/main.7f23205c.js,
      which names public-api.live.buildops.com as the PROD entry alongside rest-api.live.buildops.com and graphql.live.buildops.com.
      Not stated in any BuildOps documentation; recorded from a live probe, not from the docs.
    baseurl_probes:
    - url: https://public-api.live.buildops.com/
      status: 200
      body: OK!
    - url: https://public-api.live.buildops.com/health
      status: 200
      body: OK!
    - url: https://public-api.live.buildops.com/openapi.json
      status: 404
    - url: https://public-api.live.buildops.com/swagger.json
      status: 404
    - url: https://public-api.live.buildops.com/api-json
      status: 404
    server_note: 404 bodies are NestJS-shaped ({"statusCode":404,"message":"Cannot GET /openapi.json"}), confirming a live
      application rather than a CDN catch-all. No specification is served on any conventional path.
x-contract-discovery:
  checked: '2026-08-10'
  method: probed
  finding: 'Machine-readable contracts for BuildOps DO exist and are generated by the running services - they are auth-gated,
    not absent. Two probes prove it: api.core.live.buildops.com serves the springdoc path /v3/api-docs and answers 401 "Authorization
    token isn`t provided" (a missing spec would 404), and graphql.live.buildops.com/graphql answers a GraphQL introspection
    POST with a 403 "Your authorization token is invalid" rather than a transport error. This is why the coverage state is
    `gated` and not `unreadable` or `none`.'
  probes:
  - url: https://api.core.live.buildops.com/v3/api-docs
    status: 401
    note: springdoc OpenAPI endpoint present
    token required: null
  - url: https://api.core.live.buildops.com/swagger-ui/index.html
    status: 403
  - url: https://graphql.live.buildops.com/graphql
    status: 403
    note: GraphQL introspection rejected - "Your authorization token is invalid"
  - url: https://rest-api.live.buildops.com/openapi.json
    status: 401
    note: unauthorized request
  - url: https://public-api.live.buildops.com/openapi.json
    status: 404
  production_hosts_named_in_web_client:
  - account-management-svc.live.buildops.com
  - api.core.live.buildops.com
  - batch-operation.live.buildops.com
  - bim-svc.live.buildops.com
  - core.live.buildops.com
  - crmplus-api.live.buildops.com
  - equipment-svc.live.buildops.com
  - graphql.live.buildops.com
  - project-management-api.live.buildops.com
  - public-api.live.buildops.com
  - rest-api.live.buildops.com
  - search-query.live.buildops.com
  source: https://live.buildops.com/static/js/main.7f23205c.js
  note: These are the application's own service hosts, discovered from a public JavaScript bundle. They are recorded as evidence
    that the API estate is real and reachable, NOT as documented public endpoints. Only public-api is promoted to an apis[]
    entry, because it is the one the provider itself names as public.
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Website
  url: https://buildops.com
- type: DeveloperPortal
  url: https://developer.buildops.com/
- type: Integrations
  url: https://www.buildops.com/platform/integrations
- type: Pricing
  url: https://www.buildops.com/pricing
- type: SignUp
  url: https://www.buildops.com/book-demo
- type: Login
  url: https://live.buildops.com/
- type: Support
  url: https://academy.buildops.com/
- type: TrustCenter
  url: https://trust.buildops.com/
- type: TermsOfService
  url: https://www.buildops.com/terms-of-service
- type: PrivacyPolicy
  url: https://www.buildops.com/privacy-policy
- type: DomainSecurity
  url: security/buildops-domain-security.yml
- type: Documentation
  name: BuildOps Data Dictionary
  url: https://developer.buildops.com/docs/data-dictionary/4b402d5ab3edd-build-ops-datasets
- type: Blog
  url: https://buildops.com/resources
- type: GitHubOrganization
  url: https://github.com/BuildHero
- type: Security
  name: BuildOps Security Policy
  url: https://buildops.com/security-policy
- type: VulnerabilityDisclosure
  url: security/buildops-vulnerability-disclosure.yml
- type: TrustCenter
  name: Trust center profile
  url: security/buildops-trust-center.yml
- type: Compliance
  name: SOC 2 Type I
  url: https://trust.buildops.com/
- type: Plans
  url: plans/buildops-plans-pricing.yml
- type: RateLimits
  url: rate-limits/buildops-rate-limits.yml
- type: Packages
  url: packages/buildops-packages.yml
- type: LLMsTxt
  url: llms/buildops-llms.txt
x-enrichment:
  date: '2026-08-10'
  status: minimal
  artifacts_added: 8
  pass: local-v1
x-coverage:
  state: gated
  reason: customer-only-docs
  detail: The BuildOps Dev Center advertises a "BuildOps Public API" with REST endpoints and webhook callbacks, then gates
    the reference behind "Invite Required - reach out to your IM or CSM"; the linked doc node 404s to the public and the workspace's
    only published Stoplight project is a Data Dictionary with zero API nodes and zero operations. The contracts demonstrably
    exist behind that wall - the springdoc endpoint /v3/api-docs answers 401 rather than 404, and GraphQL introspection is
    refused with 403 - so this is a gate, not an absence.
  evidence:
  - url: https://developer.buildops.com/docs/buildops-public-api
    status: 404
  - url: https://developer.buildops.com/
    status: 200
  - url: https://stoplight.io/api/v1/workspaces/d2s6MTY5MTA1/projects
    status: 200
  - url: https://api.core.live.buildops.com/v3/api-docs
    status: 401
  - url: https://graphql.live.buildops.com/graphql
    status: 403
  - url: https://public-api.live.buildops.com/openapi.json
    status: 404
  checked: '2026-08-10'