Legacy Countryside Stewardship Scheme Agreements (England) - closed scheme

Open data API in a single place

Provided by Natural England

Get early access to Legacy Countryside Stewardship Scheme Agreements (England) - closed scheme API!

Let us know and we will figure it out for you.

Dataset information

Catalog
Natural England catalog
Country of origin
United Kingdom
Updated
Created
Available languages
English
Keywords
Area management/restriction/regulation zones and r, environment
Datasource
Official portal for European data link
Quality scoring

Dataset description

Former Countryside Stewardship Scheme live agreements holding boundaries data as at scheme closure in 2014. This Natural England dataset is static and does not include up to date information relating to the Countryside Stewardship Scheme. This scheme is now closed to new applicants. The Countryside Stewardship Scheme was originally an agri-environment scheme run by the United Kingdom Government set up in 1991. In its original form it expired in 2014 and has now fully expired. It was relaunched for the Rural Development Programme England (RDPE) 2014-2020 with £3.1bn of government subsidy for agriculture and forestry, as the Countryside Stewardship Scheme 2016. Attribution statement: © Natural England copyright. Contains Ordnance Survey data © Crown copyright and database right [year].
European data infrastructure with broad catalog discovery, free evaluation access and production-grade API options.
190K+
indexed dataset pages
32
countries and EU institutions
2019
API-first since
Free API quota
for evaluation and prototypes
SLA
history and push on production APIs
FAQ

Questions before production use

Practical answers on evaluation, licensing, freshness, versioning and support.

api.store is built and operated by Apitalks s.r.o. Company details and a direct contact path are linked in the footer for vendor checks and procurement review.
Yes. Selected APIs include a free API quota, so your team can validate coverage, freshness, response shape and workflow fit before asking for a production plan.
Often yes, but usage rights depend on the source license and dataset. We surface source, license and update metadata where available, and can help review terms before a production integration.
Maintained APIs include update metadata where available. For production integrations, we can add history, monitoring and push updates so changes are easier to detect and act on.
Production APIs can add SLA, stable identifiers, versioning support, history, push updates and direct support around the data your product or AI workflow depends on.

Didn't find the API you need?

Let us know and we will figure it out for you.

api.storeBuilt by Apitalks

European data discovery with free evaluation access and production-grade API options.

About api.storePrivacyTerms of Service
Copyright © 2026. Made by Apitalks