waba_id in both routes is the source Meta WABA ID. Kapso selects the destination solution from your project. Meta creates a destination WABA for the number.
Move a number from another solution
-
From your backend, create an intent with Meta’s Set solution migration intent API. Call
POST /{source_waba_id}/set_solution_migration_intentwith your source business token and the destination Metasolution_id. Save the returned ID. -
Register the intent with Kapso before the business removes access to the source account. Send this body to
POST /platform/v1/whatsapp/accounts/{waba_id}/partner_solution_migrations.Keep the token on your backend. Kapso uses it to verify the source account, intent, and number, then discards it. You can omit it if Kapso already has an eligible source connection in your project. For Kapso infrastructure, also send the destination Kapsocustomer_id. - When the business is ready for cutover, have its admin complete Meta’s authorization steps in Business settings → Requests → Received. After Meta accepts the intent, Kapso verifies the destination owner and billing before moving the number.
-
Poll the migration. With Kapso infrastructure, Kapso verifies messaging access for the selected Meta app before cutover and completes the connection. With Your infrastructure, wait for
awaiting_tech_provider. Use the returnedphone_number_idto call Meta’sPOST /{phone_number_id}/register, then subscribe your app withPOST /{destination_waba_id}/subscribed_appsand test sending and receiving from your backend.
Meta copies eligible templates to the new WABA. Check the templates you use before sending. Plan the cutover with the business.
Check migration status
migration_id throughout the operation. Resubmit the same Meta intent with the same inputs to recover the operation ID. Reusing a Meta intent with different inputs returns 409.
For other statuses, keep polling. If Meta’s response to the number move is unclear, Kapso checks the destination for the number before asking for support.

