Commercial Units Developer API
Pull your active listings as JSON (with image URLs) and embed them on your own website. For commercial landlords and agencies (CLLs) who list on commercialunits.com and want to syndicate that inventory to their own site.
These docs are published at developer.commercialunits.com. The source lives in tenants/commercialunits_com/developer-docs/ in the Gillside monorepo.
Documentation
| Page | What it covers |
|---|---|
| Overview | What the developer API is, who it's for, how it fits together |
| Quickstart | Copy-paste: create a key, curl your listings, render them on a page |
| Authentication | API keys, the country prefix, the Authorization header |
| Endpoints | GET /v1/listings, GET /v1/listings/{id}, the JSON schema, base URLs |
| CORS & Embedding | Register your origin, browser fetch, embedding images |
| Rate Limits & Errors | Throttling headers, error codes (401 / 403 / 404 / 429) |
At a glance
curl https://api.commercialunits.com/v1/listings \
-H "Authorization: Bearer sg_live_xxxxxxxxxxxxxxxxxxxxxxxx"- One key, one country. Keys are country-prefixed (
sg_live_…,my_live_…). The prefix routes the request to your country's data — there is no cross-country access by design. - Only your own active listings. The API returns the listings owned by the organisation the key belongs to, with
status = "active". Drafts, leased, expired, and deleted listings are never returned. - Images are plain public URLs. Embed them with
<img src>directly — no CORS needed. Use the CORS-enabledfetchonly when you need the JSON in the browser (or want to draw an image to a<canvas>).