The TideSpy Tide Data REST API accepts web HTTPS requests and returns JSON-formatted responses. All requests must contain a valid key which is assigned when signing up for this service.
HTTP requests are accepted but will be redirected to HTTPS. If you receive 301 or similar error responses, your first action should be a change to send HTTPS requests only.
The following request types are supported:
Details of the places (locations) for which data is available
Place name search
Place search by location
Tide height data for a range of dates
Wind and Swell forecasts, both in numeric terms and human-friendly text, for the next 6 or more days
Sun and Moon rise and set times and the phase of the moon, for a given range of dates
The places covered include the USA, Caribbean Islands, most central and eastern Pacific Islands, New Zealand, and maybe Australia (maybe, because unlike the other places they're oddly possessive of their tide predictions).
Tide information is available for at least the previous and following 12 months. Other data, such as wind and swell, are only forecast for a week or so into the future.
All data is corrected for local time zone and daylight saving corrections, and generally tide data is obtained from official sources, though it must not be regarded or labelled as "Official".
See the rest of this site for individual API details.
If you try to use an API and find it is not enabled for you, please email api@ofu.co.nz and say which APIs you wish to use and a brief explanation why, and we will enable them.
We, Technology Solutions and OceanFun Publishing limited, make the following statement concerning the use of this API:
While we take care to publish accurate data, and errors are rare, we cannot accept liability for damages caused as a result of the use of information supplied via the TideSpy API. The tide information is not intended for navigational, piloting, engineering, or any application where safety is concerned.
Sailors should consult official tide tables, particularly when navigating in shallow waters or in strong tidal currents.
We strongly recommend that API users who publish this data for public or private use by third parties also include a disclaimer similar to this.