Skip to main content
A consent names four things: who receives the data (your organisation), why (a purpose), what (a scope from a fixed list) and until when (an expiry).

​
Allowed scope items

levels, tier, verified_area, crops, seasons, open_flags, name, phone, nin_last4, parcel_geometry. There is no blanket consent. You receive only the items the farmer agreed to.

​
Lifecycle

The consent and attestation endpoints are released next (see the Changelog). This is how they work.
  1. You request consent for a purpose and scope.
  2. The farmer confirms with a one-time code or their PIN, in their language.
  3. FaWCOS issues a signed attestation addressed to your organisation.
  4. If the farmer revokes consent, or it expires, the attestation is revoked. Check status before relying on one.
Every read of an attestation is logged against the farmer’s consent.