Introduction
One consistent surface for locations, time, and people.
What you get
The GeoDynamics API gives you programmatic access to the same data you see in IntelliTracer: GPS positions, clockings, day programs, workplaces, vehicles, and people. JSON in, JSON out. Authenticated per identity. Read-only in the current version.
One host: https://api.geodynamics.dev. It runs against the same
backend as the existing IntelliTracer application.
Concepts
The API revolves around a handful of primitives. Every object carries a
stable Id you use to link resources. Other fields (names,
codes) can be edited by the customer, so always link on Id.
- Company
- The tenant. All data in the API is scoped to a single company. Your credentials map you to exactly one company.
- User
- A person inside the company. Employee, foreman, manager. Has clockings, day programs, and optionally a linked badge.
- Clocking
- A single clock-in or clock-out event at a point in time, with optional workplace, vehicle, or project. Sourced from a time clock, a mobile app, or an RFID reader.
- Day program
- The expected work schedule for a user on a given day: start time, stop time, breaks. The reference that clockings are compared against.
- Workplace
- A physical site where work happens: a construction site, an office, a workshop. Has an address, a code, and can be linked to one or more POIs.
- POI
- Point of Interest. A geographic zone with coordinates and a radius. When a vehicle or badge enters a POI, that generates events.
- Vehicle
- A vehicle equipped with a tracking device. Has a unique code, a type, and a last known position. Tracking reports give the full route history.
- Tracking report
- The GPS history of a vehicle or resource over a time range. A series of position fixes with timestamp, speed, and geometric sequence.
- RFID tag
- A physical tag (card, sticker, beacon) that identifies a resource (vehicle, equipment, person) at a reader. Produces access logs and presence data.
- Badge
- An identification card linked to a person. Used for clockings, access control, and Check-In-At-Work declarations.
Next steps
- Quickstart for your first API call in four steps.
- Authentication for Basic Auth and OAuth 2.1 + PKCE.
- REST API reference for every endpoint, parameter, and response shape.
- Errors & retries for HTTP status codes and backoff patterns.
- Rate limits for request budgets and throttle responses.