Data from the application for agricultural support

Open data API in a single place

Provided by Ministerium für Land- und Ernährungswirtschaft, Umwelt und Verbraucherschutz (MLEUV)

Get early access to Data from the application for agricultural support API!

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

Dataset information

Country of origin
Updated
2026.03.24 00:00
Created
2010.07.13
Available languages
English
Keywords
opendata
Quality scoring

Dataset description

The State of Brandenburg and the EU provide support for rural development. In order to make use of these funds, agricultural holdings must submit annual land-based agricultural support applications. The application data is generated digitally on the basis of the field block cadastre (DFBK). In the field blocks, the farms digitise the landscape features and blows they want to work on. The strokes are assigned attributes such as culture type, land use, bonds (restrictions) and size according to which the funding is calculated. Only one type of culture is assigned to the blows. Possible types of landscape features may include hedges, rows of trees, fieldrains, wetlands. Further explanations are provided in the attached documentation (*.pdf). For the final calculation of the funding, further indicators are needed, such as the size of the total area of the farm, the number of crops, young farmers’ premiums, small farmers’ scheme.
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.

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

Copyright © 2026. Made by Apitalks