1 Search Parcels (JSON)

Submit a parcel search using an inline JSON body with 3 US points. The response contains a task ID used in subsequent steps.

What this step does

It hands Epoch a GeoJSON FeatureCollection of point coordinates and asks it to resolve each point to the official cadastral parcel that contains it. The response is a parcel_search_task resource whose data.id is captured into {{parcel_task_id}} โ€” every later step (poll, summary, results, ingest) addresses that id. For small requests (โ‰ค500 points) the lookup runs synchronously, so the task comes back already in a terminal overall_status (completed / completed_with_errors / failed) with links.results populated.

Why it's needed

This is the entry point that turns raw coordinates into resolvable parcels. Nothing downstream exists without it: the task id it mints is what the results, summary, and ingest calls all reference. It is also where the search scope is fixed โ€” the set of points you send here is the set of parcels the rest of the workflow operates on.

Why you'd choose this (vs file upload)

Use the inline JSON body when the points are already in hand as a small, structured list โ€” a handful of sourcing coordinates from your own system. It is the simplest path: one call, and for โ‰ค500 points the result is ready immediately with no polling loop to run. Reach for the file-upload variant (Step 2) instead when the points live in a CSV/GeoJSON/Shapefile you'd rather not hand-serialise, or when the batch is large enough that asynchronous processing is unavoidable.

Next Step

โ†’ Step 2: Search Parcels File Upload (alternative), the Step 2b / 2c variants, or Step 3: Poll Task Status