Choose an unused upload reference
This endpoint removes an upload-reference record belonging to your account. Use it only when you are sure the reference is no longer needed for proof attachment or supporting-document attachment. It does not delete a registration identity or address.
Obtain the external file ID from the original upload response or available-upload list. The handler first looks up that ID for your account, with a legacy provider-ID fallback. New integrations should use the external reference exactly as returned. No request body is required.
Request removal deliberately
Use an enabled MultiTEL API account over HTTPS with its configured credentials and IP restrictions. Use POST so your application treats this as a deliberate change:
curl --silent --show-error --request POST \
--user "$API_USER:$API_PASSWORD" \
https://api.multitel.net/v3/delete_encrypted_file/0123456789abcdef0123456789abcdefThe current handler does not enforce an HTTP-method restriction: a GET request can also reach deletion. Do not expose this URL as a normal clickable link, image, bookmark, preview or prefetch target. Require an explicit removal action in your application, and do not retry automatically.
Interpret the result and its limits
Read both the HTTP result and the JSON status.code. The normal successful response is:
{
"status": {"code": 200, "msg": "Success"},
"response": []
}API code 404 with Failed, Not found means that neither lookup found a matching reference for this account. A repeated removal may therefore return 404. Leading and trailing spaces in the path value are trimmed. There is no check here that the reference is unexpired or unused by another step, so confirm your workflow before removing it.
The handler reports success after attempting the database deletion without checking whether that deletion succeeded. Treat the response as the reported result, not independent proof of erasure. If an unexpired API-created reference was visible in get_encrypted_files, that list can help check whether it remains visible, but absence from the list can also mean expiration.
Removal is not complete data erasure
The handler issues a deletion against the upload-reference table. It does not explicitly delete the stored document-content row, local uploaded file, attached proof, identity, supporting document or provider-held copy. Database cascading and retention behavior have not been verified. Do not present this operation to users as deleting all copies of their identity document or satisfying a comprehensive erasure request.
Once the local reference is removed, later attachment steps that need it may fail. Keep already-completed attachment results and use the relevant identity or proof management workflow when changing submitted registration information.