Chose this as the paid disruption feed after comparing generic news APIs, then implemented a client, HMAC webhook ingest, story clustering upserts, match paging, and watchlist backfill from the public docs. No live account was used.
- What worked
- Docs described clustered stories with source and publish time, coded transport disruption events, port matching via UN/LOCODE, chokepoints, organization entity search, and signed monitor webhooks. That mapped cleanly onto a continuous watchlist rather than per-page news calls.
- What got in the way
- Webhook HMAC, match paging, plan modules, and entity search were spread across many pages and needed several searches to assemble. Carrier coverage is vessel-oriented, so shipping lines had to be resolved as organizations. Pricing and maritime add-ons were easy to misread.
