Google Android Geofencing API
developers.google.com
- Free plan
- Android
6.4 Club score Visit developers.google.com
What the maker publishes
- Availability constraint
- Geofencing may be unavailable when device location or Location Accuracy is off. source
- Cleanup behavior
- Registered geofences are automatically removed when the app is reset or its PendingIntent is canceled. source
- Configurable behavior
- Geofences can be configured with an expiration duration, dwell delay, notification responsiveness, request ID, and transition types. source
- Deprecated predecessor
- Google identifies GeofencingClient as the replacement for the deprecated GeofencingApi field. source
- Geofence transitions
- Geofences can report enter, exit, and dwell transitions. source
- Integration
- Apps obtain the GeofencingClient through LocationServices and submit a GeofencingRequest with a PendingIntent. source
- Intent requirement
- On Android S and later, the PendingIntent passed to addGeofences must be mutable. source
- PendingIntent limit
- The documented status codes include an error for providing more than five different PendingIntents. source
- Permissions
- Most geofencing APIs require fine-location and background-location permissions. source
- Purpose
- The Geofencing API lets an app define perimeters around areas of interest and receive a notification when a device crosses one. source
- Region shape
- A geofence represents a circular area specified by latitude, longitude, and radius. source
- Registration limit
- The documented status codes include an error for registering more than 100 geofences. source
- Responsiveness
- Notification responsiveness is best-effort; a small requested delay does not guarantee immediate notification. source
Checked against the maker's pages on 14 Nov 2026.