Waymark / Routes / developers.tive.com Configure Tive webhooks to push shipment and tracker alert events to an external endpoint
domain: developers.tive.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checked community attestations: 0✓ / 0✗
Steps Authenticate via /public/v3/authenticate to get a bearer token Configure alert presets in the Tive Platform that define what conditions (e.g., temperature range) count as an alert Set up a webhook targeting your endpoint, scoping it with applyToAllShipments, applyToAllTrackers, or applyToAllAlertPresets flags Verify your endpoint receives a payload when a configured alert preset fires Add retry/backoff handling on your receiving endpoint for delivery failures Known gotchas Alert presets must exist in the Tive Platform first (or you scope the webhook to all presets) - the webhook itself doesn't define thresholds There is no public sandbox for triggering test events - validate against a live or dev shipment Webhook access still depends on the same platform account/admin prerequisites as the REST API
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp