Cause verification

POST /v1/vakis/{key}/verification

Not callable yet

Status: planned. Part of the compliance and onboarding phase, after webhooks. No date here; see the changelog.

Intended contract

{
  "state": "partner_verification",
  "verified_by": "comite-ejemplo",
  "evidence_url": "https://example.org/fichas/ficha-06.pdf",
  "notes": "Plan revisado por el comité el 2026-08-20"
}

202 Accepted:

{
  "object": "vaki_verification",
  "vaki": "clinicalaliga",
  "state": "partner_verification",
  "verified_by": "comite-ejemplo",
  "recorded_at": "2026-08-20T15:12:00Z"
}

Why this is later than it looks

The endpoint is a day of work. The thing it records is not.

Verification at Vaki is a human workflow: a review queue, evidence attachments, two-party sign-off, and an audit trail that survives someone asking “who approved this cause, and on what basis?” a year later. An endpoint that stamps verified without that behind it is worse than no endpoint — it is a claim nobody can defend.

It also adds a new value to the cause state machine, which is a coordinated change across the data model, admin filters, analytics and state guards rather than a one-file edit. Not hard; not something to discover at review time.

So: the contract is published, the endpoint is sequenced with the review workflow it depends on, and we are not shipping the stamp before the process.