TomTom Geofencing API review
A shape-flexible geofencing API with useful alerts, but a published decommission date clouds its future.
Reviewed by iTechGuides Editors · Editorial team · Updated Oct 2026
TomTom Geofencing API gives developers HTTP endpoints to create projects, manage fences, register objects, and check whether locations are inside, outside, or near defined areas. Its range of fence shapes and alert rules suits teams building location-aware applications that need geofencing as an API capability. Configuration is stored in TomTom’s cloud, and the service is available to small, mid-market, and enterprise organizations.
The geospatial feature set goes beyond simple entry and exit checks. Fences can be circles, polygons, corridors, or two-point rectangles; location reports show whether objects are inside or outside, and transition events can be tracked with history. Distance-to-nearest-border calculations add a way to assess how close an object is to crossing a boundary. Rules cover transition, dwell, object-count, and proximity alerts. Notifications can be delivered by webhook or email through the TomTom Notifications API, while the TomTom Location History API is also listed as an integration. This breadth is useful for teams that need multiple fence geometries and event types, rather than a single radius-based check.
The pricing model offers a limited-use Free evaluation with a daily request limit, no credit card requirement, and self-service support through documentation. Pay as you grow removes the daily request limit and uses usage-based pricing, with one-off or recurring payments and online support and documentation. Enterprise plans are custom, with no daily request limit, flexible QPS limits, and tailored support and documentation. Those options provide distinct routes from evaluation to larger deployments, but the lifecycle notice is decisive: TomTom documentation says the API will be decommissioned on January 31, 2027, with no recommended migration path. It is therefore a poor choice for new systems expected to operate beyond that date; teams with a short-term need should weigh the shutdown carefully before adopting it.
TomTom Geofencing API pros and cons
- Where it wins
- Supports circle, polygon, corridor, and two-point rectangle fences.
- Tracks transitions and offers dwell, proximity, and object-count alert rules.
- Cloud configuration with webhook and email notification delivery.
- Where it doesn't
- The API is scheduled for decommissioning on January 31, 2027.
- No recommended migration path is provided in the documentation.
- Access is through HTTP endpoints; no mobile SDK is listed.
TomTom Geofencing API fact sheet, pricing and score →
Advertiser disclosure: iTechGuides is reader-supported. Vendors can pay for top positions in our rankings and for a place on other products' pages, and we may earn a commission when you click some links. Bought places stand at the number bought; this page and our disclosure say so. Paying vendors may get a fuller, more detailed review from our editors, and that review can change their score. How we rank.
Last updated · How we research and update