400
with an errors array that names the failing field and error code.
For upload steps, see
Upload documents.
Read limits from the schema
Each file field can set its own types and size. Retrieve the application schema (GET /v1/onboarding/partner/applications/{applicationId}/schema) and read
x-fileUpload on the target field:
x-fileUpload is absent, the API uses the defaults in the following tables.
Filename
The API strips/ and \ from fileName, then trims spaces at each end.
Quotes, slashes, and other punctuation fail the character check.
File type
The API reads magic bytes infileContent. It doesn’t trust the Content-Type
header.
Known signatures are PDF, JPEG, PNG, ZIP (Office Open XML), and OLE2 (legacy
Office). A file with no matching signature returns unrecognized_type.
Office files (DOC, XLS, DOCX, XLSX) pass only when the field schema lists those
types. The default list doesn’t include them.
File size
A file over the limit returns
too_large.
Error codes
A failed check returns HTTP400 with numeric code 181102. The body includes
errors with field and code.