Register a subscription once and we tell you when something happens, instead of you polling to find out.The service sits on top of the Insights APIs, so the events it raises are the same events those endpoints report.
Create a subscriptionPOST the settings: what to watch, which events matter, and how you want to hear about them. We generate events as they occur, in real or near-real time.
2
Receive notificationsBy webhook, by email, by polling a GET endpoint, or by any combination.
3
Manage it over timeEdit a subscription, deactivate it to pause delivery without losing the configuration, or delete it outright.
By IMO number. Right for high-value assets, vessels with a specific risk profile, or short-term monitoring.
A fleet
By fleet ID from Fleet Management. One subscription covers every vessel in the fleet, and it follows the fleet as members change.
A zone
Jurisdictional, standard or custom areas. Right for regional risk monitoring.
A port
Ports are addressed through the same zone-and-port surface.
Prefer fleet subscriptions where you can
A fleet subscription adjusts automatically when vessels join or leave the fleet. Individual subscriptions do not, so a fleet of forty vessels becomes forty things to maintain and forty chances to miss one.Use individual subscriptions for vessels that need different treatment from the group.
A vessel stops transmitting for longer than your threshold
Positional discrepancy
Reported position conflicts with other evidence
STS pairing
A ship-to-ship transfer is detected
ETA change
A vessel's reported arrival estimate changes
Destination change
A vessel's reported destination changes
Draught change
A change consistent with loading or discharging
MMSI change
A vessel's broadcast MMSI changes
Navigational status change
A change in reported status, such as under way or at anchor
Filters narrow these further. Zone filters take specific zone_ids, or whole classes of area through zone_types and zone_sub_types, so you can watch every anchorage or every EEZ without listing them.
The recommended route for integrations. Include a callback URL on the subscription, and we POST each notification to it as JSON the moment it is generated.
Test the receiver before you rely on it
Point a subscription at a request-capture service first and confirm the payload shape and your handling, then switch the callback URL to production. A webhook that fails silently looks the same from your side as a period with no events.
Useful where a person needs to see the event, not a system. Set it on the subscription alongside a webhook.scheduler.schedule_type decides whether email arrives one at a time or batched. 0 sends each notification as it is generated. Every other value batches notifications into a digest, and the number is how many digests you get a day:
schedule_type
Delivery
0
Immediate, one email per notification
1
One digest a day
2
Two digests a day
3
Three digests a day
4
Four digests a day
24
One digest an hour
These are the only values. at_time is the UTC time, as HH:mm, at which the first digest goes out, and the rest follow at evenly spaced times across the day, based on how many digests schedule_type specifies. Each digest attaches a CSV listing every notification generated in that period.A daily digest at a fixed time suits compliance review. Immediate email suits a small number of high-consequence events, and becomes noise above that.
Retrieve notifications for a subscription over a date range, or across all subscriptions at once. Useful for backfilling after an outage, for reconciliation, and for anything batch.The {id} in these paths is the subscription ID, not a vessel or zone identifier.
Webhook plus email is the common pattern: the system reacts, and a person retains oversight without watching a queue. Add the GET endpoints for reconciliation, so you can recover a missed webhook.
Name subscriptions for their purpose. You will have more than you expect, and custom_reference is what makes them findable later.
Deactivate instead of deleting when pausing. The configuration survives, and reactivating is one call.
Watch your volume before going wide. A zone subscription over a busy EEZ with entry and exit enabled generates much more traffic than the same subscription over open water.
Review subscriptions periodically. Monitoring set up for one concern outlives that concern. Check that each subscription still earns its volume.
