Parcel Enrich: Selected Fields

How it works

1. Send POST /v1/enrich with fields: ["owner", "slope_degrees"] for a small first review. fields always contains individual Enrich IDs; selecting a bundle uses the separate preset parameter.
2. Authenticate with your own Mireye account or API token. Enrich currently costs zero customer credits; account rate limits still apply. Use a 120-second client timeout and allow for larger responses when requesting every field.
3. Supply either a US address or lat and lng, never both. Check resolved_location and address geocode provenance, then parcel_match.status: only matched runs field calculations. Ambiguous, no_match and unavailable return empty fields; those outcomes are not evidence that requested facts are absent. Never select an ambiguous candidate automatically.
4. For a matched parcel, read analysis_point: point data uses the stored parcel centroid or input fallback, while polygon calculations use the matched boundary. Preserve each field's value, unit, source, source_url, confidence, timestamps, notes and interpretation_hints. Keep all returned fields, including unfamiliar IDs and nested JSON values.
5. Inspect each field's ok, absent or failed status and partial_failures even after HTTP 200. Absent means null with an explanatory note; failed means null with error and retryable. Preserve retryable: false and meaningful null metadata. Nonfailed error/retryable and lifecycle may be omitted; do not require them or turn missing data into zero.
6. The sample below illustrates a response shape, not a live result for the example coordinate. Try your own parcel in the Enrich playground at https://www.mireye.com/dashboard/enrich or https://www.mireye.com/integrate. Choose names from https://docs.mireye.ai/api-reference/enrich-fields; Fetch's /v1/meta/fields catalog describes different selectors.

Example response