U.S. Geological Survey Time Series Revisions API
Approved water data are considered published record, but on occasion changes or deletions (revisions) must be made to data after they are approved. Data revisions are rare because of USGS quality assurance practices, including documentation of all data before they are officially approved. This field contains text explanations for data revisions on a specific time series. Changes to data also are indicated with revision qualifier codes alongside the data. Text explanations before 2017 are not necessarily available online, but can be requested. This collection is non-spatial: revision records carry no geometry, so bbox/spatial filters are not supported.
U.S. Geological Survey Time Series Revisions API is one of 47 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 time-series-revisions. 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 8 operations across 5 paths, and defines 5 schemas. It is described by OpenAPI 3.2.0, at version 0.71.7.
Requests are made against a single base URL, https://api.waterdata.usgs.gov/ogcapi/v0.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 2
U.S. Geological Survey Time Series Revisions API declares
2 security schemes
for authenticating requests.
An API key is passed in the header as api_key (ApiKeyHeader).
An API key is passed in the query as api_key (ApiKeyQuery).
ApiKeyHeader— Providing your API key gives you higher rate limits when querying our APIs. You can obtain an API key at https://api.waterdata.usgs.gov/signupApiKeyQuery— Providing your API key gives you higher rate limits when querying our APIs. You can obtain an API key at https://api.waterdata.usgs.gov/signup
Paths & Operations 8
Across 5 paths, the API surfaces 8 operations — 5 GET, 2 OPTIONS, 1 POST. Each is listed below with its method, path, parameters, and response codes.
Approved water data are considered published record, but on occasion changes or deletions (revisions) must be made to data after they are approved. Data revisions are rare because…
Schemas 5
The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are queryable (6 properties), TimeSeriesRevisionsFeatureCollection (6 properties), TimeSeriesRevisionsFeature (4 properties), Error (1 property). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from U.S. Geological Survey 12
Other APIs U.S. Geological Survey publishes across the network.
This is an independent, third-party profile of U.S. Geological Survey Time Series Revisions 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.