List registration profiles

Find existing registration profiles

List the active, non-deleted local registration profiles associated with your API account. Use this to locate a profile UUID before opening it with get_document, not to determine whether its proofs or number registration were approved.

List request

Authenticate with your enabled MultiTEL API account and its allowed IP address. The examples use HTTP Basic credentials stored in environment variables. Check both the HTTP response and JSON status.code; an HTTP 200 response alone does not establish success. All example values are fictional.

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

No request body, pagination or filter parameters are implemented by this handler. It returns the matching account’s stored profiles; do not assume a particular ordering. Avoid frequent full-list polling for large accounts.

Response list

{
  "status": {
    "code": 200,
    "msg": ""
  },
  "response": [
    {
      "id": "11111111111111111111111111111111",
      "first_name": "Example",
      "last_name": "Person",
      "phone_number": "12025550123",
      "id_number": "",
      "birth_date": null,
      "company_name": "",
      "company_reg_number": "",
      "vat_id": "",
      "personal_tax_id": "",
      "description": "Example profile",
      "identity_type": "Personal",
      "postal_code": "00000",
      "city": "Example City",
      "address": "1 Example Street",
      "signature": "BASE64_PNG_SIGNATURE_DATA",
      "date_created": "2026-10-23 16:00:00"
    }
  ]
}

With no matching active profiles, the handler returns API code 200 and an empty response list. response[].id is the local profile UUID returned as uuid during creation; it is not an identity ID or address ID.

Returned profile fields

The projection contains id, first_name, last_name, phone_number, id_number, birth_date, company_name, company_reg_number, vat_id, personal_tax_id, description, identity_type, postal_code, city, address, signature and date_created.

Optional values may be empty or null according to stored data. This legacy projection omits email, country selectors, identity_id, address_id, uploaded-file references, proof lists and verification status. It is not a proof-status or registration-approval endpoint. Treat the returned identity, contact and signature data as private.

Next steps

Save entity IDs from the original create_document response for later attachments. If that response was lost, this list cannot recover them. Inspect the profile in the portal or contact support instead of automatically creating a duplicate.