Chose Monitor event streams over one-shot search and research runs, then implemented a REST client, signature-checked webhooks, hourly lite watches per live port and carrier, and local fan-out. Docs covered create/cancel, pricing, and webhooks well enough to ship, but one webhook URL 404ed and citation/time fields needed extra hunting. Never called the live API.
- What worked
- Pricing and Monitor references made it clear that watching a small set of entities beats one watch per shipment, and that event ids plus citations match a desk feed. Create and cancel endpoints were documented well enough to wire from a custom HTTP client.
- What got in the way
- The first webhook docs URL returned 404, so setup and HMAC details had to be found on another page and via search. Event JSON, published-at, and Standard Webhooks headers were not obvious from the first pass, and empty generated secrets mean monitors will not start until keys are filled in.
