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

United States Army Corps of Engineers Locations API

USACE location data including dams, reservoirs, streamgages, and sites

United States Army Corps of Engineers Locations API is one of 10 APIs that United States Army Corps of Engineers publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Locations. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and a GitHub repository.

This API exposes 5 operations across 2 paths, and defines 3 schemas. It is described by OpenAPI 3.1.0, at version 3.0.0.

Requests are made against 2 base URLs: https://cwms-data.usace.army.mil/cwms-data, https://water.usace.army.mil/cwms-data.

5 operations 2 paths 3 schemas 1 DELETE2 GET1 PATCH1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
3.0.0
Base URL
https://cwms-data.usace.army.mil/cwms-data
Authentication
HTTP Bearer
License
Resource Areas
1

Authentication & Security 1

United States Army Corps of Engineers Locations API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (bearerAuth).

  • bearerAuth — JWT Bearer token for authenticated operations (create, update, delete). Obtain a token from the CWMS authorization endpoint.

Paths & Operations 5

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

Locations 5

USACE location data including dams, reservoirs, streamgages, and sites

GET
/locations
Get Locations
getLocations 5 params → 200400
POST
/locations
Create Location
createLocation body → 200400401
GET
/locations/{location-id}
Get Location
getLocation 3 params → 200404
PATCH
/locations/{location-id}
Update Location
updateLocation 1 param body → 200401404
DELETE
/locations/{location-id}
Delete Location
deleteLocation 2 params → 200401404

Schemas 3

The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are Location (18 properties), Error (2 properties), LocationsResponse (1 property). Each schema is shown below with its type and property counts.

Error
object
2 properties
LocationsResponse
object
1 property
Location
object
18 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

united-states-army-corps-of-engineers-locations-api-openapi.yml Raw ↑

Other APIs United States Army Corps of Engineers publishes across the network.

United States Army Corps of Engineers Basins API
United States Army Corps of Engineers Catalog API
United States Army Corps of Engineers Forecasts API
United States Army Corps of Engineers Levels API
United States Army Corps of Engineers Parameters API
United States Army Corps of Engineers Projects API
United States Army Corps of Engineers Ratings API
United States Army Corps of Engineers Time Series API
United States Army Corps of Engineers Version API
Where this information came from

This is an independent, third-party profile of United States Army Corps of Engineers 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.