Skip to main content
POST
Onboard entity
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

application/json

The onboard entity attributes

Onboard parameters for creating entity

business_infos
V2 onboarding entity business information parameters · object
required

Onboard business information parameters for creating entity

Example:

Onboard consent parameters for creating entity

Example:
name
string
required

Name of the Entity

representatives
Onboarding entity representative parameters · object[]
required
tax_number
string
required

Tax number of the Entity

external_id
string

External ID of the Entity

Response

Compliance

Entity onboard response

data
V2 entity onboard data · object

The entity as Trio registered it to onboard, with the fields of the onboarding request under the same names

Example: