Skip to content

Connecting extra numbers

Disconnect an extra number that is already paired to stop using it for a while, and reconnect it whenever you want to come back, without pairing again. Disconnected numbers stay registered in the account, but cannot be used as a sender. For the first link to WhatsApp, see pairing in the dashboard or through the API.

Billing

Disconnected extra numbers keep being charged while they are registered. To stop the charge, you need to remove the number. See the details in Extra number billing.

In the dashboard

Open the Numbers (opens in a new tab) page in the dashboard to disconnect or reconnect numbers with one click.

Reconnect

To reconnect a disconnected extra number, make a POST request to the connect endpoint with the number’s alias in the URL.

turbo-notify.sh
curl -X POST \
https://api.turbonotify.com/v1/numbers/NUMBER_ALIAS/connect \
-H "Authorization: Bearer YOUR_KEY"
HTTP status: 202
{
  "alias": "vendas_sp",
  "status": "connecting",
  "at": "2026-06-01T12:40:00Z"
}

The response (202 Accepted) only confirms that the request was accepted: status is connecting and at is the moment the request was accepted. The number connects a few seconds later. The final status (connected or failed) arrives through the number.connected / number.connect.failed webhook, or by checking Extra number status, which stays the source of the number’s current status and of its own at.

Disconnect

To disconnect a connected extra number, make a POST request to the disconnect endpoint with the number’s alias in the URL.

turbo-notify.sh
curl -X POST \
https://api.turbonotify.com/v1/numbers/NUMBER_ALIAS/disconnect \
-H "Authorization: Bearer YOUR_KEY"
HTTP status: 202
{
  "alias": "vendas_sp",
  "status": "disconnecting",
  "at": "2026-06-01T12:40:00Z"
}

disconnecting appears only in this response (202 Accepted), as a confirmation that the request was accepted, and at is the moment it was accepted. Unlike connecting, disconnecting is not one of the values in the Status table and does not appear in GET /v1/numbers/{ref} (which, right after this call, still shows the previous status and its own at until Turbo Notify finishes disconnecting). The final status (disconnected) arrives through the number.disconnected webhook, or by checking Extra number status.

Possible errors

Reconnect (POST /v1/numbers/{ref}/connect)

StatusError codeDescription
402subscription_inactiveThe organization’s subscription is past_due, terminated, pending or its trial period has expired (the response includes details.status).
402feature_not_availableThe current plan does not support extra numbers.
403no_device_linkThe extra number has no active link to WhatsApp (inconsistent state).
403extra_number_not_pairedThe extra number has not finished pairing. Call POST /v1/numbers/{ref}/pair first.
404number_not_foundThe alias or id does not match any registered number.
409already_connectedThe extra number is already connected.
409already_connectingA connection attempt is already in progress.
500internal_errorUnexpected internal server error.

Disconnect (POST /v1/numbers/{ref}/disconnect)

StatusError codeDescription
402feature_not_availableThe current plan does not support extra numbers.
404number_not_foundThe alias or id does not match any registered number.
409already_disconnectedThe extra number is already disconnected (nothing to do).
500internal_errorUnexpected internal server error.

Both routes also return 401 not_authenticated (invalid or missing key) and 403 insufficient_scope (missing the numbers:write scope, the response includes required_scope) like any other authenticated endpoint.