The chain
One project, every party, resolved
A project is not a record, it is a chain. Veritrace holds each link and the parties attached to it. The schema is canonical; the labels are local. Switch the example to see the same chain render in a different jurisdiction.
City of Gold Coast · local term for a planning submission: Development Application
Select a stage to see what we hold
Planning submission
Development Application
DA-2025/0873
What we hold at this stage
- Local reference
- DA-2025/0873
- Lodged
- 2025-11-04
- Canonical stage
- under_assessment
- Site area
- 4,120 m2
Verification
A switchboard number is not a contact record
Category incumbents publish company details. Veritrace publishes named roles, direct lines and the date each record was last verified, so you can judge the age of what you are acting on.
Typical incumbent record
Veritrace record
Verification is a dated event on the record, not a claim about the record. Where a contact has not been re-checked inside 30 days, the interface says so.
Illustrative records. Field names match the public data dictionary, entity VT-C-40218832.
Data delivery
Built as infrastructure
Read the registry the way it suits your stack: REST API, webhooks, bulk export, or direct warehouse delivery.
REST API
Projects, parties, companies and jurisdictions. Cursor pagination, ETag caching, ISO 8601 timestamps, one Veritrace ID per object.
GET /v1/projects?jurisdiction=VT-J-00042&stage=tender
Webhooks
Stage changes, new parties resolved and contact re-verification events, delivered with a signed payload and replay window.
POST /your-endpoint event=project.stage_changed
Bulk export
Daily deltas or full snapshots in CSV and Parquet, partitioned by country and jurisdiction.
s3://veritrace-delivery/2026-08-04/country=DE/
Warehouse delivery
Managed shares into Snowflake, BigQuery and Databricks, with the same schema as the API.
SELECT * FROM veritrace.public.projects