Skip to content

shipment.status_changed

Agente updated shipment status (assigned, in_transit, delivered, exception). PD-160 (S406): receivers list is currently empty — agente code hardcodes targets:['camino'] in camino-emit.ts, so the event is delivered to camino via its existing handler chain (caracol.shipment.created etc.), not via this registry entry. Kept as a forward-design slot; remove or repopulate based on S404 routing decision.

Senders

  • agente

Receivers

None declared.

Data schema

Each field maps to a type hint. | null indicates an optional field.

json
{
  "shipmentId": "string",
  "status": "string (assigned|in_transit|delivered|exception)",
  "updatedAt": "timestamp"
}

Example payload

The following is a synthetic payload that matches the schema. Production payloads are signed with HMAC-SHA256 and delivered to each receiver's registered webhook endpoint.

json
{
  "shipmentId": "example-shipmentId",
  "status": "assigned",
  "updatedAt": "example-updatedAt"
}

See also


Generated from ecosystem-sdk/packages/mcp-server/src/registry/events.json. Do not edit by hand.

Red Broom Software Ecosystem