15 September 2026

Delete a number, close a workspace

New feature. The developer console can now remove what it creates. Each connection row on Billing has a Delete button, and a workspace with no connections left can be closed from the same card.

Deleting a number closes its WhatsApp session, removes every message stored for it, and returns its slot to the workspace pool if it was on a paid one. Closing a workspace removes it together with its API keys and webhook configuration, so anything still calling the API with those keys stops working. Both actions ask for confirmation and neither can be undone.

Two refusals are deliberate. A workspace that still has numbers cannot be closed — delete them first, so the phones are actually unlinked instead of leaving orphaned sessions behind. A workspace with a live slot subscription cannot be closed either; cancel the subscription first, or it keeps billing a workspace that no longer exists.

The same actions are available over the API: DELETE /v1/connections/{id} with a key carrying the whatsapp.manage scope.

What survives on purpose: the record that a number already had its free trial. Closing a workspace and opening another does not hand the same phone a second trial.

Click-to-WhatsApp attribution retries the CRM write

Fix. Bitrix24 lists a freshly created deal seconds before it will answer a write for that same id, replying 400 Not found in between. Ad attribution written in that window was lost, leaving the contact attributed and the deal with empty UTM fields. Each write is now retried, and a write that still fails raises an alert on our side instead of failing quietly.