bidbuild API

Name: bidbuild API
Brand: bidbuild API
Availability: InStock

✓ Official Vendor SpecProductivityTask Managementbearer735 EndpointsREST

For Agents

Manage construction leads, proposals, projects, invoices, payments, and QuickBooks sync through bidbuild's business management platform.

Install Jentic One Beta

Connect the bidbuild API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the bidbuild API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with bidbuild API.

Manage construction leads from initial enquiry through to converted projects

Generate and send proposals with line items, scopes, and signatures

Track invoices, mark them as paid, and release them to QuickBooks

GET STARTED

Start building with bidbuild API

Explore with Jentic

View OpenAPI Document

bidbuild is a construction-focused business management platform that covers the full lifecycle from lead tracking through proposal generation, project execution, change orders, invoicing, and vendor inventory management. Its REST API exposes 735 endpoints across leads, projects, proposals, invoices, payments, vendors, files, notifications, and a deep QuickBooks integration. Authentication uses bearer tokens against api.bidbuild.net. The endpoint surface is large — agents typically narrow scope to a specific module such as invoicing or proposals rather than treating it as a single API.

Use Cases

Patterns agents use bidbuild API for, with concrete tasks.

★ Lead to Cash for Construction

Run the full sales-to-cash cycle for a residential or commercial construction firm. Capture a lead, generate a proposal, convert it into a project on signature, raise progress invoices, mark them paid, and release them to QuickBooks. The 735-endpoint surface covers each step and the QuickBooks integration removes the need for manual journal entry.

Create a lead in bidbuild, generate a proposal with two line items, then on acceptance create the corresponding invoice and release it to QuickBooks.

QuickBooks Synchronisation

Keep customers, vendors, projects, and invoices synchronised between bidbuild and QuickBooks Online so the accounting team works from the QuickBooks ledger while the field team uses bidbuild. The /api/v1/quickbooks/* endpoints handle the OAuth integration setup, customer and vendor sync, and per-invoice release back to QuickBooks.

Sync all QuickBooks customers into bidbuild via /api/v1/quickbooks/customers and reconcile invoice IDs.

Cashflow and Invoice Aggregation Reporting

Generate a cashflow report by querying /api/v1/invoices with filters and aggregating totals via /api/v1/invoices/aggregate/totals. This avoids loading every invoice into the report tool and supports rolling weekly, monthly, and quarterly views for finance leads inside the construction business.

Call /api/v1/invoices/aggregate/totals with date filters for the last 90 days and group totals by status.

AI Agent Project Manager Assistant

An AI agent helping a project manager track a portfolio of construction jobs can answer questions like 'which invoices are overdue?' and 'what proposals are awaiting signature?' through Jentic. The agent searches by intent, loads the relevant schema, and executes — Jentic injects the bearer token so the agent never sees the raw credential and can focus on the underlying business question.

Search Jentic for 'list bidbuild invoices', execute /api/v1/invoices, and return the subset where status is overdue.

Key Endpoints

735 endpoints — bidbuild is a construction-focused business management platform that covers the full lifecycle from lead tracking through proposal generation, project execution, change orders, invoicing, and vendor inventory management.

METHOD

PATH

DESCRIPTION

GET

/api/v1/invoices

List invoices

POST

/api/v1/invoices

Create an invoice

POST

/api/v1/invoices/{id}/quickbooks

Release invoice to QuickBooks

POST

/api/v1/invoices/{id}/mark_as_paid

Mark an invoice as paid

GET

/api/v1/invoices/aggregate/totals

Aggregate invoice totals

GET

/api/v1/quickbooks/customers

List QuickBooks customers

GET

/api/v1/notification_settings

Get notification settings

GET

/api/v1/invoices

List invoices

POST

/api/v1/invoices

Create an invoice

POST

/api/v1/invoices/{id}/quickbooks

Release invoice to QuickBooks

POST

/api/v1/invoices/{id}/mark_as_paid

Mark an invoice as paid

GET

/api/v1/invoices/aggregate/totals

Aggregate invoice totals

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

bidbuild bearer tokens are stored encrypted in the Jentic vault (MAXsystem). Agents call bidbuild operations via Jentic and the Authorization header is injected at execution time — a critical isolation given that the token also authorises QuickBooks invoice release.

Intent-based discovery

Agents search by intent (e.g., 'list overdue construction invoices') and Jentic returns the matching bidbuild operation with its filter parameters, so the agent does not need to navigate the 735-endpoint reference to find the right invoice listing route.

Time to first call

Direct bidbuild integration: 1-2 weeks for OAuth, QuickBooks pairing, and the multi-resource sync flows. Through Jentic: under 1 hour for an individual operation — search, load schema, execute.

FAQs

Specific to using bidbuild API through Jentic.

What authentication does the bidbuild API use?

bidbuild uses HTTP Bearer authentication — pass the access token in the Authorization header on every request. Through Jentic, the bearer token is stored encrypted in the Jentic vault (MAXsystem) and injected at execution time so the agent never sees the raw token, which matters because the same token can release invoices and trigger QuickBooks sync.

Can I release a bidbuild invoice to QuickBooks Online?

Yes. POST /api/v1/invoices/{id}/quickbooks releases the specified invoice to QuickBooks once the QuickBooks integration has been authorised under /api/v1/auth/quickbooks. The reverse, DELETE /api/v1/invoices/{id}/quickbooks, unreleases an invoice.

How do I aggregate invoice totals across a date range?

Call GET /api/v1/invoices/aggregate/totals with appropriate filter parameters. The response gives totals grouped by status, which is the pattern construction CFOs use for weekly cashflow reviews without scanning every individual invoice record.

How do I list bidbuild invoices through Jentic?

Search Jentic for 'list bidbuild invoices', load /api/v1/invoices, and execute. With the SDK: pip install jentic, then SearchRequest, LoadRequest, ExecutionRequest in an async flow — Jentic injects the bearer token automatically.

Does bidbuild support webhooks?

Yes — the spec exposes a QuickBooks webhook endpoint at POST /api/v1/quickbooks/webhook used to receive QuickBooks change events. Configure your webhook subscription in the bidbuild admin console and keep the endpoint reachable so QuickBooks events are processed.

How large is the bidbuild API surface?

The OpenAPI spec exposes 735 endpoints across leads, proposals, projects, invoices, payments, files, vendors, and the QuickBooks integration. Most agents work against a narrow subset — for example invoices and QuickBooks together — rather than treating the entire surface as one tool.

bidbuild API

Connect the bidbuild API to your agent

Capabilities

Start building with bidbuild API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs