Have the drawings?
Use the BIMR engine directly.
Selected vector PDF plans can become draft architectural IFC models with source-linked geometry. An API job would package that engine for your own workflow.
Explore 2D-to-3D endpointsBIMR API / Capability showcase
From 2D drawings to 3D BIM. From building records to useful answers. Bring the BIMR engine into the tools your customers already use.
API design showcase. This catalogue combines existing BIMR capabilities with proposed services. The endpoints are illustrative, not a released public API. Enquiries open your email client; this page does not place orders.
01 / A building model, ordered through your application
Let a homeowner, architect or company order a model of a real building. Supply the address and intended use. The proposed service coordinates drawing retrieval, runs the BIMR engine and delivers an IFC package directly to the buyer. No BIMR app subscription required.
Target from order confirmation for eligible buildings. The quote confirms scope and expected delivery. Archive delays, scans, missing drawings or additional review can extend the time.
Address, property reference, the right building and the buyer's intended use.
A BIMR agent coordinates archive correspondence and follows up within the approved scope.
Replies and drawings join the order record. Sheets, revisions and source rights are checked.
The BIMR engine creates the supported geometry. Coverage and assumptions are reviewed.
IFC files, a preview, room data and a quality report go to the approved recipient.
Explore a fictional order
An archive question, a missing floor plan or a fee request becomes a visible order state. Your customer can follow progress in your application and receive the final files directly.
Select a stage to explore an example. No request is sent and no file is generated.
Discuss a building orderArchive request prepared
A request identifies the property, floors and drawing types, with a reply reference and an agreed fee ceiling.
Illustrative state. No archive has been contacted.
GET /v1/bim-orders/example-order-001{
"example": true,
"order_id": "example-order-001",
"status": "archive_request_prepared",
"app_subscription_required": false,
"target": {
"min_working_days": 1,
"max_working_days": 5,
"starts_at": "order_confirmation",
"guaranteed": false
},
"deliverables": []
}Have the drawings?
Selected vector PDF plans can become draft architectural IFC models with source-linked geometry. An API job would package that engine for your own workflow.
Explore 2D-to-3D endpointsNeed the drawings?
The proposed order flow combines archive correspondence, document intake and model delivery. Scans and incomplete sets need a qualified reconstruction or specialist review path.
Explore archive endpointsA drawing-derived model describes the available drawings. Current dimensions and installations may need site verification. Stockholm's archive guidance explains this distinction; Malmö publishes about a week for document handling. Archive release and reconstruction time are separate.
02 / Explore what your application could offer
Explore 109 proposed endpoints across 17 service families. Open a family to see the customer outcome, example route and what it depends on.
Underlying functionality exists in BIMR. External API packaging and validation are still required.
A proposed service requiring new engineering or an operational workflow.
Requires vendor data, a customer connection or an agreed source licence, plus integration work.
Requires enough comparable, permitted observations. Customer scale is not assumed.
No matching endpoints. Try a broader term or reset the filters.
For homeowners, building owners, architects, surveyors, software platforms
Order orchestration, archive intake, pricing, review and direct delivery need implementation. Target: 1–5 working days for eligible orders from confirmation; the quote must give an expected delivery date.
Building identity, available drawings, intended use, model detail, estimated fees and delivery target.
POST /v1/bim-orders/quotesCreate an order against an accepted quote, authorized use and named recipients.
POST /v1/bim-ordersSee archive progress, missing information, review state and the current delivery estimate.
GET /v1/bim-orders/{order_id}Contribute permitted files to the same order, even while archive retrieval is underway.
POST /v1/bim-orders/{order_id}/documentsApprove extra archive fees, revised scope or delivery timing explicitly.
POST /v1/bim-orders/{order_id}/approvalsReturn cancellation eligibility, incurred work and the applicable refund decision.
POST /v1/bim-orders/{order_id}/cancellationAuthorized IFC download, preview, room schedule and a report of sources, coverage and assumptions.
GET /v1/bim-orders/{order_id}/deliverablesSend the approved package to a named recipient by secure link, with delivery status.
POST /v1/bim-orders/{order_id}/deliveriesFor owners, property managers, archive services
Municipality-specific access, a configured mailbox, fee authority and release decisions are required. The workflow includes human handling for login, restrictions and ambiguous replies.
Verified municipality contact, available request method and the date it was checked.
GET /v1/archives/coverageA tracked request for the selected property, sheet types and permitted fee ceiling.
POST /v1/drawing-requestsDistinguish requested, received, partial, not found, restricted and needs-action states.
GET /v1/drawing-requests/{request_id}A permission-controlled thread linking archive questions, replies and attachments.
GET /v1/drawing-requests/{request_id}/messagesAn authorized reply or agent-assisted clarification, retained with the request.
POST /v1/drawing-requests/{request_id}/repliesOriginal files linked to the request, source, building candidates and review status.
GET /v1/drawing-requests/{request_id}/documentsFor architects, bim consultants, owners, renovation teams
The engine exists for selected vector PDFs. API jobs, complete drawing-set assembly and raster reconstruction need additional work; each result needs a stated coverage and review status.
Supported input types, usable scale, missing floors or sections and a proposed model scope.
POST /v1/reconstructions/preflightA draft IFC from supported vector plans, with rooms, walls, openings and recorded assumptions.
POST /v1/reconstructionsProcessing stage and errors, independently from model coverage and review acceptance.
GET /v1/reconstructions/{job_id}IFC, room schedule, source references and model-quality findings in one output contract.
GET /v1/reconstructions/{job_id}/outputsWhich geometry came from a drawing, construction practice or an explicit assumption.
GET /v1/reconstructions/{job_id}/provenanceAccepted corrections, reviewer identity and remaining limitations for this revision.
POST /v1/reconstructions/{job_id}/reviewsA coordinated architectural model using compatible plans, sections and revision choices.
POST /v1/drawing-sets/{set_id}/reconstructionsA proposed scan-to-BIM service requiring a validated raster pipeline and geometric review.
POST /v1/raster-reconstructionsFor software teams, designers, estimators, facility managers
IFC conversion and object queries have an existing foundation. New exports, comparison and review services need validation against model contents and units.
A browser-ready model and indexed elements from a customer-authorized IFC.
POST /v1/modelsFilter actual model objects and return identifiers, classes and available properties.
GET /v1/models/{model_id}/elementsA room and floor register with model references and available quantities.
GET /v1/models/{model_id}/spacesDiscover the systems actually present in the model and their connected elements.
GET /v1/models/{model_id}/systemsAvailable areas, lengths, volumes and counts with units and measurement provenance.
GET /v1/models/{model_id}/quantitiesAdded, removed and changed objects, including unresolved identity matches.
POST /v1/model-comparisonsMissing properties and documents against the customer's stated requirements.
POST /v1/model-checksA permission-scoped view of selected models or objects with an expiry and revocation path.
POST /v1/model-viewsFor architects, contractors, surveyors, maintenance teams
Sheet classification, revision reconciliation and generated 2D outputs need new packaging and validation. Derived drawings retain their source limitations.
An inventory of sheets, floors, disciplines, dates and source files.
POST /v1/drawing-setsMissing floors, sections and references against the agreed building scope.
GET /v1/drawing-sets/{set_id}/coverageCurrent, superseded and unresolved sheet versions with the review decision.
GET /v1/drawing-sets/{set_id}/revisionsCandidate geometry and annotation changes for a reviewer to verify.
POST /v1/drawing-comparisonsA proposed PDF or SVG plan with scale and the model revision identified.
POST /v1/models/{model_id}/floor-plan-exportsA selected cut through the available geometry with source and limitation notes.
POST /v1/models/{model_id}/section-exportsFor owners, brfs, property managers, public property teams
Customer mandates and upstream entitlements govern access. A property can contain several buildings; an address match alone must not silently merge them.
Address or property-reference candidates with ambiguity and source information.
POST /v1/buildings/resolveKnown facts, linked models and documents, dates and unresolved information.
GET /v1/buildings/{building_id}An authorized correction with the previous value and source retained.
PATCH /v1/buildings/{building_id}Reconcile your building list, external IDs and owner groups without duplicates.
POST /v1/portfolio-importsThe buildings in the selected owner or manager scope, including incomplete identities.
GET /v1/portfolios/{portfolio_id}/buildingsA separately entitled register lookup with price, mandate and permitted use checked first.
POST /v1/ownership-lookupsA collection list for missing facts, drawings, documents and equipment records.
GET /v1/buildings/{building_id}/coverageFor property software, managers, inspectors, administrators
Existing extraction supports selected document types. Answers require access to the cited originals; scans readable as text are not automatically reconstructable as geometry.
Stored originals, document classification and candidate building links.
POST /v1/documentsTyped facts, source pages, confidence and review state for supported reports and invoices.
GET /v1/documents/{document_id}/extractionsAuthorized access to the original file behind a claim or extracted value.
GET /v1/documents/{document_id}/originalRelevant passages and source references within explicitly selected buildings.
POST /v1/document-searchesA cited answer from permitted building records, with unknowns kept visible.
POST /v1/building-questionsA reviewed value linked to the original extraction and the responsible reviewer.
POST /v1/documents/{document_id}/reviewsFor owners, new managers, contractors, accountants
A reported action, a paid invoice and accepted completion remain distinct. Dates and installed-product identity need source evidence.
Dated inspection, renovation and work records with their supporting documents.
GET /v1/buildings/{building_id}/historyA sourced action linked to the building, system or known model element.
POST /v1/buildings/{building_id}/eventsDocumented roof, window and other component records, dates and information gaps.
GET /v1/buildings/{building_id}/componentsInstallation, service and replacement evidence for a confirmed asset identity.
GET /v1/assets/{asset_id}/historyAuthorized originals, model revisions, identifiers and history for a named successor.
POST /v1/building-handoversFor contractors, inspectors, residents, property managers
External write operations need delegated scope and delivery controls. Due dates need an applicable rule and supporting facts; records do not certify legal compliance.
Supported obligations, their basis, due dates and missing inputs.
GET /v1/buildings/{building_id}/obligationsScheduled inspections and work, including unresolved dependencies.
GET /v1/portfolios/{portfolio_id}/calendarSelected locations, relevant model objects, requirements and permitted documents.
POST /v1/work-ordersPhotos, measurements and a contractor's completion report attached to the job.
POST /v1/work-orders/{work_order_id}/evidenceThe owner's separate decision on the submitted work and any remaining issues.
POST /v1/work-orders/{work_order_id}/acceptanceFinding-by-finding evidence linking corrective work to the original inspection.
POST /v1/inspection-closeoutsA fault report restricted to the reporter's permitted building or space.
POST /v1/issue-reportsConflicting visits, access requirements and acknowledgments within an authorized portfolio.
POST /v1/visit-coordination-checksFor financial managers, accountants, owners, engaged suppliers
Use the customer's own agreements and costs. Accounting decisions require review; external accounting sync and supplier access need separately authorized connections.
Arithmetic and matched-line exceptions against the customer's own agreed prices.
POST /v1/invoice-checksDifferences between authorized scope, submitted evidence, acceptance and invoiced work.
POST /v1/work-invoice-reconciliationsAn engaged supplier checks only the contract and job scope explicitly shared with it.
POST /v1/supplier-invoice-prechecksTiming and quantity scenarios using documented costs and explicit assumptions.
POST /v1/maintenance-scenariosSource-linked component dates and costs for an accountant to review.
POST /v1/component-register-draftsReviewed records mapped to the customer's ledger and connected accounting system.
POST /v1/accounting-exportsFor owners, energy consultants, utilities, facility managers
Area definitions, estimated readings and weather methods stay visible. Continuous meter or BMS data needs a customer-authorized provider connection.
Building-linked readings or invoice-derived periods with units and estimate flags.
POST /v1/consumption-importsA consistent time series with original periods, gaps and source references.
GET /v1/buildings/{building_id}/consumptionA qualified weather-adjusted series using a documented method and area basis.
POST /v1/energy-normalizationsBefore-and-after consumption with weather, occupancy and other comparison limits.
POST /v1/retrofit-reportsRelevant weather signals linked to documented exposure and planned activities.
GET /v1/buildings/{building_id}/weather-alertsAn authorized meter-to-building mapping, provider details and feed health.
POST /v1/meter-connectionsAuthorized time series and alarms with units, timestamps and missing-data indicators.
GET /v1/assets/{asset_id}/telemetryFor manufacturers, distributors, installers, service companies
Manufacturer data, supplier contracts and confirmed asset identities are required for product-specific claims. No catalogue access implies access to the customer base.
Candidate links between the customer's purchased items and model elements, awaiting confirmation.
POST /v1/purchase-importsLicensed technical properties, identifiers and lifecycle information.
GET /v1/products/{product_id}Documents for a confirmed installed product and the applicable version.
GET /v1/assets/{asset_id}/documentsCompatibility evidence and required checks for a specified installation.
POST /v1/replacement-part-searchesCurrent stock, customer-specific price, lead time and the supplier's timestamp.
POST /v1/supplier-availability-checksAuthenticated recall or obsolescence notices matched to confirmed product or serial ranges.
POST /v1/recall-matchesAn owner's approved request sent to selected companies with only the necessary information.
POST /v1/service-requestsPermitted register facts and source freshness, without an invented certification verdict.
GET /v1/companies/{company_id}/factsFor architects, sustainability teams, manufacturers, reuse partners
Product EPDs and generic factors have different scopes. Model quantities and condition descriptions must be reviewed for the intended assessment or reuse decision.
Qualified quantities and licensed factors with lifecycle boundaries and uncertainty.
POST /v1/carbon-assessmentsThe matched declaration, validity period and scope of applicability.
GET /v1/products/{product_id}/environmental-declarationsDocumented components, dimensions, condition and disassembly evidence.
POST /v1/reuse-inventoriesA selected inventory sent to an authorized reuse partner under agreed sharing terms.
POST /v1/reuse-listingsFor portfolio teams, planners, surveyors, energy designers
Coverage, source dates, geometric meaning and onward-use rights vary by dataset. Exterior geometry cannot establish the interior or the actual condition of a site.
A footprint-based model using a sourced height or a clearly identified estimate.
POST /v1/exterior-modelsA proposed roof model from suitable licensed laser or building geometry, subject to coverage checks.
POST /v1/roof-reconstructionsPermitted geological and public context layers with resolution and source dates.
GET /v1/buildings/{building_id}/site-contextA preliminary scenario from qualified roof and shading data, with engineering checks identified.
POST /v1/solar-screeningsAn authorized building map with selected facts, source attribution and missing locations counted.
POST /v1/building-map-exportsFor boards, banks, insurers, transaction advisers, software teams
Sharing is case-specific and owner-authorized. A report summarizes evidence and gaps; it is not an automated lending, insurance or statutory approval.
Selected model, condition, maintenance and expenditure records with sources and dates.
POST /v1/building-reportsPermitted documents and unresolved gaps for a transaction, insurance claim or finance application.
POST /v1/evidence-packagesA PDF or SVG chart from permitted data, retaining units, source dates and attribution.
POST /v1/chart-exportsComparable measures and exceptions across only the owner's selected buildings.
POST /v1/portfolio-reportsAn expiring, revocable delivery link to a selected report or package.
POST /v1/share-linksFor owners, managers, energy teams, participating manufacturers
Requires sufficient eligible observations, comparable definitions and permission. Public statistical references can support early energy comparisons; there is no demonstrated large customer dataset today.
Eligible peer or public-reference comparisons with sample size, period and comparability limits.
POST /v1/energy-benchmarksHistorical recurrence and resolution statistics with missing records and cohort limits stated.
POST /v1/maintenance-benchmarksQualified reliability and service observations for identified equipment and exposure periods.
POST /v1/equipment-outcome-reportsEligible descriptive completion and return-visit statistics without exposing customer records or current bids.
POST /v1/service-outcome-reportsFor software vendors, integrators, enterprise it
These are proposed external platform controls. Existing app sessions are not a released machine-to-machine API contract.
The operations and source permissions actually enabled for the calling integration.
GET /v1/capabilitiesMachine access limited to agreed operations, owners and buildings, with an expiry.
POST /v1/integration-credentialsExplicit building and purpose scope, duration and audit evidence.
POST /v1/access-grantsStop future access through a specified grant while retaining the required audit record.
DELETE /v1/access-grants/{grant_id}Signed delivery events for approved jobs, records and model revisions.
POST /v1/webhook-subscriptionsDurable state, retry details and separate processing, coverage and review results.
GET /v1/jobs/{job_id}Itemized operations, agreed unit prices and source charges for the calling customer.
GET /v1/usagePermitted access, corrections, approvals and deliveries with timestamps and responsible actors.
GET /v1/audit-events03 / Built around the people who use building information
A model of your building, a room schedule or a selected evidence package. The proposed order service works without an app subscription.
Embed model processing, document extraction, charts and building answers in the product your customers already use.
Connect permitted client portfolios, inspections, maintenance history, budgets and reporting.
Obtain reviewable geometry, scope work and return inspection or installation evidence to the correct building.
Reach authorized installations with the right manual, product update, part candidate or service response.
Receive a case-specific view of consumption, documented work and information gaps with the owner's authorization.
Explore per-file model orders, metered processing, portfolio integrations or partner distribution. Scope, price, source charges and delivery terms are agreed before work starts.
Our endpoints, models and graphs still need permission to use their source material. Public access to a drawing does not by itself grant permission to adapt or redistribute it. Vendor datasets follow their specific licences. Customer records are shared only within the agreed purpose and recipient scope; aggregation needs its own basis.
Product connections can distribute approved information to relevant buildings without giving a supplier access to other customers' private records.