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

U.S. Geological Survey Monitoring Locations API

USGS stream gages, groundwater wells, and other water monitoring stations.

U.S. Geological Survey Monitoring Locations API is one of 11 APIs that U.S. Geological Survey publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 3 JSON Schema definitions.

Tagged areas include Monitoring Locations. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a getting-started guide, a JSON-LD context, authentication docs, and 3 JSON Schemas.

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

Requests are made against a single base URL, https://earthquake.usgs.gov/fdsnws/event/1.

2 operations 2 paths 4 schemas 2 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
1.0
Base URL
https://earthquake.usgs.gov/fdsnws/event/1
Resource Areas
1

Paths & Operations 2

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

Monitoring Locations 2

USGS stream gages, groundwater wells, and other water monitoring stations.

GET
/collections/monitoring-locations/items
USGS Water Data Get Monitoring Locations
getMonitoringLocations 8 params → 200400403429
GET
/collections/monitoring-locations/items/{featureId}
USGS Water Data Get Monitoring Location by ID
getMonitoringLocation 2 params → 200403404

Schemas 4

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

MonitoringLocationCollection
object
GeoJSON FeatureCollection of USGS monitoring locations.
4 properties
ErrorResponse
object
Standard OGC API error response.
2 properties
MonitoringLocationFeature
object
GeoJSON Feature for a single USGS water monitoring location.
3 properties
MonitoringLocationProperties
object
Attributes describing a USGS water monitoring location.
9 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

u-s-geological-survey-monitoring-locations-api-openapi.yml Raw ↑

Other APIs U.S. Geological Survey publishes across the network.

Asset Identifier Service (AIS)
Seismic Design Web Service
ScienceBase
StreamStats Web Services
USGS Water Services (Legacy)
U.S. Geological Survey Catalog API
USGS Water Data OGC API
U.S. Geological Survey Earthquakes API
U.S. Geological Survey Reference Data API
U.S. Geological Survey Time Series Data API
Where this information came from

This is an independent, third-party profile of U.S. Geological Survey Monitoring Locations 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.