# 03. Look up a property **Level:** beginner ## Business outcome Resolve one property by address, APN, parcel ID, or coordinates inside an entitled county. Use this when the county and exact locator are already known. For a free-form address or APN without a county ID, use [Location Search](../18-location-search/) first. An interactive field uses suggest → retrieve; a one-off server request uses forward. ## API operations - `POST /v2/parcels/lookup` ## Before you run it Complete the repository [Getting started](../../README.md#get-an-api-key), copy `.env.example` to `.env`, and replace the synthetic Market, Place, parcel, and address values with IDs returned for your Organization. The examples never discover an ID and then assume that it grants access. ## cURL ### Property ```bash curl --fail-with-body --request POST \ --url "${GRIDICS_API_BASE_URL}/v2/parcels/lookup" \ --header "x-api-key: ${GRIDICS_API_KEY}" \ --header "Content-Type: application/json" \ --data "{\"place_id\":\"${GRIDICS_PLACE_ID}\",\"address\":{\"street\":\"${GRIDICS_ADDRESS}\",\"postal_code\":\"${GRIDICS_POSTAL_CODE}\"},\"fields\":[\"parcel.id\",\"parcel.apn\",\"parcel.address\",\"parcel.lot_area\",\"parcel.vacant\"]}" ``` ## Run a port ### Python 3.11+ ```bash cd recipes/03-property-lookup/python python3 main.py ``` ### Node.js 20+ ```bash cd recipes/03-property-lookup/nodejs node main.mjs ``` ### TypeScript 5 / Node.js 20+ ```bash cd recipes/03-property-lookup/typescript npm --prefix ../../.. install npm --prefix ../../.. run build node ../../../dist/recipes/03-property-lookup/typescript/main.js ``` ### PHP 8.2+ ```bash cd recipes/03-property-lookup/php php main.php ``` ### .NET 8+ ```bash cd recipes/03-property-lookup/csharp dotnet run ``` ### Java 21+ ```bash cd recipes/03-property-lookup/java javac -d build ../../../languages/java/GridicsCookbook.java Main.java && java -cp build Main ``` ### Go 1.22+ ```bash cd recipes/03-property-lookup/go go run . ``` All ports write the same normalized JSON envelope to stdout. Use `GRIDICS_DRY_RUN=1` to inspect requests without sending them. Use `GRIDICS_FIXTURE_MODE=1` with the test server for deterministic examples. ## Usage and limits One standard request plus the returned parcel row. These are cookbook safety defaults. Your current plan, capabilities, geography, quotas, and pricing are authoritative in the Gridics Developer Portal. ## Important behavior Choose exactly one lookup form. The checked-in request uses an address; edit the recipe request or use the APN/parcel/coordinate variants described in `docs/request-reference.md`. A `409` means the locator was ambiguous; do not silently choose a result. The returned `data.id` is the parcel identifier for subsequent parcel calls. Keep the returned `place_id`; do not substitute an unrelated county ID. ## Expected result The command exits `0` only when every required step succeeds. Output includes the recipe ID, API base URL, request count, per-step HTTP status, returned data, and a `fixture` or `live` execution label. Optional capability-gated steps are reported as `unavailable`; they are never filled with invented values. ## Tests From the repository root, run `python3 tests/validate_repository.py` and the language command documented in [CONTRIBUTING.md](../../CONTRIBUTING.md). Normal tests use synthetic fixtures and make no paid requests. For free-form address/APN search without a required county ID, start with [recipe 18](../18-location-search/README.md).