ausdata.io

Home / Endpoints / Approvals vs completions

Approvals vs completions

Building approvals against building activity completions, the housing supply pipeline.

history mode ABS

What it answers

How much of what gets approved actually gets built? This lines up ABS building approvals against ABS building-activity completions to expose the housing supply pipeline and the gap between the two. It shows where dwellings are stalling between sign-off and handover.

Call it

curl -H 'Authorization: Bearer ak_your_key' \
  https://api.ausdata.io/v1/approvals-vs-completions

History mode

Add start_period and end_period to walk the series back through time instead of returning only the latest point.

curl -H 'Authorization: Bearer ak_your_key' \
  'https://api.ausdata.io/v1/approvals-vs-completions?start_period=2015-Q1&end_period=2024-Q4'

Returns

Every response uses the same envelope, {data, meta, links}. The data field carries the answer (an object for a single snapshot, a list when there is one row per entity). The meta field carries the trust contract: the reference periods, retrieved_at, the per-source attribution you reproduce on publish, and the stale flag. The links field offers a csv alternative when one is available.

{
  "data": { ... },
  "meta": {
    "endpoint": "/v1/approvals-vs-completions",
    "query": { ... },
    "period": { "start": "...", "end": "..." },
    "row_count": 1,
    "retrieved_at": "<ISO-8601 UTC>",
    "sources": [
      { "name": "...", "url": "...", "attribution": "..." }
    ],
    "stale": false,
    "stale_reason": null,
    "server_version": "..."
  },
  "links": { "csv": null }
}

Draws from

This signal joins data from one source. Each source page lists the underlying datasets and canonical series.

Cross-source signals join multiple sources into one response. Reliability: a signal returns current data or a clear 503; it never serves an older vintage as the current answer.

Related signals

All endpoints