Ensure WABA funding
Verifies an external multi-partner solution account with Meta and ensures Kapso funding for it, without waiting for the Meta association webhook. Use it after Embedded Signup completes.
Your project must have exactly one active external multi-partner solution; you cannot select a solution or project, set the WABA currency, or supply a token. When the membership is unknown, Kapso reads the WABA through that solution and verifies its owning portfolio before recording the association. Financial setup then runs in the background.
202 means a funding run is pending or running - it is not confirmation that the
account is funded. Poll GET /whatsapp/accounts/{waba_id}/funding until the run reaches
a terminal state and the funding status is funded. 200 is returned when the account
is already funded or when no new run was started.
Idempotent on desired state, with no Idempotency-Key: repeated calls reuse an
in-progress run, and a terminal run is returned during a 30 second cooldown. After the
cooldown a new run is started. The endpoint never resumes an explicitly disabled
portfolio, a removed membership, or a revoked attachment - those stay explicit
workflows.
Authorizations
Path Parameters
Meta WhatsApp Business Account ID.
Body
Meta Business Portfolio ID that owns the WABA. Digits only.
"823380597459265"
Response
Already funded, or no new run was started

