Attach a supporting document

Attach a template-based supporting document

Use a template from get_supporting_document_templates and an identity already owned by your account. Upload its files through create_encrypt_files using supporting_template_id. Ordinary identity/address proof uploads are a different category and cannot be substituted.

Create the supporting document

Use an enabled MultiTEL API account and its permitted IP address. The examples use HTTP Basic credentials from environment variables; follow the authentication conventions for your account type. Send requests over HTTPS. Check both the HTTP response and the JSON status.code; application errors can arrive with HTTP 200. Examples below are fictional.

curl --silent --show-error --user "$API_USER:$API_PASSWORD" \
  --header 'Content-Type: application/json' \
  --data @supporting-request.json \
  https://api.multitel.net/v3/create_supporting_document

{
  "identity_id": "33333333333333333333333333333333",
  "template_id": "55555555555555555555555555555555",
  "encrypted_file_ids": [
    "66666666666666666666666666666666"
  ]
}

Request fields
Field	Meaning
`identity_id`	Required ID of the identity associated with your account. This request attaches to an identity, not directly to an address or telephone number.
`template_id`	Required supporting-document template ID; use the same selected template as the supporting upload. The attachment field is template_id, while the upload field is supporting_template_id.
`encrypted_file_ids`	Required nonempty JSON array of returned upload IDs. Each must belong to the current account, be unexpired and have the supporting_documents category.

Form data with repeated encrypted_file_ids[] fields is also accepted. Do not send file bytes to this attachment endpoint.

Created supporting document

{
  "status": {
    "code": 200,
    "msg": "Supporting document created successfully."
  },
  "response": {
    "id": "77777777777777777777777777777777",
    "template_id": "55555555555555555555555555555555",
    "identity_id": "33333333333333333333333333333333",
    "template_name": "Example supporting template"
  }
}

This confirms the supporting-document creation, not regulatory approval or number activation. The term permanent in the upstream resource is not a customer-facing guarantee about storage duration or deletion policy.

Errors and retries

API code 500 represents missing inputs, carrier errors or an invalid carrier response. Code 404 represents an identity not associated with the account, an invalid template, missing/expired/wrong-category uploads or an empty usable file set. Check status.msg; HTTP 200 alone is insufficient.

Upload and attach within the returned file-reference validity window. After an uncertain response, check the identity’s supporting documents in the portal before retrying. No idempotency key is exposed by this handler.