Rezolve Point SDK

Android API Reference

The Rezolve Point SDK brings high-accuracy, always-on location awareness and low-energy geofencing to your Android app.

This site is the API reference for the Android library (v18.0.0) — the packages, classes, and methods you call directly. If you're integrating for the first time, start with the Quick Start guide, which walks through project setup, Gradle, and location permissions. Use this reference to look up specifics once you know what you're building.

New in v18.0.0 — a native Push Notifications module (au.com.bluedot:pushnotifications): register the device and handle Rezolve push notifications directly through the SDK. Designed to coexist with your app's existing push setup — the module uses isRezolvePushNotification() to filter only Rezolve messages, so any notifications you already deliver through other providers flow through unaffected.

Requirements & compatibility

• Android 10 (API 29) or higher.

• Google Play Services (Location).

• For push: a Firebase project with FCM enabled, and firebase-messaging:25.x.

• As of v18.0.0 the SDK is compiled with the Java 21 toolchain — set your build accordingly when upgrading.

• Moshi is supported up to 1.9.3.

• For full setup, see the Quick Start guide.

Where to go next

• New here → Quick Start

• Geofencing — zone entry & exit → Geo-triggering

• Continuous foreground tracking → Tempo

• Remote push notifications → Push Notifications overview (Android deep dive: Push Notifications — Android)

• Permissions & the foreground-service notification → Location Permission & Notifications Best Practices

• Upgrading from an earlier version → Migration Guides (replace with the latest migration guide URL if a newer one exists)

Points of interest

These are the core classes for building an app that responds to the Actions you define in the Canvas web interface.

ServiceManager

The high-level entry point. Initialize it once with your Rezolve project credentials (from Canvas) to start a session with the Point back-end. Every other service requires ServiceManager to be initialized first.

GeoTriggeringService

Starts and stops geo-triggering, which computes Zone entry and exit events. Once started, your Zones download automatically and their Canvas-defined Actions fire without further code. Events are delivered as GeoTriggerEvent (renamed from ZoneEntryEvent in v16).

TempoService

Starts and stops Tempo, for continuous foreground location tracking over a defined period — e.g. live order or ETA tracking.

Push Notifications (module: au.com.bluedot:pushnotifications)

New in v18.0.0. Optional module for delivering Rezolve push notifications triggered by zone entry. Bridge your FirebaseMessagingService token and message events into the SDK, and extend PushNotificationsEventReceiver if your app needs custom behaviour on receipt or tap. The module uses isRezolvePushNotification() to filter only Rezolve messages, so it coexists with any other push setup in your app. For setup — FCM credentials in Canvas, the POST_NOTIFICATIONS runtime permission (Android 13+), and notification channels — see the Push Notifications overview and the Android implementation guide.

Two different "notifications." The foreground-service notification is the persistent status-bar notification that keeps Geo-triggering or Tempo alive in the background (see Location Permission & Notifications Best Practices). The Push Notifications module is for remote messages delivered via FCM. They are unrelated — don't configure one expecting the behavior of the other.