NOAA CO-OPS Slr Projections API
The Slr Projections API from NOAA CO-OPS — 1 operation(s) for slr projections.
NOAA CO-OPS Slr Projections API is one of 13 APIs that NOAA CO-OPS publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Slr Projections. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.
This API exposes 1 operation across 1 path. It is described by OpenAPI 3.2.0, at version 1.0.0.
Requests are made against a single base URL, https://api.tidesandcurrents.noaa.gov/api/prod.
Metadata
The identity and technical contract details declared by the specification.
Paths & Operations 1
Across 1 path, the API surfaces 1 operation — 1 GET. Each is listed below with its method, path, parameters, and response codes.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from NOAA CO-OPS 12
Other APIs NOAA CO-OPS publishes across the network.
This is an independent, third-party profile of NOAA CO-OPS Slr Projections 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.