EirePlan
Eireplan API
Endpoints/Precedents API

Site History

Find planning history around an address, eircode, or coordinates.

Use this request to find planning application history around a site using address text, eircode, or map coordinates.

#Request

GET /ext/v1/precedents/site-history

#Valid Query Combinations

  • Address search: address can be passed once or repeated (for example, address=...&address=...).
  • Eircode search: pass eircode when you have a known postal code.
  • Coordinate search: pass lat and lon together, with optional radius_m.

You can include limit with any of the combinations above.

Defaults:

  • radius_m defaults to 5.
  • limit defaults to 100.

#Query Parameters

ParameterTypeRequiredDescriptionExample(s)
addressstringNoSite address text. Supports single or repeated query params.address=15%20Example%20Street, repeated address keys
eircodestringNoIrish eircode for the site.D02 X285
latnumberNoLatitude for coordinate-based search. Use with lon.53.3498
lonnumberNoLongitude for coordinate-based search. Use with lat.-6.2603
radius_mintegerNoRadius in meters for coordinate search. Must be greater than 0. Default is 5.25
limitintegerNoMaximum records returned. Must be greater than 0. Default is 100.50

#Example Request

curl "https://api.eireplan.ie/ext/v1/precedents/site-history?address=15%20Example%20Street&address=15%20Example%20St%2C%20Dublin%202&eircode=D02%20X285&lat=53.3498&lon=-6.2603&radius_m=25&limit=20" \
  -H "Authorization: Bearer ek_your_api_key_here"

#Response Shape

{ "result": { query_* fields, query_radius_m, used_fallbacks, summary, precedents, source } }

#Response Structure

FieldTypeDescription
result.query_addressstringPrimary normalized address used for lookup, when available.
result.query_addressesarrayNormalized address candidates used in the request.
result.query_eircodestringNormalized eircode used for lookup, when available.
result.query_latnumberEffective latitude used for the query, when available.
result.query_lonnumberEffective longitude used for the query, when available.
result.query_radius_mintegerApplied search radius in meters.
result.used_fallbacksarrayAny fallback strategies used to complete the lookup.
result.summary.total_applicationsintegerTotal matched applications in this result set.
result.summary.decision_countsobjectCounts by normalized decision.
result.summary.type_countsobjectCounts by normalized application type.
result.precedentsarrayMatching precedent records near or matching the site input.
result.sourcestringData source strategy used for the search.

#Example Response

json
{
  "result": {
    "query_address": "15 Example Street",
    "query_addresses": ["15 Example Street", "15 Example St, Dublin 2"],
    "query_eircode": "D02 X285",
    "query_lat": 53.3498,
    "query_lon": -6.2603,
    "query_radius_m": 25,
    "used_fallbacks": ["address_normalization"],
    "summary": {
      "total_applications": 2,
      "decision_counts": {
        "granted": 1,
        "refused": 1
      },
      "type_counts": {
        "permission": 2
      }
    },
    "precedents": [
      {
        "id": "5f8fcb68-2be1-4ce7-8ef4-6a29c2fb4aa8",
        "planning_ref": "DCC-1234-25",
        "address": "15 Example Street, Dublin 2",
        "decision_norm": "granted"
      },
      {
        "id": "f40db59f-91f5-478c-a5ab-5c1b6086f7cd",
        "planning_ref": "DCC-9981-24",
        "address": "18 Example Street, Dublin 2",
        "decision_norm": "refused"
      }
    ],
    "source": "db_bbox"
  }
}

#Where It Fits

Use Site History after Search Precedents when you need neighborhood context around a known site before drilling into one precedent by id.

Knowledge API