
What can you build with the Jet.Build API
Custom Integrations
Plan connections between Jet.Build and the tools your team uses. Confirm the records, fields and operations your workflow requires against the API reference, and agree on any additional integration work before development.
View API documentation →Custom Workflows & Reporting
Use documented project, drawing, RFI, submittal and task endpoints to build workflows around your project records. Review the API reference for each endpoint's fields, permissions and supported operations.
View API documentation →A modern REST API built for construction data.
RESTful Architecture
Standard REST endpoints with JSON responses. If your team can call an API, they can integrate with Jet.Build.
Token-Based Authentication
Follow the API reference to obtain and send a user API token. Requests run with that user's project visibility and permissions; confirm token-management requirements before deployment.
Documented Project Endpoints
The public API reference covers project information, drawings, RFIs, submittals and tasks. Check the documented operation for each record type before designing a connection.
Plan How Data Updates
Define when your integration retrieves or sends records, which system owns each field, and how your team handles delays, conflicts and failed requests.
How teams extend Jet.Build.
Accounting Sync
Planning an accounting connection? Bring your accounting product and edition, the records you need to exchange, and the direction each record should move. Confirm the supported connection and implementation scope with Jet.Build before committing to a workflow.
Custom Dashboards
Identify the project records your reporting workflow needs, then check the documented endpoints and fields. Confirm any additional data requirements before building a dashboard or data pipeline.
Automated Workflows
Define the action, required records, permissions and error handling for each proposed workflow. Confirm how updates will be detected and which operations are supported before implementation.
What to confirm before connecting your systems
Confirmed custom integration examples include Sage, QuickBooks, DocuSign, RealPage and EarthCam. Each implementation defines the records exchanged, permissions, data direction, update timing and exception handling. Capabilities depend on the agreed scope and third-party access. Use this checklist with your project, accounting and implementation teams before development.
Systems to assess for a custom integration
Start with the workflow you need to connect. Explore a custom integration with the systems below. Available workflows depend on your product edition, API access and agreed implementation scope.
| Workflow | Systems to assess | Scope to define |
|---|---|---|
| Accounting and ERP | Yardi, Viewpoint, CMiC, Acumatica, NetSuite, Microsoft Dynamics 365, Xero | Project and account mapping, budgets, commitments, invoices and payment status |
| Documents and collaboration | SharePoint, OneDrive, Google Drive, Dropbox, Box, Microsoft Teams | Project files, document references, folders, notifications and collaboration |
| Scheduling | Primavera P6, the customer’s supported Microsoft Project environment, Smartsheet | Schedule information, milestones, dependencies and progress |
| Reporting | Power BI, Tableau | Project and portfolio reporting using agreed data sources |
| CRM and project initiation | Salesforce, HubSpot | Account and project information, and handoffs into project setup |
| Design and construction documents | Autodesk Construction Cloud | Agreed document and project-information exchanges |
The customer’s product edition, third-party access and permissions determine what can be implemented. Define records, direction, update timing and exception handling for each workflow; do not assume identical capabilities or universal two-way synchronization.
Continue with the integration checklist below to agree the scope and acceptance evidence.
| Decision | What to record |
|---|---|
| System and edition | The exact accounting or business product, version and company/entity structure. |
| Records and direction | The records and fields that must move, where each starts, and whether updates travel one way or both ways. |
| Source of truth | Which system controls each field and how conflicting edits are resolved. |
| Timing and exceptions | When updates occur, who sees a failure, and how corrected records are retried without creating duplicates. |
| Reconciliation | A sample project and agreed checks that show the receiving system matches the intended records and totals. |
| Ownership and scope | Who configures, tests and supports the connection, plus any implementation work or fees. |
Before rollout, ask for a demonstration of your required data flow using a controlled sample. Record limitations and acceptance criteria in the implementation scope.
Use the integration acceptance worksheet to agree which records move, in which direction, under whose permissions, and how reconciliation and exceptions will be checked before the workflow is accepted.
Download the integration acceptance worksheet (fillable PDF)Fillable PDF; save a copy before entering project information.
The worksheet defines acceptance evidence. It does not guarantee that a named connector, endpoint or synchronization method is available.
Evaluating how external AI tools fit alongside project systems? See AI construction software: choosing tools for project management.
The platform is only part of the implementation.
Your dedicated U.S.-based account manager helps configure Jet.Build around your operation, onboard internal and external stakeholders, lead recurring training, and support your team throughout the relationship.
See How Support Works