How does Bildstak connect to my project data?
Bildstak connects through native connectors and REST APIs: it reads IFC files directly, pulls schedule data via P6 exports or APIs, connects to Procore and Aconex via their APIs, reads SAP and Maconomy cost journals, ingests spreadsheets and PDFs, and accepts custom REST APIs for any other system.
Bildstak is designed to connect to the systems a project already uses, not to replace them. Connection happens through a combination of native file readers, hosted API connectors, and a custom REST API framework:
How each source type connects: - BIM models (IFC, Speckle, Autodesk APS): IFC files are read directly; Speckle and APS connect via their APIs to pull model data and keep it current. - Schedule (Primavera P6): P6 XER exports are ingested and can be refreshed on a schedule; API connection is available for P6 Cloud. - Cost/ERP (SAP, Maconomy): REST API connectors pull cost journals, budget lines and actuals; OAuth2 and API-key auth are both supported. - Document control (Procore, Aconex): REST API connections pull RFIs, submittals, documents and correspondence, with status kept live. - Standards files (IFC, BCF, COBie, IDS): read natively; BCF files can be ingested from any tool that exports them. - Spreadsheets and document libraries: Excel and Google Sheets connect directly; folders of documents (PDFs, Word files) are processed and indexed for query. - Custom REST APIs: any system that exposes a REST endpoint can be connected through the custom API connector.
Once a source is connected, it is indexed by Bildstak's federation layer. Records are joined by IFC GlobalID (for BIM projects) or by activity IDs and cost codes (for heavy civil). The project team queries the unified model — they do not interact with the individual connectors.
Updated 2026-06-19