4 Get Task Summary

Quick overview of the search results: total parcels found, how many succeeded, how many failed. Returns 409 if the task is not yet complete.

What this step does

It returns an aggregate count for the finished task: total parcels processed and a by_status breakdown of how many success versus failed. It reads only the tallies, not the individual parcel rows.

Why it's needed

Before you pull down every parcel polygon (Step 5) or promote them into the supply chain (Step 6), the summary lets you gauge the search's quality at a glance โ€” a high failure count is a signal to revisit your input points or reach for a fallback path rather than ingest a mostly-empty result. Because it reports on a finished task, it returns 409 if the task hasn't reached a terminal state yet, which is why the poll in Step 3 comes first.

When you can skip it

This step is optional. The full results in Step 5 already carry per-point status, so if you intend to fetch and review those anyway you can go straight there. Use the summary when you want a cheap up-front health check without paginating the whole result set.

Next Step

โ†’ Step 5: View Results and Map (GET /cadastral/parcels/results/:id)