Remove a registration profile deliberately
This legacy operation attempts to delete the account-owned carrier identity and address, then marks the local profile deleted. Identify the correct local profile UUID with documents and review it in the portal before calling it. It is not a proof-only removal or an undo operation.
Destructive legacy request
Authenticate with your enabled MultiTEL API account from an allowed IP address. Examples use credentials in environment variables and fictional data. Read JSON status.code and status.msg as well as the HTTP response.
The current portal invokes this operation using GET. Despite the HTTP method, it changes data. Never use the URL in a link, image, health check, browser prefetch, crawler or automatic retry. Require an explicit user deletion decision in your integration.
curl --silent --show-error --user "$API_USER:$API_PASSWORD" \
"https://api.multitel.net/v3/delete_document/$DOCUMENT_UUID"DOCUMENT_UUID is the local profile identifier returned as uuid during creation or id during profile readback. It is not the identity ID, address ID or a phone number. No request body is used.
Reported result
{
"status": {
"code": 200,
"msg": "Success"
},
"response": []
}API code 404 with message Failed, Not found means the profile UUID was not found for this account. A reported 200 means the handler reached its completion response; it does not prove that the carrier deleted the identity/address or that the local database update succeeded.
Verify removal and its scope
The current handler does not check the results of carrier deletion or the local update. After a reported success, confirm that the profile is absent from active documents results and returns not found from get_document. Those checks establish local visibility only. They do not prove deletion at an upstream carrier.
This endpoint is not a general personal-data erasure API. It does not establish deletion of uploaded files, proofs, supporting documents, logs, backups or other retained records. For confirmed upstream removal or a data-erasure request, contact support. Do not repeatedly call deletion as a substitute for checking a partial outcome.