Commercial Units Developer API commercialunits.com →

Overview

The Commercial Units Developer API lets you pull your own listings out of commercialunits.com as JSON — including image URLs — so you can display them on your own website, intranet, or app.

You already manage your listings in the Commercial Units dashboard: buildings, sizes, usage types, prices, photos, availability. The developer API exposes that same inventory over a simple, read-only HTTP interface, so the listings you keep up to date in one place stay in sync everywhere you show them.

Who it's for

The developer API is for CLLs — Commercial Landlords and Leasing agencies — who:

  • already list commercial space (offices, retail, F&B, industrial, clinics, …) on Commercial Units, and
  • want those listings to appear on their own website, branded as their own, without re-entering the data.

A typical user is a landlord or agency with a marketing site (a "Available Spaces" or "Our Portfolio" page) who wants it to render straight from their live Commercial Units inventory instead of a hand-maintained spreadsheet.

The developer API is read-only and scoped to your own active listings. It is not a public/global search API and it does not return other landlords' inventory. One API key = one organisation, in one country.

What you get

  • GET /v1/listings — a paginated list of your active listings as JSON.
  • GET /v1/listings/{id} — a single listing by its id.
  • Image URLs — each listing includes an images array of public image URLs you can drop straight into <img src="…">.
  • CORS for your domain — register your website's origin(s) in the dashboard and the API will return the right Access-Control-Allow-Origin so browser fetch from your site works.

How it fits together

  Your website  ───fetch / curl───►  Commercial Units Developer API
  (your domain)    Bearer sg_live_…    api.commercialunits.com/v1/...
        ▲                                        │
        │                                        ▼
        │                              Your active listings
        └──────  <img src="…">  ◄──────  (JSON + image URLs)
  1. You create an API key in your dashboard (Settings → Developer). It is country-prefixed — e.g. sg_live_… for Singapore — and the prefix decides which country's API the request is routed to.
  2. You call the API with that key in the Authorization header.
  3. You render the returned JSON on your page, and embed the listing photos by their public image URLs.

Per-country by design

Commercial Units keeps each country's data fully isolated. That carries through to the developer API:

  • Your key belongs to one country (the prefix — sg, my, uk, …).
  • It only ever returns listings from that country, owned by your organisation.
  • The key prefix also routes you to the correct regional API host automatically (see Endpoints → Base URL).

If you operate in more than one country on Commercial Units, you'll create a separate key per country.

Next steps