Saildrone · Rate Limits

Saildrone Rate Limits

Saildrone has not published rate-limit numbers for the Public Mission API (BETA) on developer-mission.saildrone.com. Observed behavior from open source clients (e.g. nwfsc-fram/SaildroneTS) shows pagination via `limit` (default 1000 rows) and `interval` (minutes between samples) parameters rather than per-key request budgets. Bearer tokens issued by POST /v1/auth are short-lived and clients are expected to refresh them. Documented values below are derived from client code and Saildrone's stated "schema-driven, AI/ML-ready" design rather than from a published rate-limit page.

Saildrone Rate Limits is the machine-readable rate-limit profile for Saildrone on the APIs.io network, conforming to the API Commons Rate Limits specification.

The profile also includes 4 backoff/retry policies defined.

Tagged areas include Maritime, Ocean Data, and USV.

0 Limits
MaritimeOcean DataUSV

Policies

Mission API pagination window
The /v1/timeseries/{mission} endpoint paginates by `limit` rows per response, defaulting to 1000 in widely-used reference clients. Clients re-window using the latest gps_time and call again to advance.
Mission API sampling interval
Clients can pass `interval` (minutes) to thin the time series at the server side; default of 1 minute matches Saildrone's native 1-minute averaged METOC cadence.
Bearer token TTL
Bearer tokens are short-lived; observed Saildrone reference clients re-authenticate before each batch run. Saildrone has not published a fixed TTL value.
NOAA PMEL ERDDAP rate limits
Saildrone open data hosted on NOAA PMEL ERDDAP follows ERDDAP's own fair-use rate limits and per-IP concurrency caps, which are not Saildrone-controlled. Heavy users should follow ERDDAP best practices.

Sources