Data API
Enums
Allowed values for fixed fields across the Data API datasets.
These are the exhaustive allowed values for fields that accept a fixed set of strings. Pass the machine value (the left column) when you filter on one of these fields. Filtering with a value outside a field’s set is rejected with a 400 request-validation error that names the allowed values (see Errors), the same way an unknown filter or sort key is; valid values match on exact string equality. The OpenAPI schema also advertises these values inline. The MCP search tool schemas advertise structure only (fields, types, and relational sub-fields); the enum vocabularies are served on demand by the search_fields and get_fields tools, backed by Search Fields, so an integration can still discover them without consulting this page.
Project: stage
The entitlement/permitting stage of a project.
| Value | Meaning |
|---|---|
pre_filing | Project is identified but no formal application filed. |
filed | A formal land-use application has been submitted. |
under_review | Active agency or public review in progress. |
approved | Discretionary land-use approval granted. |
permitted | A building, demolition, or site-work permit has issued, or construction financing has closed: cleared or funded to build. |
under_construction | Construction has commenced and is physically underway. |
completed | Construction is finished or occupancy reached. |
Project: disposition
Outcome or current disposition for projects that are no longer actively moving forward.
| Value | Meaning |
|---|---|
active | Project is proceeding normally. |
denied | Application was denied by the reviewing authority. |
withdrawn | Applicant withdrew the application. |
expired | Approval or permit lapsed without action. |
stalled | No activity for an extended period. |
cancelled | Project cancelled by the applicant or authority. |
Project: primary_use
The primary use category of a project.
| Value | Meaning |
|---|---|
multifamily | Multifamily residential. |
mixed_use | Mixed use (residential plus commercial). |
office | Office. |
industrial | Industrial. |
retail | Retail. |
hotel | Hotel and hospitality. |
institutional | Institutional (civic, government, religious). |
educational | Educational (schools, universities). |
r_and_d | Research and development or lab. |
other | Other or unclassified. |
Signal: signal_type
The 19 event types a signal can represent.
| Value |
|---|
project_announcement |
pre_application |
site_acquisition |
demolition_permit |
site_prep |
entitlement_application |
environmental_review |
public_review |
rfp |
entitlement_approval |
entitlement_denial |
withdrawal |
expiration |
permit_filed |
permit_issued |
construction_loan |
under_construction |
team_update |
completion |
Values documented in the Guides
The following fields accept a fixed set of values that are described with full definitions in the Guides reference. The API accepts the same machine values listed there.
| Field | Guide |
|---|---|
account_types (accounts) | Account Types |
role on has_account (project_accounts) | Project Roles — account roles like gc, developer |
role on has_contact (project_contacts) | Contact Types — contact roles like gc_contact, attorney |
track (signals) | Signal Types |
enrichment_status (contacts) | Contact Enrichment |
Filtering an enum field with a value outside its documented set returns a 400 request-validation error that lists the allowed values, not zero rows. An unknown filter or sort key is likewise a 400. See Errors for the exact response shape.