Estimating software integrations: HeavyBid, InEight, B2W, Bluebeam and ACC

Mirage Metrics connects its takeoff agents to the estimating and document systems heavy civil teams already run. Each connection goes through the interface the vendor documents: HCSS's developer platform and takeoff import for HeavyBid, InEight's integration APIs for Estimate quantity items, B2W Estimate's API and takeoff transfer, the Bluebeam API and Markups List, and Autodesk Platform Services for Autodesk Construction Cloud. The quantities arrive structured against your bid items or pay items, each with the sheet and revision it was measured on. Nothing is migrated, and where no documented interface fits, Mirage's engineers build the connector during the deployment.

Published
Updated
Reading time
9 min
Written by
Jules Toussaint

No partnership, certification or marketplace listing is claimed with any vendor named here, and no deployment with these systems is published. Vendor facts are from their own documentation, read on November 9, 2026.

The five systems at a glance

The table shows what Mirage reads from each system, how its quantities get into it, and who on your side opens the access. The mechanism column is the vendor's own name for it.

Estimating and document systems, the interface each vendor documents, and what Mirage does with it. Compiled by Mirage Metrics, November 2026
SystemVendor's interfaceWhat Mirage readsHow quantities get inAccess opened by
HCSS HeavyBidHCSS Developer Platform (API client, heavybid scopes); HeavyBid's takeoff importEstimates, bid items, activities and resourcesTakeoff data imported into HeavyBid, Excel-based on web HeavyBidYour HCSS administrator, who creates the API client
InEight EstimateInEight Estimate integration APIs (List, Upsert and Delete QuantityItems, from version 26.3)Quantity items and pay items of a jobUpserted as quantity items, which the integration alone can then updateYour InEight administrator
B2W EstimateB2W Estimate API; takeoff transfer; Excel import of pay itemsBid items and bid quantitiesTakeoff quantities transferred against bid quantities (Bid Versus Takeoff)Your Trimble B2W administrator
BluebeamBluebeam API (OAuth 2.0): Studio Projects, Studio Sessions, Markups; Revu's Markups ListDrawings in Studio Projects, markups and their statusQuantities go to the estimating system; markup status can be updated through the Markups APIEach user, through the OAuth consent
Autodesk Construction CloudAutodesk Platform Services: Data Management and Takeoff APIsSheets and files; Takeoff packages, takeoff types and takeoff itemsQuantities go to the estimating system: the Takeoff API reads in its first releaseYour ACC account administrator, who authorises the app
Estimating and document systems, the interface each vendor documents, and what Mirage does with it. Compiled by Mirage Metrics, November 2026

HCSS HeavyBid

HeavyBid is where many North American heavy civil estimators build a bid, with its bid items, activities, crews, equipment and production. HCSS documents two routes in. The first is its developer platform, which exposes HeavyBid endpoints per business unit, starting with the list of estimates, bid items, activities and resources. Access goes through an API client with a client ID and secret, and the HeavyBid scopes its token needs (HCSS Developer Portal; read access to estimate data is the HeavyBid Estimate Insights product). The second is takeoff import. HCSS states that takeoff data imports directly into HeavyBid, with an Excel-based import in web HeavyBid. HeavyBid Desktop can integrate with any takeoff solution and with Department of Transportation (DOT) import tools (HCSS, Estimating Takeoff and Bid Setup).

Mirage reads the estimate's bid item list, so each measured quantity lands against the bid item it is paid under. It then produces the takeoff file HeavyBid imports, one line per quantity, with its sheet and revision kept in a reference column. When the next package arrives, the moved quantities come as a new import, listed against the previous one. That way, the estimator sees which bid items changed before re-pricing.

Before you start, check which HeavyBid (web or Desktop) your team runs, whether the business unit has API access, and the bid item structure of the bid at hand (an owner's DOT item list or the contractor's own).

InEight Estimate

InEight Estimate is the estimating application of the InEight platform. InEight's integration specification documents three operations on quantity items, available from version 26.3: List QuantityItems, Upsert QuantityItems and Delete QuantityItems. One rule matters for an AI agent. A customer can only update or delete the quantity items created through the integration, never the ones an estimator entered or another source created (InEight Estimate Integration Specification, rev. 10.0). The same specification documents Upsert Estimates and Upsert PayItems, and InEight's help points developers to its API Developer Portal (InEight Estimate help, API Integration).

Mirage writes its measured quantities as quantity items on the job, each carrying the sheet and revision it came from. When a package is reissued, it updates or deletes only those items. The estimator's own quantity items are never touched, which is the vendor's rule and the one a reviewer wants anyway. A person approves a batch before it is written, and the log keeps who approved it.

Before you start, check the Estimate version (26.3 or later for the quantity item operations) and the job's pay item structure.

B2W Estimate

B2W Estimate, now Trimble's, is built for heavy civil bidding. Trimble's features overview lists an Estimate API that "allows machine-to-machine connectivity". It also lists bid quantities and takeoff quantities side by side with a Bid Versus Takeoff summary, the transfer of reported data from a takeoff, and Excel import and export of pay items (Trimble, B2W Estimate 25.1 features). The product page adds imports of Excel tables and connections to electronic bidding and DOT programs (Trimble, B2W Estimate).

Mirage delivers its quantities as takeoff quantities against the estimate's bid items. The Bid Versus Takeoff summary then shows where the owner's quantity and the measured one differ, item by item, which is often where a unit-price bid is won or lost. The quantities go in through the Estimate API where your licence includes it, and through the takeoff transfer or the Excel import otherwise.

Bluebeam

Bluebeam Revu is where many drawings are opened, measured and marked up. Two interfaces matter. The Bluebeam API is a REST API for Studio Projects (document storage and revisions) and Studio Sessions (shared markup), with webhooks and Markups APIs that read and update a markup's status (Bluebeam, Develop integrations). An app connects on behalf of a user through OAuth 2.0 (Bluebeam, Authentication guide). The second interface is inside Revu itself, where every markup and measurement is tracked in the Markups List. Compare Documents and Overlay Pages, which show what changed between two revisions, come with a Core or Complete subscription (Bluebeam, Compare documents vs Overlay Pages).

Mirage reads the drawings from Studio Projects, or the PDFs your team exports. It can also read the measurements an estimator already placed, so its own quantities and the team's are compared rather than duplicated. Its quantities go to the estimating system, not into Revu. Where a quantity needs a person's look, its status can be set through the Markups API, so the question shows up where the estimator already works.

Autodesk Construction Cloud

Autodesk Construction Cloud (ACC) holds the drawings, sheets and documents of many large projects, and its Takeoff product holds quantities. Autodesk Platform Services documents the APIs. The ACC developer's guide covers authorising an app on an account (APS, ACC developer's guide). The Takeoff API covers the packages, takeoff types and takeoff items of a takeoff project (APS, Takeoff API), and its first release focuses on read access (APS blog).

Mirage reads the current sheets and their versions from ACC, so it measures what the project actually issued. It can also read the takeoff items your team already created in ACC Takeoff, to compare them with its own. Its quantities go to the estimating system, because the Takeoff API reads. If Autodesk documents a write path later, it becomes an option, not before.

How a connection is set up

  1. In the first meeting, you name the systems and versions, and the bid item or pay item structure the quantities must follow.
  2. Your administrator opens the access each vendor documents, with the least rights the workflow needs: an API client, an integration user, an OAuth consent or an export folder.
  3. The proof of concept, one week after the first meeting, runs on a past bid's drawings, so Mirage's quantities can be set against the ones your team measured.
  4. Nothing is written into a system before a named person on your side approves it, and every agent action is logged with its inputs, its sources and its result.
  5. The first workflow goes into production in 4 to 6 weeks, operated, monitored and improved by Mirage's engineers.

The rules behind the last two steps are on security and approvals and audit. The documents a procurement team asks for are in the procurement and security pack.

What this page does not say

This page does not say that Mirage holds a partnership, a certification or a marketplace listing with HCSS, InEight, Trimble, Bluebeam or Autodesk, and it does not name a client using these connections, because none is published. It does not say that Mirage writes where a vendor documents no write path. The vendors' interfaces also change, which is why each connection is checked against the version your team runs, in the first meeting.

The published construction proofs

OCBM runs three agents in production with every quantity tied to a source drawing (OCBM case study); John Cockerill cut piping takeoff time by 80 to 90% (John Cockerill case study). Neither uses the systems on this page.

Questions readers ask

  • No, Mirage does not replace HeavyBid, InEight Estimate or B2W Estimate. Those systems hold the estimate: crews, equipment, production rates, unit costs, the bid. Mirage measures the quantities from the drawings, keeps each one tied to its sheet and revision, and hands them to the estimate through the interface its vendor documents. The estimator prices in the system the team already runs.

  • Mirage writes directly into your estimate only where the vendor documents a write path, and only after a person on your side approves. InEight documents one for quantity items, limited to the items the integration created. HCSS documents imports of takeoff data into HeavyBid, and Trimble documents an Estimate API and takeoff transfers for B2W, so quantities go in through those. Autodesk's Takeoff API is read access in its first release.

  • This page claims no partnership, certification or marketplace listing with these vendors. Each connection uses the interface the vendor documents publicly, with the access your administrator grants under your licence.

  • No deployment of these integrations is published yet. The published construction deployments are OCBM, where every quantity is tied to a source drawing, and John Cockerill, on piping takeoff. A connection to your system is scoped in the first meeting and tested on a past bid's documents in the proof of concept.

Sources and scope

Checked on .

Which system holds your estimate?

Name it and its version in the first call. The proof of concept, a week later, runs on one of your past bids.

We use your email to reply to you and, now and then, to tell you about Mirage. You can opt out at any time. Privacy policy