For developers

A clearer contract for changing records.

Bring permit and contractor activity into your software with ObservedWork API and data feeds.

Discuss your territory and workflow with our team. Data access, delivery options and evaluation scope are confirmed separately.
Data delivery workspace showing six Chicago permit records and seven source-linked export fields.

Delivery example. Six Chicago source records and their export fields. Integration scope and availability are agreed separately.

01

Define the integration before building

This page is an integration overview, not a public API reference. Contact us to confirm availability, authentication, sample records, coverage, delivery format and service terms for your application. Our public Seattle walkthrough shows source fields and interpretation limits; it does not demonstrate an ObservedWork API endpoint.

02

Stable references

Keep record and account references consistent across your workflow. Clear identity context and source information make corrections easier to understand and reconcile with your own systems.

03

Understandable changes

Separate new records, corrections, backfills, and identity changes. Source dates and observation dates give your team the context to decide which events belong in downstream workflows.

04

Delivery designed for retries

Discuss record delivery, update cadence, versioning, and coverage with our team. Share your integration requirements so we can define the data contract and delivery approach for your application.

05

Change feeds and deltas

A consumer that restarts should resume without missing changes and without reprocessing everything it has already seen. Discuss cursor semantics, event ordering, replay windows and idempotency with our team before you build. The useful question is not how many records exist; it is how your system learns that one of them changed.

06

A new permit and a newly observed permit are different events

A record discovered during a backfill is not a fresh opportunity, and treating it as one puts stale work into a rep’s queue. Source dates and observation dates travel with every record so your pipeline can tell them apart. Decide deliberately which event types belong in an alert and which belong only in your archive.

Discuss an integrationWhy date semantics matter
A clearer view starts here

Your next account
is already doing the work.

Bring the work behind each contractor into focus. Start with your territory.

Create your free account

Free account. No credit card.