Add a document to an investor

Uploads one document, with all of its files, for the investor itself. The body shape follows the investor’s type, chosen by type:

• Individual → an identity document (passport, driving-licence, national-identity-card, residence-permit). A passport is one file with side: front; the other three are two files, one front and one back, in the same call. The file is read optically, so it must be a real, legible image (JPEG or PNG).
• Entity → one of its own company documents (certificate of registration, articles, shareholder register…), filed for Securitize compliance review: exactly one file, PDF allowed, no side, documentNumber or expiresAt. Optional: the list of types is a menu, not a checklist — send what you hold. A company has no identity document of its own: send a person’s identity document to POST /investors/{investorId}/key-parties/{keyPartyId}/documents.

A company type on an individual, or an identity type on an entity, answers 422 before anything is stored.

Two ways to send the files, on this same route and with the same answers. As JSON, each file base64-encoded in files[].content, at most 10 MB a file. Or as multipart/form-data, each file as a part of its own, at most 20 MB a file: the text parts carry type, documentNumber and expiresAt, and the files go in a front part, plus a back part for a two-sided document, or in one file part for a company document. Send files over 10 MB as multipart; a part travels as the file itself, without the third that base64 adds. See Two ways to send the files.

This never starts verification. Read verification.status in the response:

• individual — awaiting_documents while something is still owed (missing names it, e.g. ["IDENTITY"]), then awaiting_submission once the identity document is accepted;
• entity — awaiting_key_parties while its key parties still need adding or documenting (missing, e.g. ["COMPANY_BENEFICIARIES"]), then awaiting_submission.

awaiting_submission is not a stuck state: it is waiting for your POST /investors/{investorId}/verification/submit. No verdict arrives from this endpoint, and the investor’s status stays none.

The status code is the outcome; there is no per-file result. A two-sided document is stored only if both sides are accepted. Each call stores a new document, so sending the same document twice keeps two copies. Once the investor is submitted, this route answers 409. For sandbox tests you can use the sample files at /secid-api/fixtures/passport.png and /secid-api/fixtures/company-document.png on this site.