Indax

API overview

Industrial facilities in the United States as linked records you can query.

The Indax API serves industrial facilities in the United States as linked records: the Sites, the Organizations that operate and own them, their Permits, the Projects at each Site, and dated Events such as permit actions, inspections, violations and enforcement actions.

Each value carries a status and, where available, a confidence score. Indax publishes changes to the API once a day.

Record types

The API returns one record per real-world entity, with one served value per field.

TypeID prefixRouteWhat it is
Organizationorg_/v1/organizations/{id}A company or an agency.
Sitesite_/v1/sites/{id}A facility at one address.
Projectprj_/v1/projects/{id}A new plant, expansion or modification at one Site (Projects).
Permitpmt_/v1/permits/{id}A permit issued to a Site.
Eventevt_/v1/events/{id}A dated permit action, inspection, violation, enforcement action or filing.

Person records (per_) are planned.

EdgeFrom → ToMeaning
operatesorganization → siteThe current operator. A Site has at most one.
ownsorganization → siteAn owner. A Site can have several.
located_atproject → siteWhere the Project happens. Exactly one per Project.
undertaken_byproject → organizationWho carries out the Project. Zero or one.
has_permitsite → permitThe Site holds the permit.
issued_topermit → organizationThe permit applicant.
occurred_atevent → siteThe event happened at the Site.
part_ofevent → projectThe event belongs to the Project.
concernsevent → permitThe event is an action on the permit.

Records embed their non-event edges, and /edges pages them. Read events through the Site and Project timelines (Relationships and timelines).

IDs are stable. If two records turn out to be the same entity, the old ID answers 301 with the surviving ID.

Next

Start with Getting started to make your first call.

On this page