Integrations
Where what SeaLagom finds can go, and where your programs can take it from. Nothing here is sold separately: it comes with the plan that has the data.
Alerts go to
E-mail
ProfileRegion subscriptions, voyage alert rules, analysis alerts (your own prompts matched against every new warning), new warnings along a watched route.
Profile, Subscriptions and Alerts.
Telegram
About the botThe SeaLagom bot: the newest warnings of a NAVAREA, what is around a position, a vessel, a port, a coast station, and watches on a region with a severity floor.
Link your account from Profile, Security. The bot is enabled when its name shows there.
Slack, Discord, Microsoft Teams
A voyage alert rule or an analysis alert posts into a channel: paste the channel's incoming webhook URL as a recipient.
Slack: Apps, Incoming Webhooks. Discord: channel settings, Integrations, Webhooks. Teams: channel, Connectors or a Workflow with 'post to a channel when a webhook request is received'.
Zapier, Make, n8n, IFTTT, your own server
The same alerts as a JSON POST {event, id, sent_at, title, text, link, data} with X-Sealagom-Event, X-Sealagom-Delivery and X-Sealagom-Timestamp headers.
Paste the catch-hook URL of the tool as the recipient. Only public https URLs are called; the URL itself is your secret, keep it one nobody can guess.
Signed API webhooks
Webhook docsEvery new, changed or withdrawn warning, pushed to your server as it happens, signed with your webhook secret (HMAC-SHA256 of the body, and of timestamp.body).
Full API plan: set the URL and secret in the API settings, test it with one click.
Programs read from
API
API referenceWarnings, routes checked against them, themed feeds, noon reports and voyages, weather at a position, ports, distances, coast stations and zones.
One key, JSON or GeoJSON, OpenAPI description, rate limits by plan.
Python and JavaScript clients, MCP server, GitHub Action
Integration kitReady code: clients for both languages, an MCP server so a desktop agent can ask SeaLagom directly, an Action that checks a route file in CI.
Open source, on GitHub.
RSS and plain text
RSSThe newest warnings of every region or of one region, for feed readers, intranets, pagers and scripts.
No key. /feeds/warnings.xml, /feeds/navarea/<id>.xml, /feeds/coastal/<id>.xml, /feeds/warnings.txt.
ECDIS and GIS files
RegionsWarnings in force as files for JRC, Furuno, Transas, SevenCs ECDIS and for QGIS, Google Earth and OpenCPN.
From any region page or from the map, by plan.
Noon reports from any file
NoonExcel, Word, PDF, a photo of the log, an e-mail or plain text: SeaLagom reads the reports into the voyage; your own Excel template filled back.
The Noon tab on the map; the same through the API.
Sign in with GitHub or Google
Sign inNo new password.
On the sign-in page.
Security, in short: alerts and webhooks are only ever sent to public https addresses; signed deliveries carry a timestamp and a delivery id so your server can refuse a replay; API keys can be regenerated in Profile at any time. Signal and WhatsApp have no open bot access for a service like this; if your company needs one, write to [email protected].