Skip to content
Changelog

Report a bug

Radar integration: operations for AI agents

Radar connects to Type.com as an integration. This page lists the 46 operations documented for Claude and Codex in Type.com: 25 read, 14 write, 7 destructive.

About Radar

Radar is a full-stack location infrastructure platform offering SDKs and APIs for geofencing, location tracking, geocoding, search, routing, and maps.

Categories: Developer Tools & IT

How to connect Radar to Type.com

Access
Organization connection: one shared account for the workspace.

To add the connection, follow the steps in Space connections.

Documented operations

46 operations. Your connection's permissions determine which operations are available. API references describe the vendor surface; they do not expand your connection's credentials or access.

46 operations listed.

Track

  • Write

    Track

    Tracks a location update. Returns the user and the events generated, depending on project settings. On iOS and Android, use the SDK to track user locations in the foreground or in the background. `deviceId` is used to identify logged out users. `userId` and `deviceId` are used to identify logged in users. If a matching user already exists, it will be updated. If not, a new user will be created. Do not send any PII, like names, email addresses, or publicly available IDs, for `userId`. See privacy best practices for more information.

    POST /v1/track

Geocoding

  • Read

    Forward geocode

    Geocodes an address, converting address to coordinates. This endpoint is best for complete addresses. For partial addresses or place names, call the autocomplete endpoint instead. Returns a confidence level indicating the certainty of the result's latitude and longitude: * **`exact`**: Precise coordinates for a known address location. * **`interpolated`**: Estimated coordinates between two known address points when an exact address location is unavailable. * **`fallback`**: Coarse coordinates (e.g., postal code/city) for the containing region when no precise location is available.

    GET /v1/geocode/forward

  • Read

    Reverse geocode

    Reverse geocodes a location, converting coordinates to address.

    GET /v1/geocode/reverse

  • Read

    IP geocode

    Geocodes the requester's IP, converting IP address to city, state, and country.

    GET /v1/geocode/ip

Search

  • Read

    Autocomplete

    Autocompletes partial addresses and place names, sorted by relevance and proximity.

    GET /v1/search/autocomplete

  • Read

    Search users

    Searches for users near a location, sorted by distance.

    GET /v1/search/users

  • Read

    Search geofences

    Searches for geofences near a location, sorted by distance.

    GET /v1/search/geofences

  • Read

    Search places

    Searches for places near a location, sorted by distance.

    GET /v1/search/places

  • Read

    Validate an address

    Validates an address. Currently only available for US and Canada addresses for enterprise customers. This endpoint is best for validating complete structured addresses. For partial addresses or place names, call the autocomplete endpoint instead. Returns a `verificationStatus` as part of the `result`, as defined below: * `verified`: The input has a complete and unique match with a result. * `partially verified`: The input has a partial match with a result. * `ambiguous`: The input closely matches multiple results. * `unverified`: Unable to verify the input address. Returns a `recordType` value in the `metadata` field as part of the `result`, values are defined below according to USPS standards: * `S`: Street Address * `P`: Post Office Box * `R`: Rural Route * `H`: High-rise * `F`: Firm * `G`: General Delivery On US addresses, an `analysis` field may be returned, which contains the following fields: * `unit:missing`: Radar detected units at the address, but no unit was specified. * `unit:invalid`: Radar detected units at the address, but the unit specified doesn't exist.

    GET /v1/addresses/validate

Routing

  • Read

    Distance

    Calculates the travel distance and duration between an origin and a destination.

    GET /v1/route/distance

  • Read

    Matrix

    Calculates the travel distances and durations between multiple origins and destinations for up to 625 routes.

    GET /v1/route/matrix

  • Read

    Directions

    Calculates the most efficient route between two or more locations to visit in order.

    GET /v1/route/directions

  • Read

    Optimize route

    Calculates the optimal ordering and route to visit a list of locations.

    GET /v1/route/optimize

  • Write

    Route match

    Snaps points collected along a route to roads that were most likely traveled on. Returns the matched path and road information. For best results, the sample rate should be less than 10 seconds between points.

    POST /v1/route/match

Users

  • Read

    List users

    Lists users. Users are sorted descending by `updatedAt`.

    GET /v1/users

  • Read

    Get a user

    Gets a user. The user can be referenced by Radar `_id`, `userId`, or `deviceId`.

    GET /v1/users/:id

  • Write

    Send remote track requests to users

    Sends a remote track request to a list of users via silent push notifications.

    POST /v1/users/refresh

  • Destructive

    Delete a user

    Deletes a user. The user can be referenced by Radar `_id`, `userId`, or `deviceId`.

    DELETE /v1/users/:id

Trips

  • Read

    Get a trip

    Gets a trip. The trip can be referenced by Radar `_id` or `externalId`.

    GET /v1/trips/:id

  • Read

    Get a trip

    Gets a trip. The trip can be referenced by Radar `_id` or `externalId`.

    GET /v1/trips/:externalId

  • Read

    List trips

    List trips.

    GET /v1/trips

  • Write

    Create a new trip

    Use the SDK to start trips and track users for most use cases. Trips can also be created server-side or through integrations (e.g., Olo). Location updates with the specified `userId` from the SDK will update the trip for that user.

    POST /v1/trips

  • Write

    Update a trip

    Updates a trip. The trip can be referenced by Radar `_id` or `externalId`. On iOS and Android, use the SDK to update trips.

    PATCH /v1/trips/:id/update

  • Write

    Update a trip

    Updates a trip. The trip can be referenced by Radar `_id` or `externalId`. On iOS and Android, use the SDK to update trips.

    PATCH /v1/trips/:externalId/update

  • Destructive

    Delete a trip

    Deletes a trip. The trip can be referenced by Radar `_id` or `externalId`.

    DELETE /v1/trips/:id

Geofences

  • Read

    List geofences

    List geofences.

    GET /v1/geofences

  • Read

    Get a geofence

    Gets a geofence. The geofence can be uniquely referenced by Radar `_id` or by `tag` and `externalId`.

    GET /v1/geofences/:id

  • Read

    Get a geofence

    Gets a geofence. The geofence can be uniquely referenced by Radar `_id` or by `tag` and `externalId`.

    GET /v1/geofences/:tag/:externalId

  • Read

    Get users in a geofence

    Gets users currently in a geofence.

    GET /v1/geofences/:tag/:externalId/users

  • Write

    Upsert a geofence

    Upserts a geofence. The geofence can be uniquely referenced by `tag` and `externalId` or by the Radar `_id`. If a geofence with the specified `tag` and `externalId` already exists, it will be updated. If not, it will be created.

    PUT /v1/geofences/:tag/:externalId

  • Write

    Upsert a geofence

    Upserts a geofence. The geofence can be uniquely referenced by `tag` and `externalId` or by the Radar `_id`. If a geofence with the specified `tag` and `externalId` already exists, it will be updated. If not, it will be created.

    PUT /v1/geofences/:id

  • Destructive

    Delete a geofence

    Deletes a geofence. The geofence can be uniquely referenced by Radar `_id` or by `tag` and `externalId`.

    DELETE /v1/geofences/:id

  • Destructive

    Delete a geofence

    Deletes a geofence. The geofence can be uniquely referenced by Radar `_id` or by `tag` and `externalId`.

    DELETE /v1/geofences/:tag/:externalId

Events

  • Write

    Log a conversion

    > [!NOTE] > > Conversions are available on the **Enterprise plan**. Logs a conversion to analyze alongside other location activity in your app. This can represent anything from a purchase or signup to engagement with an in-app feature.

    POST /v1/events

Beacons

  • Read

    List beacons

    Lists beacons. Beacons are sorted descending by `createdAt`.

    GET /v1/beacons

  • Read

    Get a beacon

    Gets a beacon. The beacon can be uniquely referenced by Radar `_id` or by `tag` and `externalId`.

    GET /v1/beacons/:id

  • Read

    Get a beacon

    Gets a beacon. The beacon can be uniquely referenced by Radar `_id` or by `tag` and `externalId`.

    GET /v1/beacons/:tag/:externalId

  • Write

    Create a beacon

    Creates a beacon.

    POST /v1/beacons

  • Write

    Upsert a beacon

    Upserts a beacon. The beacon can be uniquely referenced by Radar `_id` or by `tag` and `externalId`. If a beacon with the specified `tag` and `externalId` already exists, it will be updated. If not, it will be created.

    PUT /v1/beacons/:id

  • Write

    Upsert a beacon

    Upserts a beacon. The beacon can be uniquely referenced by Radar `_id` or by `tag` and `externalId`. If a beacon with the specified `tag` and `externalId` already exists, it will be updated. If not, it will be created.

    PUT /v1/beacons/:tag/:externalId

  • Destructive

    Delete a beacon

    Deletes a beacon. The beacon can be uniquely referenced by Radar `_id` or by `tag` and `externalId`.

    DELETE /v1/beacons/:id

  • Destructive

    Delete a beacon

    Deletes a beacon. The beacon can be uniquely referenced by Radar `_id` or by `tag` and `externalId`.

    DELETE /v1/beacons/:tag/:externalId

Fraud

  • Write

    Unblock users and devices

    Disables block rules for the specified users or devices. Each item targets exactly one user or device; unblocking a user does not unblock their devices, and unblocking a device does not unblock its users. If a target does not exist or has no block rules to disable, the item succeeds with `changedBlockCount` set to `0`.

    POST /v1/fraud/unblock

  • Destructive

    Block users and devices

    Creates block rules for existing users or devices. Each item targets exactly one user or device; blocking a user does not automatically block their devices, and blocking a device does not automatically block its users. Each successful block creates a new rule, even if the target is already blocked. If a user or device does not exist in the project and environment associated with your API key, the item succeeds without creating a rule.

    POST /v1/fraud/block

Places settings

  • Read

    Get Places settings

    Gets your current Places settings.

    GET /v1/settings

  • Write

    Update Places settings

    Updates your Places settings.

    PATCH /v1/settings

See How connections work for access and permissions, or browse all integrations.

Reference date: October 28, 2026. Radar API docs.