This is the documentation for the Cordova plugin. Before integrating, read the native SDK documentation to familiarize yourself with the platform.
See the source on GitHub here. Or, see the @radarlabs/cordova-plugin-radar package on npm here.
Install
Install the Cordova plugin:
Before writing any JavaScript, you must integrate the Radar SDK with your iOS and Android apps as described in the iOS SDK documentation and Android SDK documentation.
On iOS, you must add location usage descriptions and background modes to your Info.plist. Initialize the SDK in application:didFinishLaunchingWithOptions: in AppDelegate.m, passing in your Radar publishable API key:
On Android, you must add the Google Play Services library to your project, then add the SDK to your project, preferably using Gradle. Finally, initialize the SDK in onCreate() in MainActivity.java, passing in your Radar publishable API key:
Integrate
Initialize
When your app starts, initialize the SDK with your publishable key.
Use your Test Publishable key for testing and non-production environments. Use your Live Publishable key for production environments.
Note that you should always use your publishable API keys, which are restricted in scope, in the SDK. Do not use your secret API keys, which are unrestricted in scope, in any client-side code.
Identify user
To identify the user when logged in, call:
where userId is a stable unique ID for the user.
To set an optional dictionary of custom metadata for the user, call:
where metadata is a JSON object with up to 16 keys and values of type string, boolean, or number.
Finally, to set an optional description for the user, displayed in the dashboard, call:
where description is a string.
You only need to call these functions once, as these settings will be persisted across app sessions.
Learn about platform-specific implementations of these functions in the iOS SDK documentation and Android SDK documentation.
Request permissions
Before tracking the user’s location, the user must have granted location permissions for the app.
To determine the whether user has granted location permissions for the app, call:
status will be a string, one of:
GRANTED_BACKGROUND
GRANTED_FOREGROUND
DENIED
UNKNOWN
To request location permissions for the app, call:
where background is a boolean indicating whether to request background location permissions or foreground location permissions.
Learn about platform-specific permissions in the iOS SDK documentation and Android SDK documentation.
Foreground tracking
Once you have initialized the SDK and the user has granted permissions, you can track the user’s location.
To track the user’s location in the foreground, call:
status will be a string, one of:
SUCCESS: success
ERROR_PUBLISHABLE_KEY: SDK not initialized
ERROR_PERMISSIONS: location permissions not granted
ERROR_LOCATION: location services error or timeout (10 seconds)
ERROR_NETWORK: network error or timeout (10 seconds)
ERROR_BAD_REQUEST: bad request (missing or invalid params)
ERROR_UNAUTHORIZED: unauthorized (invalid API key)
ERROR_PAYMENT_REQUIRED: payment required (organization disabled or usage exceeded)
ERROR_FORBIDDEN: forbidden (insufficient permissions or no beta access)
ERROR_NOT_FOUND: not found
ERROR_RATE_LIMIT: too many requests (rate limit exceeded)
ERROR_SERVER: internal server error
ERROR_UNKNOWN: unknown error
Learn about platform-specific implementations of this function in the iOS SDK documentation and Android SDK documentation.
Background tracking
Once you have initialized the SDK and the user has granted permissions, you can start tracking the user’s location in the background.
For background tracking, the SDK supports custom tracking options as well as three presets:
EFFICIENT: A low frequency of location updates and lowest battery usage. On Android, avoids Android vitals bad behavior thresholds.
RESPONSIVE: A medium frequency of location updates and low battery usage. Suitable for most consumer use cases.
CONTINUOUS: A high frequency of location updates and higher battery usage. Suitable for on-demand use cases (e.g., delivery tracking) and some consumer use cases (e.g., order ahead, “mall mode”).
Learn about platform-specific implementations of these presets in the iOS SDK documentation and Android SDK documentation.
To start tracking the user’s location in the background, call one of:
You only need to call these methods once, as these settings will be persisted across app sessions.
Though we recommend using presets for most use cases, you can customize the tracking options. See the tracking options reference.
To determine whether tracking has been started, call:
To stop tracking the user’s location in the background (e.g., when the user logs out), call:
Learn about platform-specific implementations of these functions in the iOS SDK documentation and Android SDK documentation.
To listen for events, location updates, and errors, you can add event listeners:
Listeners should be set only once and before tracking begins.
Add event listeners outside of your view lifecycle if you want them to work when the app is in the background.
You can also remove event listeners:
Trip tracking
On iOS and Android, to start a trip to a destination, call:
Update information about the trip. Status can be set to ‘unknown’ to leave the status unchanged as it will update via location tracking.
Later, to complete the trip and stop tracking, call:
Or, to cancel the trip and stop tracking, call:
Learn more about trip tracking.
Manual tracking
You can manually update the user’s location by calling:
Learn about platform-specific implementation of this function in the iOS SDK documentation and Android SDK documentation.
Other APIs
The Cordova plugin also exposes APIs for anonymous context, geocoding, search, and distance.
Get location
Get a single location update without sending it to the server:
Context
With the context API, get context for a location without sending device or user identifiers to the server:
Geocoding
With the forward geocoding API, geocode an address, converting address to coordinates:
With the reverse geocoding API, reverse geocode a location, converting coordinates to address:
With the IP geocoding API, geocode the device’s current IP address, converting IP address to city, state, and country:
Search
With the autocomplete API, autocomplete partial addresses and place names, sorted by relevance:
With the geofence search API, search for geofences near a location, sorted by distance:
With the places search API, search for places near a location, sorted by distance:
Distance
With the distance API, calculate the travel distance and duration from an origin to a destination:
Matrix
With the matrix API, calculate the travel distance and duration between multiple origins and destinations for up to 25 routes:
Support
Have questions? We’re here to help! Contact us at radar.com/support.