baul.weigh.pending

A weigh_on_site (variable-weight, e.g. truffle) order was created in Baúl and is held in pending_weigh — Camino prompts the on-site contact for a scale photo, its AI vision reads the weight and POSTs it back to Baúl /api/orders/[id]/weigh-proposal (advisory; a human confirms in Pesajes). S513 Truffle v2.

Senders

• baul

Receivers

• camino

Data schema

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

{
  "orderId": "string (orders.id — Camino correlates the photo reply to this)",
  "operatorId": "string (baul operators.id)",
  "ecosystem_org_id": "string | null (operators.ecosystem_org_id — event routing)",
  "customerName": "string | null",
  "productName": "string | null",
  "notifyPhone": "string | null (operators.weigh_notify_phone, E.164 — null degrades v2 to v1 manual)",
  "is_demo": "boolean"
}

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.

{
  "orderId": "example-orderId",
  "operatorId": "example-operatorId",
  "ecosystem_org_id": "example-ecosystem_org_id",
  "customerName": "example-customerName",
  "productName": "example-productName",
  "notifyPhone": "example-notifyPhone",
  "is_demo": true
}

See also

• Events registry index
• Webhooks integration guide
• Errors & retries

---

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