Radar Integration

Location infrastructure platform providing geofencing, geocoding, routing, and device tracking APIs for mobile and web applications. Connect Radar events to the tools your engineering teams already use. Start with Watch Beacons, then follow with Get Beacon or Get Geofence to automate the next step.

Explore Documentation

3-day trialCancel anytimeUp to 10 minutes quick set up

GDPR
Data Encryption
2FA
Local Data Region

Supported triggers and actions for Radar integration

Triggers can detect changes in Radar and run actions that can create, search or modify data inside Radar automatically [3] — exactly how you set them.

Watch BeaconsTriggers when a user enters or exits the range of a monitored Bluetooth beacon.
Watch GeofencesTriggers when a user enters or exits a geofence boundary.
Watch TripsTriggers when a trip status changes, such as when a user approaches or arrives at their destination.
Get BeaconRetrieves a single Bluetooth beacon by its ID.
Get GeofenceRetrieves a single geofence by its ID.
Get Places SettingRetrieves the current Places configuration settings for the project.
Get TripRetrieves a single trip by its external ID.
Get UserRetrieves a single Radar user by their user ID or device ID.
Get Users in GeofenceReturns all users currently located inside a specified geofence.
List BeaconsReturns a paginated list of all Bluetooth beacons in the project.
List GeofencesReturns a paginated list of all geofences in the project.
List TripsReturns a paginated list of trips, optionally filtered by status or external ID.
List UsersReturns a paginated list of all users tracked in the project.
Search AutocompleteReturns address and place suggestions based on a partial search query for autocomplete UIs.
Search GeofencesSearches for geofences near a given location within a specified radius.
Search PlacesSearches for points of interest and places near a given location by name or category.
Search UsersSearches for users by user ID, device ID, or custom metadata fields.
Watch UsersTriggers when a user's location or context changes, such as entering a geofence or changing country.
Create BeaconCreates a new Bluetooth beacon in Radar and associates it with a geofence or place.
Create TripCreates a new trip to track a user's journey from an origin to a destination in real time.
Delete BeaconPermanently deletes a Bluetooth beacon by its ID.
Delete GeofencePermanently deletes a geofence by its ID.
Delete TripPermanently deletes a trip by its external ID.
Delete UserPermanently deletes a Radar user and all associated location data.
Geocode ForwardConverts a text address into geographic coordinates (latitude and longitude).
Geocode IPReturns the estimated geographic location for a given IP address.
Geocode ReverseConverts geographic coordinates (latitude and longitude) into a human-readable address.
Log ConversionRecords a conversion event for a user, used for attribution and funnel analytics.
Make an API CallExecutes an arbitrary authenticated HTTP request to the Radar API.
Refresh UsersTriggers a server-side refresh of location and context data for specified users.
Route DirectionsReturns turn-by-turn driving, cycling, or walking directions between an origin and destination.
Route DistanceCalculates the travel distance and estimated time between an origin and destination.
Route MatchSnaps a sequence of GPS coordinates to the road network and returns the matched route.
Route MatrixComputes travel distances and durations between multiple origins and destinations in a single request.
Route OptimizeFinds the most efficient visiting order for a set of stops given an origin and destination.
TrackRecords a location update for a user and evaluates geofence entry/exit events.
Update Places SettingsUpdates the Places data provider and configuration for the project.
Update TripUpdates the status or destination details of an existing trip.
Upsert BeaconCreates a new Bluetooth beacon or updates an existing one matched by its external ID.
Upsert GeofenceCreates a new geofence or updates an existing one matched by its external ID.
Validate AddressValidates and standardizes a postal address, returning corrected components and confidence scores.

How to integrate Radar in automation workflow?

3 simple steps to make your Radar connected with other apps in automation workflows on WEXTL. Up to 10 minutes integration set up.

STEP 1

Select Radar in workflow

Pick Radar app in the workflow builder [4] - just one click to select the app.

STEP 2

Connect Radar

When prompted, authorize access to Radar in WEXTL once. Radar credentials are encrypted and never shared with WEXTL. Authorization will be reused in any future API calls [3].

WEXTL wants to integrate with your Radar account. Approve?

STEP 3

Build a workflow

Build your workflow with Radar yourself or with WEXTL® AI Builder. Connect Radar to any available integrations [5], or use HTTP node to go beyond them.

Radar

How Radar connects and integrates with WEXTL

Save and approve your credentials once — WEXTL® stores authorization information encrypted and reuses the authentication whenever Radar app is called in workflows. That allows your developer tools automations to run without your attention, per defined schedule [7]. Explore documentation [6] for a detailed list of fields that Radar supports.

Full Radar API documentation

The following table illustrates what fields Radar integration require during authorization flow inside our workflow builder [4].

Demonstration of Radar connection step inside WEXTL Workflow Builder [4].

Field	Type	Help
Secret API KeyRequired	password	Your secret API key from the Settings page (Settings > API Keys). Use your Test Secret key for testing and your Live Secret key for production. Required for all server-side endpoints.

Connect Radar to popular apps on WEXTL

Enter a name of the other app you want to sync with Radar below. Click on selected app to explore integration options with Radar. If the app you search for is not available in WEXTL yet, you can use HTTP node [10] instead to integrate it directly.

Example automation with Radar integration

Select Watch Geofences trigger from Radar - this will be a starting point in your automation. Whenever event happens in Radar, workflow will start [7] from Watch Geofences node.

Search for Delete Geofence, connect it as the next step of integration sequence. You can use filters between Watch Geofences and Delete Geofence, so only important data pass from Watch Geofences to the next step. WEXTL gives you full control over the process of Radar automation. All parts of workflow are visible on the canvas [4].

Radar on WEXTL has 41 modules for creating developer tools automations. Explore Radar documentation for more.

Video slide demonstrates how Watch Geofences and Delete Geofence nodes are used in Radar workflow.

Video slide demonstrates how Watch Geofences and Delete Geofence [6] nodes are used in Radar workflow.

Frequently asked questions

Common questions about automating Radar in your workflows.

Radar has 3 triggers, including "Watch Beacons", "Watch Geofences", and "Watch Trips". Triggers are start points of the workflow, and automations may start from them.

Integration has 38 actions, including "Get Beacon", "Get Geofence", and "Get Places Setting", and more. Refer to our Radar Documentation for detailed inputs and outputs.

No. Most automations are built visually on the canvas by picking triggers, actions, and mapping fields. You can add custom JavaScript with Functions when advanced logic is needed — but our customers do that in rare cases [4].

Yes. Connections are authenticated per account, credentials are encrypted at rest, and you can enforce approvals and team-level access controls on any automation.

The Radar integration on WEXTL runs directly on its vendor public API — every field name, authentication method, and rate limit is controlled by Radar official API and covered in documentation [3]. WEXTL handles the request signing and pagination for you.

Absolutely. Where Radar provides native webhooks, you can use instant triggers to eliminate polling delay. For custom webhooks, WEXTL offers Custom Webhook node, so you can start automation whenever Radar or any other service sends event to webhook URL.

WEXTL is an AI-first visual canvas. The platform allows you to describe automation in plain text — and AI will wire nodes for Radar inside the workflow builder [4]. You can also use built-in workflow nodes (AI Agent, Human in the Loop, Condition, Aggregate Results) in pair with Radar modules to craft complex integration flows with branches, filtering, and conditional logic. There are absolutely no limits of what you can build.

References

List of sources used to gather information about the Radar integration.

Radar integration source code, module specs and credentials implementation.
Internal Radar integration documentation, structured input and output parameters, scopes, and authentication methods.
Official Radar vendor API documentation — used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
WEXTL® Visual Workflow Builder, anonymized data from our technical support team.
WEXTL® Apps Library
WEXTL® Radar App Documentation
WEXTL® Workflow Scheduler
WEXTL® HTTP node documentation

Radar Integration

Supported triggers and actions for Radar integration