Letsbuild + Ziggu

Letsbuild and Ziggu connect through Ziggu's public REST API. The snags your site team records reach Ziggu daily, where you decide which ones to publish to the buyer. From there the buyer follows the points on their own home, reports new ones, and confirms a repair when it is done. That confirmation travels back to Letsbuild. Five property developers run this today: Immobel, ION, AG Real Estate, Vesta and Nextensa.

Key takeaways

• Letsbuild connects to Ziggu through Ziggu's public REST API. Stratokit and Peliqan both offer a ready-made connector, or you build it yourself.
• Snags sync daily. Nothing is visible to the buyer until someone on your team publishes it.
• Buyers can report a point in Ziggu. Your team reviews it and pushes it into Letsbuild, so nothing reaches the site team unfiltered.
• A buyer can be asked to confirm a point is resolved, and that status goes back to Letsbuild.
• Immobel, ION, AG Real Estate, Vesta and Nextensa run this connection.

Why buyers do not get a Letsbuild login

Letsbuild is built for the people on site. It carries every point on every unit, in shorthand, with the internal statuses your team needs to run the work. A buyer reading that does not get reassurance, they get questions, and they see work in progress that was never meant for them.

The usual alternative is email, and email is worse. A buyer reporting a loose socket sends it to whoever they last spoke to, that person forwards it, and three messages later somebody has to remember to check whether it was done. Multiply by two hundred apartments.

Ziggu is the layer in between. The buyer sees the points you published, on their own home, in language written for them. See Reports.

Nothing reaches the buyer until you say so

The daily sync brings points into Ziggu. It does not put them in front of the buyer. Someone on your team publishes them, and that gap is deliberate: a point logged at eight in the morning with a photo and three words is not what you want a buyer reading at nine.

That gives you two separate controls. Publishing decides when a buyer sees a point. Access per report decides who sees it, which is what keeps buyer A out of buyer B's punch list on the same floor.

Closing a point without an argument

In Ziggu you can ask the buyer to confirm a point is resolved. They press one button, and that confirmation goes back to Letsbuild so your site team sees it where they work.

The value is not the click. It is that at the provisional handover, and again a year later, nobody is arguing about whether something was fixed. The buyer said so, in writing, at the time.

What data moves between Letsbuild and Ziggu

The first column is the name your team knows from the app, the second is the endpoint the connection writes to.

‍

How do you connect Letsbuild to Ziggu?

Three routes, same API underneath. Pick the one that matches who is going to maintain it.

1. Use Stratokit. They build connectors for construction software, so they know what a snag is and what a handover looks like before you explain it.
2. Use Peliqan. They come at it from the data side, which suits you better if Ziggu and Letsbuild are two sources among several you already move around.
3. Build it yourself, or have your own partner do it. Request an integration token from Ziggu and write against api.ziggu.app/public. Endpoint reference: Ziggu API documentation.

Whichever route you take, the mapping decision comes first: which Letsbuild project corresponds to which Ziggu project, and how a point finds the right unit inside it. On a development with two hundred apartments that is the whole job, because every buyer has to see their own points and nobody else's. Settle it, run it on one building, and look at what a buyer would see before you widen it.

Where teams use it

Getting through provisional handover without a spreadsheet

The points recorded at handover are already in Letsbuild. Published to Ziggu, each buyer sees their own list and confirms what has been fixed, so the list closes itself instead of being chased by phone.

Catching what the buyer spots, without the inbox

Buyers notice things after they move in. In Ziggu they report them against their own home, with a photo, and your team decides whether it belongs in Letsbuild. See how property developers use Ziggu.

Talking to the buyer without giving away the site tool

Contractors work in Letsbuild, which has no conversation with the buyer in it. When a partner needs to arrange an appointment directly, you can give that partner a Ziggu account instead of a phone number, and the exchange stays on the project.

What Letsbuild and Ziggu do not do

• Points sync daily, not the moment they are recorded. A point logged on site this morning is in Ziggu tomorrow.
• Nothing reaches the buyer automatically. Someone on your team publishes it. That is a control, and it is also work.
• A buyer-reported point does not go straight into Letsbuild. Your team reviews it first. That is deliberate.
• Projects and units are matched, not created. A point that does not resolve to something that already exists in Ziggu has nowhere to land, so the mapping has to be right before you scale up.
• Ziggu's API is rate limited to 60 requests per minute across all endpoints, which is what shapes the first load of an existing punch list.

Questions about the Letsbuild integration

Who is running this today?

Immobel, ION, AG Real Estate, Vesta and Nextensa.

Does the buyer see every point?

No. Nothing is visible until your team publishes it, and access is set per report, so a buyer sees their own home and not their neighbour's.

Can a buyer report a point themselves?

Yes, in Ziggu, against their own unit. Your team reviews it and pushes it into Letsbuild if it belongs there.

Can the buyer confirm a point is resolved?

Yes, and that confirmation goes back to Letsbuild as a status update. One button for them, a written record for you.

How quickly does a point appear?

Points sync daily. After that a buyer sees it as soon as your team publishes it.

Do our contractors need Ziggu accounts?

Usually not. Partners work in Letsbuild. Give a partner a Ziggu account when you want them talking to the buyer directly, for instance to arrange an appointment, because Letsbuild has no conversation with the buyer in it.

We use Archisnapper instead.

Same kind of route. See Archisnapper and Ziggu.

Last verified: 28 August 2026.