Skip to main content
POST
Upload onboarding document
IMPORTANT: This feature is only available after a distribution channel has been created for your organization.To request the creation of a distribution channel, contact Trio Support or your Trio Account Manager.

Authorizations

Authorization
string
header
required

Basic authentication header of the form Basic <encoded-value>, where <encoded-value> is the base64-encoded string username:password.

Headers

Trio-Version
enum<string>
required

Version of the v2 contract the client is written against. Each breaking change publishes a new version.

Available options:
2026-10-19.v2
Trio-Target-Org-Id
string<uuid>

ID of another org to act on instead of the API key's own org. The key's org must have been granted access to it, and the request is refused with 403 FORBIDDEN otherwise. When that access or the API key is read-only, only GET and HEAD requests may carry it. When the target org requires mTLS, so does the request. Leave it out to act on the key's own org.

Body

multipart/form-data

Document parameters and binary file

Multipart form params to upload an onboarding document

document_type
enum<string>
required

Document type, among the required_documents the onboarding asked for

Available options:
power_of_attorney,
financial_statement,
identification,
company_contract
file
file
required

The PDF file

reference_id
string<uuid>
required

The entity_id, or the representative id, the POST /v2/onboarding response published

reference_type
enum<string>
required

Whether the document is the entity's or a representative's

Available options:
entity,
entity_representative

Response

Document uploaded successfully

The onboarding document uploaded

data
object
required