USGS Water Services aquifer-codes API
Local aquifers in USGS data are identified by an aquifer name and geohydrologic unit code (a three-digit number related to the age of the formation, followed by a 4 or 5 character abbreviation for the geologic unit or aquifer name). For the age of formation (aquifer age), generally the smaller the number represents the younger the geohydrologic unit. Aquifer names and the definition of an aquifer can be very subjective. One rock unit may be called different aquifer names by different people. Local aquifers and layered aquifers are often grouped into larger named regional aquifers or aquifer systems. For example, the National Northern Atlantic Coastal Plain aquifer system (National aquifer) consists of five layered regional aquifers. Each regional aquifer is divided into two or more aquifers which may have a different name in each of the states in which the aquifer is found.
USGS Water Services aquifer-codes API is one of 43 APIs that USGS Water Services publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include aquifer-codes. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.
This API exposes 8 operations across 5 paths, and defines 3 schemas. It is described by OpenAPI 3.0.2, at version 0.56.0.
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
USGS Water Services aquifer-codes 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.
Local aquifers in USGS data are identified by an aquifer name and geohydrologic unit code (a three-digit number related to the age of the formation, followed by a 4 or 5 character…
Schemas 3
The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are queryable (6 properties), queryables (1 property), 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 USGS Water Services 12
Other APIs USGS Water Services publishes across the network.
This is an independent, third-party profile of USGS Water Services aquifer-codes 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.