Document control integrations: Oracle Aconex, Bentley ProjectWise and Autodesk Docs

Mirage Metrics connects its document control agent to the systems where large projects keep their documents. Each connection goes through the interface the vendor documents: the Aconex Documents and Mail APIs, Bentley's ProjectWise SDK and Web Services Gateway, and Autodesk Platform Services for Autodesk Docs. For each system, this page separates two paths. The read path is what the agent can see. The write path is what it may change once a named person approves. Nothing is migrated, and the system stays the record.

Published
Updated
Reading time
11 min
Written by
Jules Toussaint

No partnership, certification or marketplace listing is claimed with Oracle, Bentley or Autodesk, and no deployment with these systems is published. Vendor facts are from their own documentation, read on November 10, 2026.

The three systems at a glance

The table shows what the agent reads in each system, what it may write, and who on your side opens the access. The interface column uses each vendor's own names.

Document control systems, the interface each vendor documents, and the read and write paths Mirage uses. Compiled by Mirage Metrics, November 2026
SystemVendor's interfaceRead pathWrite pathAccess opened by
Oracle AconexAconex REST APIs: Documents API and Mail API, OAuth 2.0 preferredRegister search, document metadata, files and event log; mail and transmittals, with their attachments and threadsRegister Document and Supersede Document; Create Mail, a transmittal with registered documents attached includedYour organization, which registers the integration with Oracle; calls run as an Aconex user with that user's access
Bentley ProjectWiseProjectWise SDK (C libraries, event hooks); Bentley Web Services Gateway with the ProjectWise plug-inDocuments, attributes, states and files the account can see; hooks on events such as a check-out or a state changeSettled against the SDK documentation that comes with Bentley Developer Network membership, for the version you runYour ProjectWise administrator
Autodesk Docs (Autodesk Forma Data Management)Autodesk Platform Services: Data Management API; Transmittals and Reviews APIs; custom attributes batch updateHubs, projects, folders, items and versions; transmittals with their recipients, folders and documents; reviews and their progressNew items and new versions; custom attribute values; approval workflows and new reviews. No transmittal: that API reads onlyYour account administrator, who adds the app as a custom integration; with three-legged access, the user's own project rights
Document control systems, the interface each vendor documents, and the read and write paths Mirage uses. Compiled by Mirage Metrics, November 2026

For Procore, see the Procore integration guide. Takeoff quantities read from Autodesk's Takeoff API are covered with the estimating software integrations.

Oracle Aconex

Oracle documents the Aconex REST APIs module by module. The Documents API reads the register. With it, you can list and search documents, view a document's metadata, download its file, and view its event log, which records events such as a document sent with a transmittal. On the write side, it offers Register Document and Supersede Document. Files over 100 MB go through a large file upload, whose progress is checked as a background job (Oracle, Documents API Developer Guide).

The Mail API reads mail, transmittals included, with their attachments and threads. It writes with Create Mail, Reply Mail and Forward Mail. Two limits apply. Registered documents can only be attached to mail of the Transmittal or Tender Transmittal type, and a user can only create the mail types that user is permitted to create. Each organization also keeps its own register. For a received document, the API returns its id in the recipient organization's register once it has been registered from the mail (Oracle, Mail API Developer Guide, July 2026).

Access starts with registration: every integration with Aconex must be registered. A customer registers its own for internal use and receives credentials that identify it. OAuth 2.0 is the preferred method. A call acts for a user whose account must be active and who must have access to the data, within limits on the volume and frequency of requests. Oracle plans to retire all Integration IDs towards the beginning of 2027, after which Basic Authentication will no longer be accepted for API access (Oracle, Getting started with APIs).

On the read path, Mirage reads each incoming transmittal and the registered documents on it (number, revision, status, title), and checks them against your convention and your organization's register. On the write path, once approved, it registers or supersedes documents in your register, and prepares outgoing transmittals with the registered documents attached. Those are sent through Create Mail as an Aconex user whose permissions your administrator sets, so Mirage never creates a mail type that user may not.

Before you start, check three things: that the integration is registered for OAuth, which mail types its user may create, and the project's document schema, which the Documents API returns.

Bentley ProjectWise

Bentley describes two programmatic routes into ProjectWise. The first is the ProjectWise SDK, a set of C libraries for establishing sessions with ProjectWise datasources and communicating with them. Its hooks start a process on a user event in ProjectWise Explorer, such as checking out a document or changing its state. The SDK comes with membership of the Bentley Developer Network (Bentley, ProjectWise SDK). The second is Bentley Web Services Gateway, with its ProjectWise plug-in. It is an on-premise server through which any service, client or mobile application, on any platform, accesses data and files, and it is how ProjectWise Web and ProjectWise Web View reach a datasource (Bentley, ProjectWise Plug-in for Bentley Web Services Gateway).

Transmittals live in ProjectWise Deliverables Management, which sends packages of documents between organizations for review and approval. An outgoing package is a transmittal, and an incoming one is a submittal. The sender's document controller creates the transmittal, and the receiving organization's document controller assigns a lead reviewer. The lead reviewer then consolidates the reviewers' responses into the one that goes back (Bentley, Transmittal / Submittal Design Review Workflow).

On the read path, Mirage works through the Gateway or the SDK, under a ProjectWise account your administrator sets up. It reads the documents, attributes and states of the folders it is given, and a state change can start its checks through the SDK's hooks. The write path depends on your version. Bentley's public pages describe the SDK's scope, not each operation, so which writes Mirage uses (a new version, an attribute, a state) is settled against the SDK documentation for the version you run, before anything is written. Until then, Mirage's output is a list your controller acts on in ProjectWise, and your controller sends transmittals from Deliverables Management.

Before you start, check whether the project runs on ProjectWise Design Integration with the Gateway installed, and which folders, attributes and states carry your document control.

Autodesk Docs (Autodesk Forma Data Management)

Autodesk Docs, which Autodesk's developer blog now calls Autodesk Forma Data Management, holds an Autodesk Construction Cloud project's files, meaning its folders, documents and their versions. Autodesk Platform Services documents the APIs. The Data Management API reads hubs, projects, folders, items and versions (APS blog, August 26, 2025). It writes by creating an item, a file's first version, or a new version of an existing one. Those calls take no custom attribute values, so attributes are written through the custom-attributes batch-update endpoint instead (APS blog, September 12, 2025).

Two folder rules matter to a document controller. A folder can carry a naming standard and required custom attributes, and a file is conforming only when its name follows the standard and its required attributes have values. A file uploaded without its required attributes goes to the holding area if the holding area is enabled. If it is not, the upload itself fails (same post).

The Transmittals API is read-only: it lists a project's transmittals and returns each one's recipients, folders and documents (APS blog, December 10, 2025). The Reviews API, by contrast, reads approval workflows, reviews and the progress of each step, and writes two things: a new approval workflow, and a review started on selected file versions (APS blog, September 30, 2025).

Before any call, the account administrator adds the app's client ID under Account Admin, Custom Integrations. With three-legged authentication, the user must also have access to the project, at least to its Docs files (APS blog, August 26, 2025).

On the read path, Mirage reads the folders and versions it is given, the transmittals with their documents, and the reviews in progress. It checks every file against your convention as well as the naming standard Autodesk already enforces. On the write path, once approved, it creates new versions, writes custom attribute values through the batch-update endpoint, and starts new reviews. Your controller sends transmittals in Autodesk Docs, from the list Mirage prepares, because the API does not create them.

When the owner and the joint venture run different systems

On a large project, the owner may mandate its own system while the joint venture keeps its own register. That can mean Aconex on one side and ProjectWise or Autodesk Docs on the other, or two organizations on the same Aconex project, each with its own register. Mirage reads the transmittal where it arrives and checks it against the owner's convention and the joint venture's. Once approved, it registers the documents on the joint venture's side with both numbers kept. Outgoing documents go the other way, checked against the owner's convention before the transmittal is sent. Each side keeps its own access rules, and the agent holds only the rights each administrator grants it.

The workflow itself, and the conventions it checks, are on the construction document control page.

How a connection is set up

  1. In the first meeting, you name the systems and their versions, and your document control procedure: numbering convention, status and review codes, distribution matrix.
  2. Your administrators open the access each vendor documents, with the least rights the workflow needs. In Aconex, that is an integration your organization registers, with its user. In ProjectWise, it is an account on the folders concerned. In Autodesk Docs, it is the app added as a custom integration in Autodesk's Account Admin.
  3. The proof of concept, one week after the first meeting, runs on past transmittals, so what the agent flags can be set against what your controller found.
  4. Nothing is written into a system before the named approver set for the workflow signs off, and every agent action is logged with its inputs, its sources, its result and who approved it.
  5. The first workflow goes into production in 4 to 6 weeks.

The rules behind the last two steps are on security and approvals and audit. Mirage runs in your cloud, on your premises or hosted by Mirage. 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 Oracle, Bentley or Autodesk, and it names no client using these connections, because none is published. It does not say that Mirage writes where a vendor documents no write path, or that it sends transmittals through Autodesk's API, which reads them only. 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). No document control deployment is published yet.

Questions readers ask

  • Mirage writes into Aconex, ProjectWise or Autodesk Docs only where the vendor documents a write path, and only after the named approver set for the workflow signs off. Oracle documents Register Document, Supersede Document and Create Mail for Aconex. Autodesk documents new items and versions, custom attribute values and new reviews, while its Transmittals API reads only. For ProjectWise, Bentley's public pages describe the SDK's scope, so the writes are settled against the SDK documentation for your version first.

  • Mirage can send a transmittal in Aconex only. There it uses Create Mail with the Transmittal type and registered documents attached, if the user it runs as may create that mail type. In Autodesk Docs, the Transmittals API reads only, so Mirage prepares the transmittal and your controller sends it. In ProjectWise, your controller sends it from Deliverables Management, from the list Mirage prepares.

  • Mirage claims no partnership, certification or marketplace listing with Oracle, Bentley or Autodesk. Each connection uses the interface the vendor documents, registered by your organization where the vendor requires it, and run with the access your administrator grants.

  • No deployment of these integrations is published yet. The published construction deployments are OCBM, with three agents in production and every quantity 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 past transmittals in the proof of concept.

Sources and scope

Checked on .

Which system holds your register?

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

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