Skip to content
Flora Carbon AIFloraTraceSample data

Sync & devices

How field data arrives from the FloraTrace mobile app: the phones in the field, every upload they made, and the endpoint they talk to.

API contract

Data source

Where the console reads trees, measurements and photos from.

Demo dataSeeded · active
A fictional sample: 3 sites, 10 plots, 600 trees, 4 rounds. People, places and organisations in it are made up.
Your projectsSign-in

Sign in with a FloraTrace account to see the projects you are a member of: overview, map, registry, analytics and photos. QA, ledger, reports and sync are only in this demo until the app records what they need.

Go to your data

How sync works

From a phone under a sal tree to a tamper-evident record.

API contract

  1. FloraTrace app

    Offline-first queue. Each record gets a client UUID and each photo a SHA-256 at capture.

  2. POST /api/syncbatch_id

    Idempotent by client UUID: retries on 2G never double-insert.

  3. Validationzod

    Types, ranges, references and clock skew. GPS > 10 m and height drops become warnings.

  4. QA queue

    Records land as submitted; reviewers approve or reject with an audit trail.

  5. Merkle anchoring

    Approved records per site and round are hashed into a root and anchored.

Field devices

Phones running the FloraTrace app

Sync activity

Every upload from the field, newest first.

Try the contract

Runs the proposed sync contract in this browser tab, with nothing sent anywhere: one new tree, three measurements and a photo manifest. Send it twice to see idempotency.

The response appears here: accepted counts, duplicates, warnings, and the SHA-256 check on the photo upload.