Bimefy is a construction site intelligence platform. It connects BIM, construction planning, cameras, reality capture and site data so teams can compare what was planned with what is actually happening on site.
No construction organisation runs on one platform. There is usually a common data environment, a scheduling tool, whatever the site team uses day to day, and a set of systems specific to how that business works. Bimefy is designed to be part of that landscape rather than a replacement for it.
The Bimefy Integration API is the general-purpose route in. It covers the same paths the named partner integrations use: registering cameras and submitting snapshots, uploading reality-capture datasets, and submitting sensor measurements into a project.
Authentication is by bearer token. Tokens are created per project by an administrator, carry a specific set of scopes, and can be rotated or revoked. Requests are rate limited and logged, so integrations are observable in production rather than opaque.
The API reference is published as an OpenAPI specification with an interactive browser, so a developer can read the endpoints, the request shapes and the scopes each one requires before writing anything.
What the Integration API covers today.
Tokens are created per project, carry only the scopes you select, and can be rotated or revoked by an administrator.
Register cameras against a project and submit snapshots into it, the same route the camera partner integrations use.
Upload capture datasets through a multi-part flow designed for large files, with the batch completed once the parts are in.
Submit measurements into a project, with idempotency support so a retried batch is not stored twice.
Limits are documented and returned in response headers, so a client can back off correctly instead of guessing.
Requests made with an integration token are logged, which makes a live integration reviewable.
The details a developer usually wants before reading the full specification.
Four steps from token to data in the project.
A project administrator issues a token in the project's integration settings and selects its scopes.
Your system sends the token as a bearer token on each request.
Submit snapshots, capture datasets or sensor measurements to the endpoints your scopes allow.
The data lands in the Bimefy project alongside the model, the programme and the rest of the site record.
Common reasons to integrate directly.
Register cameras a team operates itself and submit their imagery into the project.
Push reality-capture datasets into the project from an existing pipeline instead of uploading by hand.
Send measurements from monitoring equipment into the project as they are produced.
Technology partners can connect their own systems to customer projects using scoped tokens.
Construction organisations already carry a lot of software. Adding one more disconnected tool makes the fragmentation worse, not better.
An integration API means Bimefy can take its place in an existing stack. The systems that already produce site data keep producing it, and the data arrives where the model and the programme already are.
Scoped tokens, published limits and request logging are what make that workable in an enterprise setting: access is explicit, reviewable and reversible.
Roles that get the most out of this integration.
Other systems Bimefy connects with
Let approved AI assistants read project data through the Model Context Protocol, with access scoped by token.
View integrationRegister Secury360 cameras against a Bimefy project so site imagery becomes part of the wider project record.
View integrationSend sensor measurements into a Bimefy project so monitoring data sits in the same context as the model and the site.
View integrationBring drone site captures into the project so repeated flights build a visual record over time.
View integrationSee how Bimefy can connect your existing construction systems and turn site data into project intelligence.
Trusted by innovation driven companies