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

Federal Highway Administration Geofence Expiration API

Geofence expiration management endpoints

Federal Highway Administration Geofence Expiration API is one of 12 APIs that Federal Highway Administration publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Geofence Expiration. The published artifact set on APIs.io includes an OpenAPI specification and a support channel.

This API exposes 3 operations across 3 paths, and defines 9 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against a single base URL, http://localhost:8080.

3 operations 3 paths 9 schemas 2 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Server
http://localhost:8080
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Federal Highway Administration Geofence Expiration API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (BearerAuth). By default, every request must be authenticated.

  • BearerAuth — Keycloak JWT Bearer Token. Required for all endpoints except decode endpoints. Obtain a token from the /auth/token endpoint using your credentials.

Paths & Operations 3

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

Geofence Expiration 3

Geofence expiration management endpoints

POST
/prd/v2/deposit/geofence/expiration/cleanup
Manually trigger Geofence expiration cleanup
triggerCleanup → 200401403500
GET
/prd/v2/deposit/geofence/expiration/expired
Get expired Geofence deployments
getExpiredGeofenceDeployments → 200401403500
GET
/prd/v2/deposit/geofence/expiration/cleanup/status
Get cleanup service status
getCleanupStatus → 200401403500

Schemas 9

The contract defines 9 schemas that model the data the API accepts and returns. The most detailed are GeofenceDeploymentResponse (10 properties), GeofenceFeature (3 properties), GeofenceFeatureCollection (2 properties), ErrorResponse (2 properties). Each schema is shown below with its type and property counts.

MultiLineString
GeofenceFeature
object
GeoJSON Feature representing a single geometric element within a geofence
3 properties 1 required
GeofenceDeploymentResponse
object
Response model for Geofence deployment
10 properties
Polygon
GeofenceFeatureCollection
object
GeoJSON FeatureCollection representing a geofence area
2 properties
MultiPolygon
Geometry
object
1 property 1 required
LineString
ErrorResponse
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

federal-highway-administration-geofence-expiration-api-openapi.yml Raw ↑

Other APIs Federal Highway Administration publishes across the network.

Federal Highway Administration
Federal Highway Administration Authentication API
Federal Highway Administration Configuration Rest Controller API
Federal Highway Administration Deposit API
Federal Highway Administration Geofence Deployments API
Federal Highway Administration Path Management API
Federal Highway Administration Registration API
Federal Highway Administration Secret Management API
Federal Highway Administration TIM Configuration API
Federal Highway Administration User Limits Management API
Federal Highway Administration Vendor Limits Management API
Where this information came from

This is an independent, third-party profile of Federal Highway Administration Geofence Expiration 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.