Get Precedent Details

Fetch one precedent record by ID with full detail.

Use this request when you already have a precedent id and need the richer detail record.

#Request

GET /ext/v1/precedents/:id

#Path Parameters

Parameter	Type	Required	Description
`id`	string	Yes	Precedent UUID returned by the search endpoint.

#Query Parameters

Parameter	Type	Required	Description
`geometry`	string	No	How much site geometry to return: `simplified` (default), `full`, or `none`. Any other value returns `400`.

simplified is the right default for mapping — it returns a boundary with reduced vertex detail, which is what you want on a web map. Use full only when you need the boundary at its published precision, and none to skip the geometry lookup entirely when you just want the record.

Site boundaries are fetched live from the national dataset rather than stored, so this lookup can fail. When it does the request still succeeds: polygon is omitted and has_polygon comes back false. Treat a missing polygon as "no boundary available right now", not as "this site has no boundary".

#Example Request

curl "https://api.eireplan.ie/ext/v1/precedents/5f8fcb68-2be1-4ce7-8ef4-6a29c2fb4aa8" \
  -H "Authorization: Bearer ek_your_api_key_here"

#Response Structure

Field	Type	Description
`precedent.id`	string (UUID)	Unique precedent identifier.
`precedent.planning_ref`	string	Official planning reference.
`precedent.address`	string	Site address.
`precedent.description`	string	Application description.
`precedent.applicant`	string	Applicant or developer name.
`precedent.local_authority`	string	Responsible authority.
`precedent.decision_norm`	string	Normalized decision value.
`precedent.received_date`	string	Received date.
`precedent.decision_date`	string	Final decision date.
`precedent.official_record_url`	string	Link to the official planning record.
`precedent.official_docs_url`	string	Link to official planning documents.
`precedent.has_polygon`	boolean	Whether site boundary geometry was available for this request.
`precedent.point`	object	GeoJSON `Point` geometry for the site location. This is the geocoded application address, not a surveyed position.
`precedent.polygon`	object	GeoJSON `Polygon` or `MultiPolygon` geometry for the site boundary. Omitted when `has_polygon` is `false` or `geometry=none` was requested.

#Example Response

json

{
  "precedent": {
    "id": "5f8fcb68-2be1-4ce7-8ef4-6a29c2fb4aa8",
    "planning_ref": "DCC-1234-25",
    "address": "15 Example Street, Dublin 2",
    "description": "Mixed-use development with 42 apartments",
    "applicant": "Example Developments Ltd",
    "local_authority": "Dublin City Council",
    "decision_norm": "granted",
    "received_date": "2025-03-12",
    "decision_date": "2025-08-07",
    "official_record_url": "https://planning.localauthority.ie/records/DCC-1234-25",
    "official_docs_url": "https://planning.localauthority.ie/docs/DCC-1234-25",
    "has_polygon": true,
    "point": {
      "type": "Point",
      "coordinates": [-6.2603, 53.3498]
    }
  }
}

#Where It Fits

Start with Search Precedents if you do not already have the precedent identifier.

To plot a set of results on a map, see the worked example in Site History by Boundary — the site-history responses carry no coordinates, so geometry comes from this request.