From test key to attestation in three steps.
- 1
Get a test key
Create a test key in the FaWCOS workspace under Settings, API access. It starts with FWS_test_ and is shown once.
- 2
Request consent
Name the farmer, the purpose and the data scope. The answer is the same whether or not the farmer is registered.
- 3
Fetch the attestation
When the farmer consents, you receive a signed attestation with only the facts they agreed to share.
One host. The key decides the environment.
A test key only ever returns synthetic farmers. A live key only returns real farmers who consented. The two cannot be mixed.
| Key prefix | Environment | Data |
|---|---|---|
FWS_test_ | Sandbox | Synthetic farmers and consents only |
FWS_live_ | Live | Real attestations under real consents |
Keys are shown once, stored hashed, and revoked immediately when you ask. Test keys are self-serve. Live keys are issued after a manual review by the FaWCOS team.
Going live is a review, not a form.
The FaWCOS team reviews every live key request. You will be asked for:
- Your registered business identity
- A named responsible officer
- The purposes you will request consent for
- A signed data-sharing agreement
You can use test keys at any time while the review is under way. Requests for purposes outside the list you submit are refused.
Documentation
Open the docs- QuickstartFrom a test key to your first attestation.
- AuthenticationTest and live keys, rotation and going live.
- EnvironmentsSandbox and live, and sandbox test values.
- ConsentHow a farmer’s consent becomes an attestation.
- ErrorsError codes and what to do about them.
- Rate limitsPer-minute and daily limits per key.
The documentation is a draft until the endpoints are live. Anything not yet built is marked Draft there.
Want to build on FaWCOS first?
Tell us what you want to use verified, consented farm data for. We will reach out when sandbox access opens.