Why now
IMO's revised ECDIS performance standards (MSC.530(106)) bring S-100 onto the bridge, and S-124 is the product for navigational warnings in it. The specification is ready; the data is not. National coordinators still publish text: NAVTEX, web pages, PDFs. Neptun bridges that gap: you can build, test and demonstrate S-124 in your product today with real, current warnings instead of hand-made samples.
What you get
Each request returns a ZIP containing one S-100 exchange set. Unpacked, it looks like this:
Who sent it, and is it unchanged?
S-124 is not just a data format. A receiver has to know who issued a warning and that nobody altered it on the way. Neptun covers three layers:
Each dataset names the authority that issued the warning in agencyResponsibleForProduction, with its series, number and year. The file name carries our producer code NPTN.
Every dataset and the catalogue are signed (DSA, SHA-256). The certificates are in the catalogue, so a receiver can check the data without asking us.
Today: HTTPS with an API key. Next: a SECOM service (IEC 63173-2) where both sides identify with Maritime Connectivity Platform certificates.
What we are, and what we are not
Neptun distributes official warnings; it does not issue them. We sign as Neptun, never in the name of an authority. The original source prevails. Our certificates come from Neptun's own test scheme administrator, not from the IHO scheme used for type-approved ECDIS, so an ECDIS in operation will not accept them. That is fine for development, testing and situational awareness. Every catalogue entry is marked notForNavigation. The data does not replace the official reception of navigational warnings via NAVTEX/GMDSS.
API
GET /v1/warnings/s124?bbox=minLat,minLon,maxLat,maxLon
Exchange set (ZIP) for an area; also lat/lon/radius, lang, source, since. Up to 1,000 datasets per package; page with the X-Neptun-Next-Offset header.
GET /v1/warnings/s124/{mid}
A single warning as an S-124 dataset (GML), by its Neptun ID.
curl -H "Authorization: Bearer mapi_…" -o navarea-x.zip \
"https://neptun.marine-api.com/v1/warnings/s124?bbox=-60,90,0,170&lang=en"
How a warning becomes S-124
| Neptun field | S-124 | Note |
|---|---|---|
| nts “AUSCOAST 317/26” | messageSeriesIdentifier | series AUSCOAST, number 317, year 2026 |
| series name | warningType | NAVAREA, coastal or local warning |
| source authority | agencyResponsibleForProduction | the issuing authority |
| category / kind | navwarnTypeGeneral, navwarnTypeDetails | IHO labels; details only where unambiguous |
| place, detail | navwarnTitle, information | in the requested language |
| valid_from / valid_until | fixedDateRange, cancellationDate | |
| closed | restriction | Entry Prohibited |
| polygon, line, position | S100:Surface, Curve, Point | approximate positions get no geometry |
Check it yourself
Every release is tested against the official IHO schemas (S-124 2.0.0, S-100 5.0.0 exchange catalogue and Part 15), and every signature is verified. You can do the same with the sample and our public certificates:
unzip neptun-s124-sample-navarea-x.zip
xmllint --noout --schema 124_2.0.0.xsd S100_ROOT/S-124/DATASET_FILES/NPTN/*.GML
openssl verify -CAfile neptun-s100-test-root.pem neptun-data-server-nptn.pem
Certificates
Neptun S-100 test scheme administrator SHA-256 906ae33e97a555da640ff24f1620f3502b7d035aebfe1427cd53df1b67fd08cd
Neptun data server NPTN SHA-256 7aa127b7f35efd310f326f9851a3872843d9e91458a57739491b238e57fc4b2a
Next steps
- SECOM service (IEC 63173-2) with Maritime Connectivity Platform identities
- In-force bulletins and cancellation references (
References) - Producer code from the IHO S-62 register
For NAVAREA and national coordinators
Your warnings already exist as text. Neptun turns them into an S-124 draft; your staff check and release it, and it is signed with your own key in your environment. We never see your key. If you want to see your own warnings in S-124, write to us and we will send you a package.
Access and pricing
S-124 is offered on request: trial access for development and testing, and licences for use and redistribution in your product. Write to [email protected] with a sentence about your project.
Questions
Which edition?
S-124 Edition 2.0.0 (IHO schema build 20250729) on the S-100 5.0.0 GML profile.
Why are there no code values in the enumerations?
S-124 makes the numeric code optional. The labels are normative, so we deliver labels only. That way no wrong code can creep in.
Which languages?
The texts come in the language you ask for (lang), and the language code is set in every text element.
Where does the data come from?
From the official sources listed on the coverage page. Each dataset names its authority; the original always prevails.