Custom JoinData integration development
Appfront builds integrations with JoinData, the independent data platform for farmers and growers. Through JoinData, a farmer decides who may use which data from the farm, such as milk data, milking robot data or animal health data. We connect your application to JoinData, so you retrieve data from farmers who give their consent, and that consent is always respected.
What is a JoinData integration?
JoinData is a cooperative, independent data platform for the agricultural sector. Farmers and growers manage in one place who may use which data from their farm, and for what purpose. This includes, for example, milk recording data, bulk tank milk data, data from the milking robot or milking parlour, sensors, concentrate feed and animal health. JoinData only passes on data with the farmer's consent, and does not use the data itself.
For a software supplier, adviser or supply chain partner, this means that data a farmer wants to share can be retrieved through JoinData, without the farmer having to export files. For this, JoinData has a data catalogue listing the available datasets, along with the API documentation. In practice, an application has to track consents properly and map data from different sources into its own model.
We build custom solutions because applications differ: which data you need, for what purpose, and how your own application is structured. The rules for data consumers and how to connect are set by JoinData; we factor that into the first step. What you use data for follows from the consent the farmer gives.
With consent
Data only from farmers who give consent, with that consent always respected.
Via JoinData
Datasets from the data catalogue, retrieved through the API, with no exports by the farmer.
In your application
Data from different sources in your own model, ready for advice or analysis.
How we build your JoinData integration
We start with your application: which data you need, for what purpose, from which farmers, and how it currently comes in. Then we look in the data catalogue to see which datasets are available and what is needed to connect as a data consumer. The purpose must be clear, because that is what the farmer gives consent for. A clear purpose also makes it easier for farmers to say yes.
Your purpose, data, farmers and current data supply.
Choosing datasets and connecting in line with JoinData's rules.
Tracking consents, retrieving data via the API.
Go-live, monitoring, and maintenance when datasets change.
What a JoinData integration actually does
The components below appear in almost every JoinData integration. Which ones you need depends on your application.
Datasets
Selected from the data catalogue.
Permission
Tracked per farmer and per purpose.
Retrieving
Via the JoinData API.
Conversion
Into your own model.
Withdrawal
Stopping when consent lapses.
Log
Every retrieval recorded.
Who we build a JoinData integration for
The integration is intended for anyone using agricultural data with consent.
Software suppliers
Apps for farmers. The data is the core.
Advisers
Advice based on farm data. Consent matters most.
Chain partners
Dairy and feed. Retrieval is what's needed.
Research
Analysis across many farms. The model is the core.
Technology and integrations
This page is about integrations with JoinData. For the agri-food supply chain, see our page on agri-food software, for arable farming our page on field registration in arable farming, and for crop protection our page on spray registration and crop protection. You can read about our way of working on building software.
If the dairy farm uses Lely Horizon and you want that cow data in your feed calculation or advisor environment, take a look at our Lely Horizon integration.
For submitting data to the KringloopWijzer, see our page on an integration with the KringloopWijzer.
Why Appfront for your JoinData integration?
Data a farmer has to export by hand arrives late and incomplete, and data without consent has no place here. That is what we build on: with consent, via JoinData, and in your own application.
No exports
Data arrives automatically.
Trust
Consent always respected.
Usable
In your own model.
Security and privacy in a JoinData integration
The integration processes farm data that may only be used with the farmers' consent. Access credentials are stored encrypted, data is used only for the agreed purpose, and every retrieval is logged.
The integration runs in a European data centre or in your own environment, with encrypted storage and daily backups.
Frequently asked questions about a JoinData integration
Questions agricultural parties ask before getting started.
A cooperative, independent data platform for farmers and growers. Farmers use it to control who may use which data from their farm. JoinData only passes on data with consent, and does not use it itself.
That is listed in JoinData's data catalogue, for example milk recording data, bulk tank milk data, milking robot data, sensors, feed and animal health. We look at which datasets suit your application in the first step.
In JoinData, the farmer gives your application consent for a specific purpose and for specific data. The integration only retrieves what has been consented to, and stops if the farmer withdraws consent.
In line with the agreements and conditions that JoinData sets for data consumers. We cover these in the first step, together with you and JoinData, so that the integration falls within those agreements from the start.
Yes. Data from different datasets is converted to your own model, so it can be used together in your application or analysis. For example, milk data and feed data can be placed side by side for a recommendation, provided the farmer consents to both.
The integration reports it and records what went wrong. The retrieval is retried or queued for review, so no data goes missing. The log shows, per farmer and per dataset, when data was last retrieved.
For software vendors, advisers, supply chain parties and researchers who want to use data with farmers' consent, and who do not want to handle it through exports or loose files. The more farmers you serve, the more an integration saves compared with manual work per farm.
Farm data in your application, with consent?
Tell us which data you need, for what purpose and from which farmers. We will show you which datasets exist and what the integration with JoinData looks like.