Choose the retirement workflow
Retire a messaging brand when the business no longer needs that registration. This stops using the existing registration; it does not register a replacement, release rented phone numbers or correct business identity details. For a correction, use Update a messaging brand.
The public brand DELETE call and the portal’s Delete brand action have different scope. The public call deletes one registry brand. The portal coordinates number detachment and campaign deactivation before it attempts the brand deletion.
| Workflow | What it does |
|---|---|
| Portal: Delete brand | Shows associated campaigns and assigned numbers, requires the brand ID as confirmation, then attempts the related cleanup before deleting the brand. Earlier steps can remain completed if a later step fails. |
| API: DELETE /tcr/v2/brand/{brandId} | Requests deletion of this account-owned brand only. It does not automatically detach numbers or deactivate the brand’s campaigns. An active campaign can prevent deletion. |
Review the impact in the portal
Open the messaging registration page, find the correct brand and choose Delete brand. Review the associated campaign and assigned-number counts. Type the exact brand ID to enable the final action. The customer form is available only when the account has registration-management permission.
The portal processes active campaigns in sequence: it attempts to detach each currently assigned number, deactivates the campaign, and then deletes the brand. It skips another remote deletion for campaigns already marked expired or deleted. After those external steps succeed, it updates the local campaign and number records in a database transaction.
This sequence is not one atomic transaction across the registry, carrier and local records. A later failure cannot restore a number or campaign already changed externally. Keep the returned detached-number and deactivated-campaign details when available; reconcile those identifiers instead of creating another brand.
Prepare a direct API deletion
Use an enabled API account over HTTPS from a permitted source IP address. The brand must belong to that account. Read and retain its ID and current state, then check its campaigns and number assignments. Detach affected numbers and deactivate campaigns before deleting the brand. Do not treat this DELETE as a cascade operation.
curl --silent --show-error --fail-with-body --user "$API_USER:$API_PASSWORD" \
"https://api.multitel.net/tcr/v2/brand/$BRAND_ID"Delete the reviewed brand
Execute the following only for the intended retirement, after checking the brand ID and completing the preceding cleanup. There is no request JSON body.
curl --silent --show-error --fail-with-body --user "$API_USER:$API_PASSWORD" \
--request DELETE \
--header "Idempotency-Key: $IDEMPOTENCY_KEY" \
"https://api.multitel.net/tcr/v2/brand/$BRAND_ID"The documented successful result is HTTP 204 with no response body. Do not require a JSON success object or the legacy v3 status/response envelope. A rejected non-2xx result does not mark the brand deleted through the current API synchronization path.
Use one idempotency key for the intended request. Keep the method, path, query and body bytes unchanged on a replay. The key does not make the wider portal cleanup atomic and does not prove that a carrier number was detached. An in-progress duplicate can return 409 with Retry-After; completed requests can replay their saved response, including an error.
Verify retirement and reconcile partial results
Check the portal’s brand and campaign lists and the affected numbers after the operation. The public API’s success synchronization marks the individual brand deleted locally; it does not remove the other campaign resources or clear purchased-number assignments. Registry status, carrier assignment and the local display are separate checks.
The current portal carrier adapter accepts an HTTP success response without separately validating every business-status value in its body. For that reason, verify the affected numbers’ actual campaign assignments after a portal cleanup, even if the portal reported success. If an assignment or status is inconsistent, retain the affected IDs and contact support before sending through or recreating the retired setup.
For HTTP 400, read the detailed registry error, especially an active-campaign restriction. For 401, 403 or 404, check credentials, permitted source IP and account ownership. For 429, honor Retry-After. A timeout, 500 or 502 can follow a completed external change; inspect the existing registration before repeating the request.
Check the remaining account charges
The current DELETE service does not dispatch an immediate brand-registration debit. Deleting a brand does not release the rented phone numbers, issue a refund or establish the final account balance. Review any existing campaign commitments, number rental and usage charges in the portal. This operation is not a quote for those separate services.