Org APInationaltrust.org.uk ↗
Search National Trust places by location and retrieve opening times, facilities, and accessibility details via a simple two-endpoint API.
What is the Org API?
The National Trust Places API provides two endpoints for discovering and inspecting heritage properties, gardens, and nature reserves listed on nationaltrust.org.uk. The search_places endpoint returns geo-sorted results within a configurable radius, while get_place_details exposes over 10 structured response fields per property — including per-asset opening hours, facilities with availability flags, and accessibility features — making it straightforward to build location-aware tools on top of the National Trust catalogue.
curl -X GET 'https://api.parse.bot/scraper/92c3cbb6-8ac7-4acf-a4cb-d737aa785309/search_places?limit=5&latitude=51.5072178&location=London&longitude=-0.1275862&miles_radius=50' \ -H 'X-API-Key: $PARSE_API_KEY'
Typed, relational, agent-ready
A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.
- Fully typed · autocompletes
- Objects link to objects
- Typed errors & pagination
Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:
uv add parse-sdk uv run parse init uv run parse add --marketplace nationaltrust-org-uk-api
uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.
"""Walkthrough: National Trust SDK — bounded, re-runnable; every call capped."""
from parse_apis.nationaltrust_org_uk_api import NationalTrust, PlaceNotFound
client = NationalTrust()
# Search for places near London by coordinates
for place in client.place_summaries.search(
location="London", latitude="51.5072178", longitude="-0.1275862", limit=3
):
print(place.title, place.town, place.county)
# Take one result and drill into full details
hit = client.place_summaries.search(
location="London", latitude="51.5072178", longitude="-0.1275862", limit=1
).first()
try:
detail = hit.details()
print(detail.name, detail.address.postcode)
print("Opening note:", detail.opening_times.note)
for fac in detail.facilities[:3]:
print(f" Facility: {fac.name} — available={fac.available}")
for acc in detail.accessibility[:3]:
print(f" Access: {acc.name} — {acc.description}")
except PlaceNotFound as e:
print(f"Place gone: {e.place_path}")
print("exercised: place_summaries.search, PlaceSummary.details")
Search for National Trust places near geographic coordinates. Returns places sorted by distance from the given point within a configurable radius. Each result includes basic info and a website_url_path for use with the get_place_details endpoint. When latitude and longitude are provided, results are proximity-sorted; when only location text is provided, results match by name.
| Param | Type | Description |
|---|---|---|
| limit | integer | Maximum number of places to return. |
| latitude | string | Latitude of the search centre point as a decimal string (e.g. '51.5072178'). |
| location | string | Location name or search text (e.g. 'London', 'Bath'). Used as a query label when coordinates are provided, or as a name-match filter when used alone. |
| longitude | string | Longitude of the search centre point as a decimal string (e.g. '-0.1275862'). |
| miles_radius | integer | Search radius in miles from the centre point. |
{
"type": "object",
"fields": {
"total": "total number of matching places",
"places": "array of place summaries with id, title, description, location, and opening status"
},
"sample": {
"total": 118,
"places": [
{
"id": "139",
"town": "Southwark",
"title": "George Inn",
"county": "London",
"latitude": 51.503799,
"image_url": "https://nt.global.ssl.fastly.net/binaries/content/gallery/website/national/regions/london/places/george-inn/library/exterior-george-inn-london-39951.jpg",
"longitude": -0.08904,
"description": "Last remaining galleried inn in London",
"website_url_path": "/visit/london/george-inn",
"image_description": "Exterior of the George Inn in Southwark, London, showing white wooden galleries"
}
]
}
}About the Org API
Searching for Properties
The search_places endpoint accepts a latitude and longitude pair alongside an optional miles_radius to return National Trust places sorted by proximity. You can also pass a location string as a human-readable label for the search centre. Each result in the places array includes a title, description, current opening status, and a website_url_path that feeds directly into get_place_details. Use the limit parameter to control how many results come back. The total field tells you how many matches exist for the given radius regardless of the limit applied.
Place Details
Passing a place_path (e.g. '/visit/london/ham-house-and-garden') to get_place_details returns a full property record. The address object includes street lines, town, county, country, and postcode. The location object adds latitude, longitude, and a region label. Contact details come back as a contact object with telephone and email.
Opening Times, Facilities, and Accessibility
Opening times are returned as an opening_times object containing a plain-text note and a days map keyed by date, with each date carrying a status and per-asset hour ranges — useful for properties that have multiple separately-timed assets such as gardens, houses, or cafés. The facilities array lists each facility by name, includes a boolean available flag, a description, and a key_facility flag to distinguish headline amenities. The accessibility array gives named features with descriptions. Any active closure or emergency notice appears in the emergency_notice field.
Coverage
The API covers properties listed under the Visit section of nationaltrust.org.uk. Results are limited to England, Wales, and Northern Ireland, which reflects the National Trust's operational territory. Scotland is covered by the separate National Trust for Scotland and is not included.
The Org API is a managed, monitored endpoint for nationaltrust.org.uk — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when nationaltrust.org.uk changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official nationaltrust.org.uk API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Build a 'places near me' map widget using
search_placeswith latitude/longitude and the opening status field. - Generate accessible-venue guides by filtering
accessibilityfeatures fromget_place_detailsresults. - Display today's opening hours for a specific property using the
daysmap insideopening_times. - Show dog-friendly or café-equipped properties by checking the
key_facilityflag in thefacilitiesarray. - Alert users to current closures by surfacing the
emergency_noticefield on a property detail page. - Populate a travel itinerary with structured address and contact data from the
addressandcontactresponse objects. - Index National Trust properties by region using the
regionfield in thelocationobject for faceted browsing.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does the National Trust have an official developer API?+
What does `get_place_details` return for opening times, and how granular is the data?+
opening_times object contains a human-readable note and a days map keyed by calendar date. Each date entry carries a status and asset-level hour ranges, so properties with multiple separately-operated areas (such as a walled garden and a house) each have their own hours listed. The data covers the dates the source site currently publishes, which is typically a rolling window of upcoming dates.Does `search_places` support filtering by facility type, such as returning only dog-friendly properties?+
search_places endpoint returns summary results filtered by proximity and radius; facility filtering is not a supported parameter there. Facility details including the available flag and key_facility flag are only returned per-property by get_place_details. You can fork this API on Parse and revise it to add a facility-filter layer on top of the search results.Does the API cover National Trust for Scotland properties?+
Are historical or past opening times available, or only upcoming dates?+
opening_times data reflects what is currently published on the National Trust site, which is a forward-looking schedule. Past dates are not retained in the response. The days map scope and freshness depend on what the source publishes at the time of the request.