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 company data, 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 permission for it, and so that permission is always respected.
What is a JoinData integration?
JoinData is a cooperative and 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, milking robot or milking parlour data, sensors, concentrate feed and animal health. JoinData only shares data with the farmer's consent, and does not use the data itself.
For a software provider, adviser or supply chain partner, this means that data a farmer wishes to share can be retrieved via JoinData, without the farmer having to export files. JoinData provides a data catalogue listing the available datasets, along with API documentation. In practice, an application must track consents carefully and bring 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 terms that apply to recipients and how connecting works are set by JoinData, and we take those into account from the first step. What you use the 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 via the API, without 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 arrives. Then we look in the data catalogue to see which datasets are available and what is required to connect as a recipient. The purpose must be clear, as this is what the farmer consents to. A clear purpose also makes it easier for farmers to say yes.
Your purpose, data, farmers and current data supply.
Choose datasets and connect in line with JoinData's terms.
Track consents and retrieve data via the API.
Go-live, monitoring, and maintenance when datasets change.
What a JoinData integration does in practice
The components below feature in almost every JoinData integration. Which you need depends on your application.
Datasets
Selected from the data catalogue.
Consent
Tracked per farmer and per purpose.
Retrieving
Via the JoinData API.
Conversion
Into your own model.
Withdrawal
Stops when consent lapses.
Audit log
Every retrieval logged.
Who we build JoinData integrations for
The integration is intended for those who use agricultural data with consent.
Software suppliers
Apps for farmers. The data is at the heart of it.
Advisers
Advice on farm data. Consent matters most.
Chain partners
Dairy and feed. Retrieval is what is needed.
Research
Analysis across many farms. The model is central.
Technology and integrations
This page is about integrations with JoinData. For the agri and food 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 how we work at custom software development.
For supplying data to the KringloopWijzer, see our page on an integration with the KringloopWijzer.
Why choose Appfront for your JoinData integration?
Data that a farmer has to export by hand arrives late and incomplete, and data without consent should not be there at all. We build on that principle: with consent, via JoinData, and within your own application.
No manual exports
Data arrives automatically.
Trust
Consent is always respected.
Usable
In your own data model.
Security and privacy in a JoinData integration
The integration processes farm business data, which may only be used with the farmer's 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 that agricultural organisations ask before getting started.
A cooperative, independent data platform for farmers and growers. Farmers manage who may use which data from their business. JoinData shares data only with consent, and does not use it itself.
This is listed in the JoinData data catalogue, for example milk control data, bulk tank milk data, milking robot data, sensor data, feed and animal health data. In the first step, we look at which datasets suit your application.
The farmer grants your application consent in JoinData, for a specific purpose and for specific data. The integration retrieves only what consent covers, and stops if the farmer withdraws it.
In line with the agreements and terms that JoinData sets for data consumers. We take these into account in the first step, together with you and with JoinData, so that the integration complies with them from the outset.
Yes. Data from different datasets is mapped to your own model, so it can be used together in your application or analysis. For example, milk data and feed data can be viewed side by side to inform advice, provided the farmer has consented to both.
The integration reports the failure and records what went wrong. The retrieval is retried or queued for review, so no data goes missing. The log shows, per farm and per dataset, when data was last retrieved.
For software suppliers, advisers, supply chain partners and researchers who want to use data with farmers' consent, and who would rather not handle this 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 farms. We will show you which datasets are available and what the integration with JoinData would look like.