PortPulsePortPulse

Freight Forwarders (3PL) — turn congestion into customer-facing exceptions

Power portals and emails with standardized port signals. Trigger exception workflows when wait time or queue length breaches lane rules, and export CSV with strong ETags for cheap scheduled jobs.

3PL exception workflows using normalized congestion and dwell signals
Exception-ready signals for portals, emails, and webhooks

Exception rules by lane

  • Congestion score > 0.65 for 5 days → alert
  • Queue length +30% w/w → reroute recommendation
  • Weekend bunching detector for gateway ports

White-label components

  • JSON/CSV parity for your UI and exports
  • Sparkline teasers for emails & portal cards
  • Unified error body with request_id for support

Operational reliability

  • Freshness SLO p95 ≤ 2h; explicit timestamps
  • Edge p95 < 300 ms with strong caching
  • ETag/304 for CSV to minimize bandwidth

Onboarding in hours

  • OpenAPI + Postman examples
  • 5 ports trial; drop into existing cron jobs
  • Consistent fields across 100+ ports
Forwarder portal modules with standardized congestion charts
Drop-in charts for customer-visible SLAs

Endpoints for exception flows

  • /v1/ports/USLAX/alerts — severity + explain fields
  • /v1/ports/USLAX/trend?days=14&fields=avg_wait_hours,queue_length
  • /v1/ports/SGSIN/overview — latest snapshot for teasers
  • /v1/meta/sources — source timing for audit
curl -H "X-API-Key: DEMO_KEY" \
  "https://api.useportpulse.com/v1/ports/USLAX/alerts"
Freshness (p95)
≤ 2h
Edge latency (p95)
≤ 300ms
CSV ETag
304 ready