Data from the Archicad model in your own systems Quantities and properties without retyping Via the Archicad API

Custom Archicad integration development

Appfront builds integrations with Archicad, the BIM software from Graphisoft. The model holds a lot of data that is needed outside Archicad: quantities, properties, spaces and statuses. We connect the model to your estimating, planning or in-house systems, so that data is not retyped and can flow back into the model.

What is an Archicad integration?

Archicad is the BIM software from Graphisoft, widely used by architects. The model contains not only geometry but also data: walls, floors and window frames with their properties, spaces with floor areas, and custom properties you add yourself, such as a status or a code. Graphisoft offers a JSON interface over HTTP, a Python wrapper for it, and a C++ API for custom add-ons.

That data is often needed outside Archicad, and that is where things go wrong. Quantities are copied by hand into the estimating package. Spaces and floor areas are exported to a spreadsheet for the client. And anyone who tracks a status or code in another system doesn't see it reflected in the model.

We build custom because practices and models differ: which properties you use, which data needs to go where, and whether the integration runs on a workstation with Archicad or as an add-on inside Archicad itself. We look at which route fits in the first step, together with you.

Data from the model

Elements, properties and spaces into your own systems.

Back to the model

Statuses and codes written back as a property.

Via the Archicad API

JSON interface, Python or a custom add-on.

How we build your Archicad integration

We start with your models: which properties you use, which data currently leaves by hand, and which system needs it. We often begin with quantities or spaces, because that is where most of the time goes. Once the first integration runs well, the route back to the model follows. That way you quickly see whether the integration saves time. We test on your own models, so the integration works with the properties you actually use.

1
Mapping your models

Properties, data and systems.

2
Choose a route

JSON interface, Python or an add-on.

3
Building the integration

Data from the model and back.

4
Go-live and maintenance

Go-live, and maintenance for new Archicad versions.

What an Archicad integration actually does

The components below feature in almost every Archicad integration. Which ones you need depends on your models.

Elements

Per type and storey.

Properties

Including your own properties.

Spaces

Spaces with floor areas.

Quantities

Into your estimating.

Write-back

Status and code written back.

Validation

Missing data flagged.

Who we build an Archicad integration for

The integration is intended for practices and companies that work with Archicad. The more often data from the model is needed elsewhere, the more an integration delivers.

Architecture firms

Spaces and floor areas. The client wants to see them.

Contractors

Quantities for estimating. No retyping.

Developers

Homes and plots. Statuses matter most.

Software suppliers

A product alongside Archicad. The API is the core.

Technology and integrations

This page covers integrations with Archicad. If you work with Revit, see our page on the Revit integration. For exchange via open formats, there is our page on the IFC integration, and for software for practices, our page on architectural practice software. You can read about our approach on custom software development.

If you don't draw in Archicad but in the DWG-based CAD software BricsCAD, and you want to exchange bills of materials and item data with your ERP, take a look at our Bricsys BricsCAD integration.

Archicad JSON interface Python wrapper Add-On API in C++ Elements Properties Zones Quantities IFC Log

Why Appfront for your Archicad integration?

Quantities transferred by hand, and a status that exists only outside the model, cost time and introduce errors. We build on that: data from the model where it's needed, the way back into the model, and an integration built on Archicad's API.

No retyping

Quantities carry over automatically.

Model up to date

Status and code written back to the model.

On the API

As Graphisoft intends.

Security and privacy for an Archicad integration

The integration processes design data from your projects. That data stays within your own environment, credentials are stored encrypted, and every exchange is logged.

Where the integration stores data outside the workstation, it does so in a European data centre, with encrypted storage and daily backups.

Frequently asked questions about an Archicad integration

Questions practices ask before they get started.

Archicad is Graphisoft's BIM software. Architects use it to create a model of elements, properties and zones, from which drawings and schedules are generated.

Graphisoft offers a JSON interface over HTTP and a Python wrapper for it, plus a C++ API for custom add-ons. The JSON interface talks to a running instance of Archicad. Which route fits depends on what the integration needs to do. For data that is only needed occasionally, the JSON interface is often enough; for work that has to happen inside Archicad itself, an add-on is the better choice.

For exchange with other parties it often is. An integration makes sense if you need the data repeatedly in your own system, or if you want to write data back to the model. An IFC export is a snapshot; an integration keeps the data up to date while the design is still changing.

Yes. Quantities per element or per code go from the model to your estimating software, and they are updated when the model changes. You see what has changed since last time, so the estimator doesn't have to check the whole list again.

Yes. A status or code from your own system comes back as a property in the model, so the model shows what has been decided elsewhere. In Archicad, a designer can then see, for example, which homes have been sold or which components have already been ordered.

We test the integration on the new version before you upgrade, and adapt it if the API has changed. That way you can upgrade when it suits your practice, without the integration grinding to a halt.

For architectural practices, contractors and developers who repeatedly need data from Archicad in other systems, and for software vendors who want to connect their product to Archicad.

Archicad connected to your own systems?

Tell us what data you need from the model and where it currently goes by hand. We'll show you which route is available and what the integration looks like.

Edit content