How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Radar Geofences API

Create, read, update, and delete geofences.

Radar Geofences API is one of 9 APIs that Radar publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Geofences. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 4 operations across 2 paths, and defines 5 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against a single base URL, https://api.radar.io/v1.

4 operations 2 paths 5 schemas 1 DELETE2 GET1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.radar.io/v1
Authentication
API Key
Terms of Service
Resource Areas
1

Authentication & Security 1

Radar Geofences API declares 1 security scheme for authenticating requests. An API key is passed in the header as Authorization (RadarKey). By default, every request must be authenticated.

  • RadarKey — A Radar publishable (client) key (prjlivepk... / prjtestpk...) or secret (server) key (prjlivesk... / prjtestsk...), passed in the Authorization header without…

Paths & Operations 4

Across 2 paths, the API surfaces 4 operations — 1 DELETE, 2 GET, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Geofences 4

Create, read, update, and delete geofences.

GET
/geofences
List geofences.
listGeofences 2 params → 200
PUT
/geofences/{tag}/{externalId}
Create or update a geofence.
upsertGeofence 2 params body → 200
GET
/geofences/{tag}/{externalId}
Get a geofence.
getGeofence 2 params → 200
DELETE
/geofences/{tag}/{externalId}
Delete a geofence.
deleteGeofence 2 params → 200

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are Geofence (11 properties), GeofenceUpsertRequest (6 properties), GeofenceResponse (2 properties), GeofenceListResponse (2 properties). Each schema is shown below with its type and property counts.

GeofenceUpsertRequest
object
6 properties 2 required
GeofenceListResponse
object
2 properties
GeofenceResponse
object
2 properties
Geofence
object
11 properties
Meta
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

radar-io-geofences-api-openapi.yml Raw ↑

Other APIs Radar publishes across the network.

Radar Addresses API
Radar Events API
Radar Geocoding API
Radar Routing API
Radar Search API
Radar Tiles API
Radar Track API
Radar Trips API
Where this information came from

This is an independent, third-party profile of Radar Geofences API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.