specification: API Commons Rate Limits
specificationVersion: '0.1'
schema: https://raw.githubusercontent.com/api-evangelist/interface-research/main/schema/api-commons.yml#/$defs/RateLimits
provider: DNV
providerId: dnv
created: '2026-05-04'
# Provenance stamped 2026-08-11: this artifact was written by the API Evangelist
# bulk sweep dated 2026-05-04, not harvested from the provider. See roadmap#35.
method: generated
modified: '2026-05-05'
reconciled: false
tags:
  - Maritime
  - Classification
  - Vessel
  - Rate Limiting
description: DNV does not publish per-second/per-minute rate limits for its Maritime customer APIs. Access
  is gated by a signed API contract and OAuth 2.0 client credentials issued via Azure AD B2C. Access tokens
  are valid for ~20 minutes and should be reused across requests. Effective limits are governed by the
  contract and fair-use review.
sources:
  - https://maritime.dnv.com/api/cs-iacs-customer
  - https://maritime.dnv.com/api/cs-iacs-customer/docs/index.html
notes: No published rate-limit numbers; reconciled=false. Token reuse guidance and OAuth flow are documented;
  per-call throttles are not.
responseCodes:
  throttled: 429
  serviceUnavailable: 503
limits:
  - name: Contract-bound API access
    scope: contract
    metric: varies
    limit: see DNV API contract / contact local DNV representative
    notes: Effective limits are governed by the contract. No public RPS/RPM numbers are published.
policies:
  - name: Token Reuse
    description: OAuth 2.0 access tokens (Azure AD B2C) are valid for ~20 minutes and should be reused
      across HTTP requests rather than re-acquired per call.
  - name: Backoff Strategy
    description: Clients should implement exponential backoff with jitter on 429/503 responses.
  - name: Contracted Access
    description: A DNV API contract must be signed; the named technical contact receives client_id / client_secret.
maintainers:
  - FN: Kin Lane
    email: kin@apievangelist.com