Geofencing API
Draw the zones that matter - a site, a depot, a customer's premises, a restricted area - decide who they apply to and when, and let the platform monitor entry and exit for you.
Overview & Solution
Knowing where a field team is only helps if someone is watching. In practice nobody watches a live map all day, so arrivals go unrecorded and out-of-territory movement is noticed weeks later, if at all.
The Geofencing API turns a zone into a rule. You register a polygon or a radius around a point, attach it to specific employees and a daily time window, and choose whether entry, exit or both should trigger. From then on the platform monitors the GPS stream your devices are already pushing and raises an event whenever a crossing happens.
Key Value Propositions
- Two ways to draw a zone - pass a polygon you drew on a map, or a centre point plus a radius and the circle is generated for you.
- Scoped to people and hours - a zone applies to a named set of employees, and only inside a daily working window, so after-hours movement doesn't generate noise.
- Entry, exit, or both - choose per zone which crossings matter.
- Live monitoring and end-of-day reporting - watch crossings as they happen during the shift, and read the same record back afterwards as the day's attendance and site-visit report.
Industry Use Cases
1. Field Service & Maintenance
- Verified site arrival - a technician crossing into the customer's site records the arrival itself, instead of relying on a phone call or an end-of-day form.
- Time-on-site - entry and exit crossings give you the actual duration of a visit.
2. Logistics & Transport
- Depot and hub monitoring - know when a vehicle reaches or leaves a loading point without anyone watching the screen.
- Restricted-area alerts - flag movement into areas a route should never touch.
3. Distribution & Field Sales
- Territory discipline - assign each zone to the reps who own it, and surface work happening outside the assigned patch.
- Beat verification - confirm the planned outlets were actually entered, not just driven past.
Works with
Geofencing evaluates the GPS your devices already send and applies to the workforce you already manage, so it is usually integrated alongside these:
| API | Role in a geofencing integration |
|---|---|
| Tracking API | Supplies the GPS stream the zones are evaluated against |
| Employee Management API | Defines the employees a zone is assigned to (geofence_vehicle_query selects them by username) |
| Events API | Where crossing events land, alongside duty and visit events |
