Overview
Organizations
Accounts
Funding methods
Beneficiaries
Transactions
Authorizations
Import verification
Import a verification for the in-scope organization from a donor’s Sumsub share token (Reusable KYC).
Lets a broker reuse a KYC/KYB they already performed on their own
Sumsub tenant instead of asking the customer to repeat the flow. The
broker generates a single-use share token on their tenant and posts
it here under Nxos-On-Behalf-Of: <child-org-id>. We import the
applicant on our tenant under externalUserId = <child-org-id> and
move the verification record to PENDING. Sumsub’s applicant-review
webhook fires shortly after and the platform progresses the org to
APPROVED — poll GET /v1/organizations/verification to observe
that transition.
Pre-requisite: the donor must have added nxos as a Reusable KYC partner in their Sumsub dashboard, and we must have enabled the feature on our side. There is no automated onboarding for the pairing itself.
Share tokens are single-use. A retry of this endpoint with the same
token returns share_token_invalid.
See Verification for the full flow.
curl --request POST \
--url https://api.nxos.io/v1/organizations/verification/import \
--header 'Authorization: <authorization>' \
--header 'Content-Type: application/json' \
--data '
{
"shareToken": "<string>"
}
'{
"object": "organization_verification",
"status": "APPROVED",
"type": "BUSINESS",
"updatedAt": "2026-03-15T14:30:00.000Z"
}Documentation Index
Fetch the complete documentation index at: https://docs.nxos.io/llms.txt
Use this file to discover all available pages before exploring further.
Headers
Bearer token. Format: Bearer <api_key>
Unique key per logical operation. UUID v4 recommended. Max 255 characters.
Body
Request body for POST /v1/organizations/verification/import.
Single-use share token generated by the donor on their Sumsub tenant for a Reusable KYC partnership with nxos.
Response
The request has succeeded.
Verification record for an organization. Surfaces the live status plus a last-updated timestamp; polling this endpoint is the canonical way to learn when KYB completes.
Object type. Always organization_verification.
organization_verification Current verification status.
NOT_STARTED, PENDING, APPROVED, REJECTED, ON_HOLD, RESUBMISSION_REQUIRED Verification flow applied to the org.
BUSINESS, INDIVIDUAL ISO 8601 timestamp of the most recent status change.
curl --request POST \
--url https://api.nxos.io/v1/organizations/verification/import \
--header 'Authorization: <authorization>' \
--header 'Content-Type: application/json' \
--data '
{
"shareToken": "<string>"
}
'{
"object": "organization_verification",
"status": "APPROVED",
"type": "BUSINESS",
"updatedAt": "2026-03-15T14:30:00.000Z"
}