Radar

Location infrastructure platform for geofencing, geocoding, address validation, routing, and user location tracking.

Detail	Value
Category	Data
Base URL	https://api.radar.io/v1
Authentication	API Key
Endpoints	15
Connector key	radar

Using Radar in a workflow

1. Go to Connections and click New Connection.
2. Pick Radar from the marketplace.
3. Enter your credentials (see Authentication above for what's expected).
4. In a workflow, drop an API Call node and select this connection.
5. Pick the operation you need from the Operation dropdown — the full list is below.

Available endpoints

Endpoint	Summary
POST /track	Track device location
GET /geocode/forward	Forward geocode address to coordinates
GET /geocode/reverse	Reverse geocode coordinates to address
GET /geocode/ip	Geolocate IP address
GET /addresses/validate	Validate US/Canada address
GET /search/autocomplete	Autocomplete address or place name
GET /search/geofences	Find geofences near a location
GET /search/places	Find places near a location
GET /search/users	Find users near a location
GET /users	List users by last update time
GET /route/distance	Calculate travel distance and duration
GET /route/directions	Get turn-by-turn directions
GET /route/matrix	Calculate distance/duration matrix
GET /route/optimize	Optimize visit order for multiple locations
POST /route/match	Snap GPS trace to roads

Each endpoint is documented in full below. Use the outline on the right to jump to one.

POST /track

Track device location

Detail	Value
Operation ID	track.updateLocation
Method	POST
Path	/track

Parameters

No parameters.

Request Body

Field	Type
deviceId	string
userId	string
latitude	number
longitude	number
accuracy	number
foreground	boolean
stopped	boolean
metadata	object
deviceType	string

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Radar connection from the Connection dropdown.
3. In the Operation dropdown, select track.updateLocation.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Radar API reference.

GET /geocode/forward

Forward geocode address to coordinates

Detail	Value
Operation ID	geocode.forward
Method	GET
Path	/geocode/forward

Parameters

Name	Location	Type	Required
query	query	string	Yes
layers	query	string	No
country	query	string	No
lang	query	string	No

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Radar connection from the Connection dropdown.
3. In the Operation dropdown, select geocode.forward.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Radar API reference.

GET /geocode/reverse

Reverse geocode coordinates to address

Detail	Value
Operation ID	geocode.reverse
Method	GET
Path	/geocode/reverse

Parameters

Name	Location	Type	Required
coordinates	query	string	Yes
layers	query	string	No

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Radar connection from the Connection dropdown.
3. In the Operation dropdown, select geocode.reverse.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Radar API reference.

GET /geocode/ip

Geolocate IP address

Detail	Value
Operation ID	geocode.ip
Method	GET
Path	/geocode/ip

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Radar connection from the Connection dropdown.
3. In the Operation dropdown, select geocode.ip.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Radar API reference.

GET /addresses/validate

Validate US/Canada address

Detail	Value
Operation ID	addresses.validate
Method	GET
Path	/addresses/validate

Parameters

Name	Location	Type	Required
city	query	string	Yes
stateCode	query	string	Yes
postalCode	query	string	Yes
countryCode	query	string	Yes
number	query	string	No
street	query	string	No

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Radar connection from the Connection dropdown.
3. In the Operation dropdown, select addresses.validate.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Radar API reference.

GET /search/autocomplete

Autocomplete address or place name

Detail	Value
Operation ID	search.autocomplete
Method	GET
Path	/search/autocomplete

Parameters

Name	Location	Type	Required
query	query	string	Yes
near	query	string	No
layers	query	string	No
limit	query	integer	No
countryCode	query	string	No

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Radar connection from the Connection dropdown.
3. In the Operation dropdown, select search.autocomplete.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Radar API reference.

GET /search/geofences

Find geofences near a location

Detail	Value
Operation ID	search.geofences
Method	GET
Path	/search/geofences

Parameters

Name	Location	Type	Required
near	query	string	Yes
radius	query	integer	No
tags	query	string	No
limit	query	integer	No

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Radar connection from the Connection dropdown.
3. In the Operation dropdown, select search.geofences.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Radar API reference.

GET /search/places

Find places near a location

Detail	Value
Operation ID	search.places
Method	GET
Path	/search/places

Parameters

Name	Location	Type	Required
near	query	string	Yes
radius	query	integer	No
chains	query	string	No
categories	query	string	No
limit	query	integer	No

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Radar connection from the Connection dropdown.
3. In the Operation dropdown, select search.places.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Radar API reference.

GET /search/users

Find users near a location

Detail	Value
Operation ID	search.users
Method	GET
Path	/search/users

Parameters

Name	Location	Type	Required
near	query	string	Yes
radius	query	integer	No
limit	query	integer	No

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Radar connection from the Connection dropdown.
3. In the Operation dropdown, select search.users.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Radar API reference.

GET /users

List users by last update time

Detail	Value
Operation ID	users.list
Method	GET
Path	/users

Parameters

Name	Location	Type	Required
limit	query	integer	No
updatedBefore	query	string	No
updatedAfter	query	string	No

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Radar connection from the Connection dropdown.
3. In the Operation dropdown, select users.list.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Radar API reference.

GET /route/distance

Calculate travel distance and duration

Detail	Value
Operation ID	route.distance
Method	GET
Path	/route/distance

Parameters

Name	Location	Type	Required
origin	query	string	Yes
destination	query	string	Yes
modes	query	string	Yes
units	query	string	No
avoid	query	string	No

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Radar connection from the Connection dropdown.
3. In the Operation dropdown, select route.distance.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Radar API reference.

GET /route/directions

Get turn-by-turn directions

Detail	Value
Operation ID	route.directions
Method	GET
Path	/route/directions

Parameters

Name	Location	Type	Required
locations	query	string	Yes
mode	query	string	No
units	query	string	No
avoid	query	string	No
lang	query	string	No

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Radar connection from the Connection dropdown.
3. In the Operation dropdown, select route.directions.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Radar API reference.

GET /route/matrix

Calculate distance/duration matrix

Detail	Value
Operation ID	route.matrix
Method	GET
Path	/route/matrix

Parameters

Name	Location	Type	Required
origins	query	string	Yes
destinations	query	string	Yes
mode	query	string	Yes
units	query	string	No

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Radar connection from the Connection dropdown.
3. In the Operation dropdown, select route.matrix.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Radar API reference.

GET /route/optimize

Optimize visit order for multiple locations

Detail	Value
Operation ID	route.optimize
Method	GET
Path	/route/optimize

Parameters

Name	Location	Type	Required
locations	query	string	Yes
mode	query	string	No
units	query	string	No

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Radar connection from the Connection dropdown.
3. In the Operation dropdown, select route.optimize.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Radar API reference.

POST /route/match

Snap GPS trace to roads

Detail	Value
Operation ID	route.match
Method	POST
Path	/route/match

Parameters

No parameters.

Request Body

Field	Type
path	array
mode	string
units	string
roadAttributes	boolean

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Radar connection from the Connection dropdown.
3. In the Operation dropdown, select route.match.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Radar API reference.