Docs / Developer / API Access

Developer & API

API Access

Agribantu is a closed, invitation-only network — that's true of API access too. Here's how programmatic access actually works, and how to request it.

Audience: integration partners & technical teams

Not a public, self-serve API

Most of what makes Agribantu useful — verified locations, permitted movements, scoped access grants — only holds up because every party on the other end of a request is a known, accountable member of the network. A public sign-up-and-go API would undercut that in the same way an open network membership would: it's not a limitation we intend to lift as the product matures, it's the same design decision as the rest of the network, applied to code instead of people.

That means there's no public API key you can generate from a dashboard today. Programmatic access is issued the same way network membership is — deliberately, to a known party, for a specific purpose.

How access is granted

  • Role-based. An integration credential carries the same kind of scoped, named permissions a human grant does — it can read or write exactly what it was issued for, and nothing else.
  • Audited. Every request made through an integration credential is logged against the organisation and jurisdiction it belongs to, the same audit trail every other authority- or organisation-facing action goes through.
  • Revocable. Access can be withdrawn immediately and permanently, the same way a human external-access grant can — see the External Access Portal guide for the equivalent human-facing workflow this mirrors.

What integration typically looks like

Approved integration partners are most often one of the following:

  • A regulatory or industry body pulling compliance data — for example, an ICAR/ADE-format export consumer (see ICAR/ADE Data Exchange).
  • A device or fleet-tracking provider feeding live position data in.
  • An existing farm recordkeeping system reconciling records with Agribantu rather than replacing itself (see RMIS Traceability Alignment for how Agribantu represents data provenance across systems).

Each of these gets a scoped integration credential and, where useful, a working session with our team to confirm exactly which endpoints and data shapes the integration needs — rather than a generic all-purpose key handed out unread.

Requesting access

If you're a regulator, industry body, device provider, or existing recordkeeping system that needs to integrate with Agribantu, tell us who you are and what you're trying to connect using the network notification form — we review integration requests the same way we review membership requests.

Get in touch