List available registration uploads

List available upload references

Use this endpoint after uploading registration documents when you need to find references that are still available for attachment. Use an enabled MultiTEL API account over HTTPS with its configured credentials and IP restrictions. The list is scoped to your account.

curl --silent --show-error --user "$API_USER:$API_PASSWORD" \
  https://api.multitel.net/v3/get_encrypted_files

No request body or query parameters are required. The handler lists API-created upload rows whose expired flag is clear and whose expiration time is later than the server's current time. It exposes no pagination, search or sort parameters. It is not a list of all identities, proofs or historical documents on your account.

Read metadata, not document bytes

Read the HTTP result and the JSON status.code. A successful response has an array in response; an empty result is an empty array, not a missing-account error. The example uses fictional metadata and identifiers.

{
  "status": {"code": 200, "msg": ""},
  "response": [{
    "id": "0123456789abcdef0123456789abcdef",
    "proof_type": "abcdef0123456789abcdef0123456789",
    "entity_type": "addresses",
    "description": "Example address proof",
    "file_name": "example-document.pdf",
    "date": "2026-10-01 12:00:00"
  }]
}

Upload metadata fields
Field	Meaning
`id`	The external upload reference. Copy it exactly for the relevant attachment request. Do not calculate an identifier yourself or substitute an identity, address or template ID.
`proof_type`	The masked recorded type reference when present, otherwise an empty string. For proof uploads this is the proof type; supporting-document uploads record their template reference under this same key. Read entity_type to distinguish them. It is not the upload ID.
`entity_type`	The recorded attachment category, such as identities, addresses or supporting_documents. Choose the matching attachment workflow.
`description`	The stored upload description.
`file_name`	The original filename. This is not a download URL.
`date`	The recorded creation time, formatted by the server without a time-zone offset.

The response contains no document bytes, storage URL or expiration deadline. Keep expired_at from the original upload response. Listing an upload does not extend its validity, attach it to an identity or prove that a carrier has approved it.

Attach before the reference expires

Use the appropriate proof attachment or supporting-document attachment workflow. The current upload workflow gives references a short validity window; do not delay attachment merely because a reference appeared in this list. A reference may expire or become unavailable between listing and attachment. Handle the attachment response rather than assuming success.

If the list is unexpectedly empty, check the account and whether the upload has expired or was created through another workflow. Do not automatically upload the same documents again without checking the original upload and attachment results.

Privacy

Filenames and descriptions can identify people or documents even though the file contents are absent. Limit access and avoid logging whole responses. To remove an unused local upload reference, see remove an upload reference; that operation is not a comprehensive document-erasure service.