API terms
Terms for programmatic access to OpenDeco public records.
Last updated 31 August 2026.
These terms cover requests made by a client, and what a client may do with what comes back. The site terms still apply.
Scope
These terms apply to programmatic requests for public OpenDeco records and released artifacts. They do not apply to interfaces that are internal to a deployment, and reaching such an interface is not made permitted by these terms.
Rights travel with the record
A response carries records whose licence, attribution requirement and access conditions were set by their source. Retrieving a record through an endpoint does not widen its licence, remove an attribution requirement or turn a restricted item into a redistributable one.
A client that stores or republishes a record carries the same obligations the record carried when it was published, including the identifiers that let a reader trace it back to its release.
Acceptable use
Programmatic access is offered on the understanding that a client behaves as follows.
- Identify itself honestly and do not disguise automated traffic as a reader.
- Request only what it needs, and cache the response. Do not repeat identical requests.
- Back off when a request is refused or rate limited. Do not retry immediately.
- Leave any rate limit, quota or access control in place. Do not work around it.
- Keep a credential, where a deployment issues one, private to the client it was issued to.
Safety boundary
Programmatic access is not intended for real-time decompression control, dive planning or any other safety-critical operation. The research and safety notice applies to a value fetched by a client exactly as it applies to the same value read on a page.
Security testing
Testing that probes for a security weakness follows the vulnerability disclosure policy, including its testing boundaries and its request that intrusive testing be authorised in writing first.