Relationships and timelines
Follow the links between records and read a Site's or Project's dated events.
Edges: GET /v1/{collection}/{id}/edges
Filter with label (repeatable) and direction (in, out or both). Page with cursor and limit (up to 200, default 50).
| Edge property | Meaning |
|---|---|
confidence | 0 to 1, on the same scale as attribute values. |
method | hard_key: matched on an exact identifier. rule: set by a fixed Indax rule. splink: a probabilistic match. geo: matched by distance, within 500 m. |
from | The date Indax first saw the link, not the date operation began. |
Indax never merges companies on a name alone. If a Site's owner is spelled two ways, both appear as owners. When you group by company, check both the operator and the owners.
Timelines: GET /v1/sites/{id}/timeline
Sites and Projects have timelines, newest first. Filter with since and until (YYYY-MM-DD) and event_type (repeatable). GET /v1/events/{id} returns one event in the same shape.
| Event type | What it covers |
|---|---|
permit | Permit applications, drafts, final actions, withdrawals and construction permits. |
filing | Operating status changes, program registrations, certifications and injury filings. |
inspection | Inspections and stack tests. |
violation | Violations, by severity. |
enforcement | Formal and informal enforcement actions. |
notice, incentive | Public notices, tax abatement applications, grants and loans. |
Each event also has an event_subtype; the full list is in GET /openapi.json. date_kind says which date event_date is, for example issued, occurred or closed. project_forming is true when the event can start or extend a Project.