Developers
Build on Field. Every command is signed and checked.
Your tools can file, follow and act on reports through Field’s API, webhooks and SDKs. Underneath, every device speaks one signed protocol, so nothing reaches a terminal that the terminal has not verified.
What you can build
Your tools, wired into the loop.
- Customer API
- Read your fleet, its reports and their diagnoses, and ask for a capture or a fix. Every request goes through your policy and your approvers, as it would from the portal.
- Webhooks and API keys Rolling out
- Your tools hear when a report is filed, a diagnosis is ready, an approval is waiting and a fix is verified. Keys are created, scoped and revoked by your own administrators.
- App SDKs On request
- Android, React Native and iOS SDKs hand your own app’s errors and context to Field, with the same redaction on the device. Ask us for early access.
- Service desks Rolling out
- ServiceNow and Zendesk, both ways: reports open as incidents or tickets with a summary and a link back.
The API reference and webhook details are in your portal’s documentation after sign-in. Integrations
The protocol
What the protocol guarantees.
- Signed end to end
- Every request a device makes and every command it receives is signed, so a proxy in the middle cannot forge or alter one.
- Checked on the device
- A terminal runs only named fixes from the signed library, and checks each command itself before it acts.
- Risky means two keys
- Commands that interrupt or wipe a device need a second approval, signed by a service kept apart from the one that sends commands.
- One contract, every agent
- Android, Windows, macOS, Linux and the browser all pass the same shared tests before anything ships.
Building on Field?
Talk to the engineers who wrote the protocol. We will walk your team through the agents, the APIs and the test vectors.
Or write to hello@tickflow.co