Cause updates

POST /v1/vakis/{key}/updates

Not callable yet

Status: next. This is the smallest endpoint on the roadmap and it lands in the same phase as webhooks. No date here; see the changelog.

Intended contract

{
  "title": "Entrega en Pereira",
  "body": "Entregamos 120 kits de aseo en el barrio San Jorge…",
  "images": ["https://example.org/entregas/pereira-01.jpg"],
  "notify_supporters": true
}

201 Created:

{
  "id": "upd_01J9Z4M2K7QF3B",
  "object": "vaki_update",
  "vaki": "clinicalaliga",
  "title": "Entrega en Pereira",
  "notified": true,
  "created_at": "2026-08-17T14:00:00Z"
}

With notify_supporters: true, everyone who donated to the cause is notified.

Why this one is worth waiting for

It closes the transparency loop automatically. If your product already publishes delivery or impact records, each one becomes an update in front of the exact people whose money paid for it — without anyone copying text between two systems.

It maps onto machinery Vaki already has (the update model and the supporter notification path), which is why the build is small. It is sequenced after webhooks only because webhooks unblock more.