KYC

Download subaccount identity file

GET/v1/verifier/subaccount/file

Downloads an identity verification file (document image or selfie) for a specific subaccount. The response is the raw binary file.

Authorization

ApiKeyAuth

X-Api-Key<token>

For accessing these endpoints a valid API key must be sent in the X-Api-Key header.

In: header

Query Parameters

identityFileType*string

Type of identity file to download.

Value in

"backDocument"
"frontDocument"
"selfie"
"livenessFrontDocument"
"livenessBackDocument"
"livenessSelfie"

subAccountId*string

Identifier of the subaccount.

Response Body

`application/octet-stream`

`application/json`

`application/json`

`application/json`

Download subaccount identity file

curl --request GET \  --url 'https://gateway.bit2me.com/v1/verifier/subaccount/file?identityFileType=backDocument&subAccountId=string'

null

Get account details GET

Returns account details for the authenticated user. Personal data (name, surname, email, phone) is returned masked for privacy. The response includes the user's profile settings, verification state, company data (for business accounts), knowledge level and onboarding status. The gateway injects the authenticated user's identity; the caller does not send it.

Find blockchain addresses GET

Returns the list of blockchain deposit addresses associated with a wallet pocket on the specified network. These are the addresses generated by the platform for the user to receive funds, not the external addresses registered in the address book. Both `network` and `walletPocketId` are required, and the pocket must belong to the authenticated user. An empty array means the pocket has no address ready on that network; request one with `POST /v1/blockchain-manager/address`.