Parcel Enrich: Full Catalog

How it works

1. Omit both fields and preset to request the entire current Enrich catalog. Nulling both has the same meaning; an empty fields array is invalid. Read the returned field map dynamically without a fixed count or list.
2. For a narrower bundle, send {"lat":40.75,"lng":-73.99,"preset":"terrain"}. One Enrich preset can be combined with individual fields, for example fields: ["owner"], and the server returns their union without duplicates. Enrich presets are separate from Fetch presets.
3. 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.
4. 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.
5. 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.
6. 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.
7. 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.
8. This example shows the no_match outcome: no field calculation ran. A matched response instead contains every current field with its own status, provenance and hints; partial failures do not discard successful fields.

Example response