Skip to content

Integrations & API

Your website, your portals, your tools. One live source.

Forms, feeds, webhooks and a read-only API all work from the same live project data, so every channel shows the same units.

Aerial view of a new apartment building among tiled-roof houses in a coastal town, with a pool, gardens and the sea at sunset
A desk with a monitor showing a property website, and a phone and a tablet beside it
Long pool with sun loungers in an olive and lavender garden behind a terraced apartment building

One live source

Everything you connect reads the same project.

Enquiries arrive from your website, microsite, agent portal and booking widget. Feeds, webhooks, calendars, deposits and AI assistants work from the same live data. Choose an event to see where it goes.

Example integrations hub: website forms and portals on one side, feeds, webhooks and calendars on the other, all fed by one bildflow project.

Sample data
Show an event

Unit A102 is reserved: your webhooks get unit.status_changed, and portals reading your feed see it on their next read.

Two ways to connect

No code needed. Or bring your own.

Most teams copy a snippet or paste a URL. Developers get a read-only API, an OpenAPI document and signed webhooks.

No code

Copy a snippet or paste a URL. No developer needed.

  • Enquiry form and booking widget for your website, with your logo and brand colours.
  • WordPress plugin with your live inventory and the [bildflow_availability] shortcode.From Growth
  • Availability map you can frame into any page while the microsite is published.From Growth
  • Portal feeds in Kyero v3 XML or CSV, read by the portal from a secret URL.From Growth
  • Webhooks into Zapier, Make or n8n: paste the URL they give you.From Growth
  • Google Calendar sync for viewings, set up by each person.
  • Card deposits straight into your own Stripe account, or a bank transfer.From Growth

For developers

A read-only REST API, an OpenAPI 3.1 document and signed webhooks, on the same live data as the app.

  • Read-only REST API for projects, units and the availability map, with bf_ keys.From Growth
  • OpenAPI 3.1 document at /api/public/openapi.json, no key needed.
  • Webhooks signed with HMAC-SHA256, retried 6 times over about 33 hours, with a delivery log and Resend.From Growth
curl "https://bildflow.io/api/public/units?project=harbour-views" \
  -H "Authorization: Bearer bf_your_key"

Catalogue

Everything bildflow connects to.

Each item shows the plan it starts on and links to its step-by-step guide.

Your website

Forms, maps and pages that show live units and send enquiries straight in.

Property portals

Feeds that portals read from a secret URL, refreshed when your units change.

  • Kyero v3 XML feed

    From Growth

    Kyero, and portals that read Kyero feeds, pull your available units from a secret URL. Sold units drop off.

    Read the guide: Kyero v3 XML feed
  • CSV feed

    From Growth

    For portals and agencies that import a spreadsheet, read from a secret URL in the same way.

    Read the guide: CSV feed

Automation tools

Tools that accept webhooks. There is no listed app: you paste their URL in as an endpoint.

Calendar and payments

Viewings in your own calendar, deposits in your own Stripe account.

AI assistants

Ask Claude or ChatGPT about your projects. Every action is recorded in your audit trail.

  • Claude

    From Pro

    Connect Claude to read your workspace and create tasks, lead notes or leads. Leads and buyers stay off until an owner or admin switches them on. A lead it creates is routed and announced like any other.

    Read the guide: Claude
  • ChatGPT

    From Pro

    Connect ChatGPT to read your workspace and create tasks, lead notes or leads. Leads and buyers stay off until an owner or admin switches them on. A lead it creates is routed and announced like any other.

    Read the guide: ChatGPT

Developers

Read your inventory and receive events in your own code.

What it doesn’t do (yet)

So you can plan around it.

  • The API is read-only. New leads arrive through the enquiry form, booking widget, microsite and agent portal, and your team (or an AI assistant) adds them in the app. They do not arrive through the API.
  • There is no listed Zapier app. Zapier, Make and n8n connect through webhooks.
  • Feeds come in two formats, Kyero v3 XML and CSV, and portals read them on their own schedule.

Questions about integrations

Can we add or change data through the API?

No. The API is read-only: projects, units and the availability map. New leads arrive through the enquiry form, booking widget, microsite and agent portal, and your team (or an AI assistant) adds them in the app.

Is there a Zapier app?

Not a listed one. In Zapier, start a Zap with Webhooks by Zapier and Catch Hook, then paste its URL in as a bildflow endpoint. Make and n8n work the same way.

How do property portals get our units?

They pull them. You create a feed in Kyero v3 XML or CSV and give the portal its secret URL. The portal reads it on its own schedule, so a change shows on its next read.

What if our server is down when an event is sent?

bildflow tries again 6 times over about 33 hours. The delivery log shows every attempt, and Resend sends a failed delivery again.

Which plan do we need?

The enquiry form, booking widget and Google Calendar come with every plan. The API and WordPress plugin start on Growth, portal feeds on Growth and webhooks on Growth. Claude and ChatGPT start on Pro.

Do buyers’ and leads’ details go through the API?

No. Buyers, leads, documents and internal fields are never part of the API, and custom fields appear only when you mark them public. Webhook events carry just the personal data each event needs, such as a new lead’s contact details.

Connect your first project.

Start today with the enquiry form and booking widget. Add feeds, webhooks and the API when your plan includes them.

We use cookies for analytics. Cookie Policy