For integrators & vendors
Build on the open API, on equal terms
Integrating with LITS is a thin adapter, not a rebuild. You keep your product and your database, and add a client that submits events to the registry and reads reference data back — with your own key, on a published contract, no private agreement.
How you connect
- Your own per-operator key — every submission is attributed to you and audited.
- Submit and read — register animals, lodge movements, record vaccinations, request certificates, and pull veterinary-zone reference data.
- Reliable writes — an
Idempotency-Keyon every write, retries with backoff and a circuit breaker, and an acknowledgement id on every response.
The endpoints you use
| Method & path | Purpose |
|---|---|
POST /v1/animals | Register or identify an animal |
POST /v1/movements | Lodge a movement permit / consignment |
POST /v1/certificates | Request a registry-signed certificate |
GET /v1/zones | Pull veterinary / FMD zone reference data |
GET /v1/verify/{token} | Public certificate verification (no auth) |
The full contract is on the standard; the step-by-step is in the vendor integration guide.
Conformance & accreditation
- Build in the sandbox against the published OpenAPI contract with test keys.
- Run in dry-run — record what you would send, with no live calls, to verify mapping and volumes.
- Pass conformance — a public suite checks your integration against the contract.
- Go live — receive a production per-operator key and the right to display the conformance badge.
Equal footing, no lock-in
- The same terms for everyone — FuroTrack is the reference client, not a privileged one.
- Versioned and additive — path-versioned (
/v1); additive changes never break you, breaking changes ship under a new version. - A public changelog you can follow.
Certificates are requested by clients and signed by the registry. Your app prints or embeds from the signed payload — it never mints a national certificate itself.