Import a verified session
Import a verification the customer already passed on the partner’s own Sumsub level, handed over as a share token. Prerequisites, and what does and doesn’t transfer: KYC Sumsub Shared Token.
Answers 200, not 202: the import is committed before the response, which carries the same requirements breakdown as GET /ramp/customer/{customer_id}/kyc?requirements=true.
Only shareToken is accepted. The verification level and the customer’s identity are ours to decide. The token is a credential; it is never logged and appears in no response.
No country is sent: it is read from the shared verification and used to route the customer. The customer’s registered user_info.email is set on the imported applicant, so the email step confirms that address rather than one the customer types in.
Nothing is trusted wholesale. Everything imported is re-checked against Etherfuse’s own requirements, so a session approved in the partner’s account is not automatically approved here.
Authorizations
API key sent in the Authorization header.
Path Parameters
The customer (child org) ID. Must belong to the caller's organization or a direct child.
Body
A verification session the partner already completed with the same provider, handed over as a share token they minted for us. No other field is accepted.
The single-use, short-lived share token minted for the verified applicant, targeting Etherfuse's client id.
"_act-sbx-jwt-eyJhbGciOi..."
Response
The session was imported. requirements describes what is still outstanding.
The outcome of importing a verification session.