Bit2Me Verifier API
The Verifier API from Bit2Me — 2 operation(s) for verifier.
Work with this as data
Every API here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for apis
7 MCP tools reach this
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This API
curl "https://apis.io/api/v1/apis/bit2me:bit2me-verifier-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.
OpenAPI Specification
openapi: 3.2.0
info:
title: Bit2Me API Gateway Verifier API
version: 2.0.0
tags:
- name: Verifier
paths:
/v1/account/verify/identity:
get:
description: 'Returns the current status of the identity verification process for the
authenticated user, including document images, KYC express status, risk level,
extra measures, and tier information.'
responses:
'200':
content:
application/json:
example:
countryFormRequired: false
disableProcess: false
error: []
extraMeasurePending: false
image: []
questions: true
risk:
action: accepted
level: medium
status: verified
tier: 2
verified:
- questions
- identity
- email
- phone
schema:
properties:
countryFormRequired:
type: boolean
disableProcess:
type: boolean
duplicatedAccountEmail:
description: Obfuscated email of the account that already owns the duplicated identity document. Only present when the identity error field (`error`) includes the value `number` (see ErrorsParam).
example: mai***@gmail.com
type: string
error:
items:
enum:
- number
- expiryDate
- noDocUploaded
- imageDoc
- imageSelfie
- other
- unacceptableRisk
- underAge
- fraud
- unsupportedIdType
- noNationality
- idCountryDiffersResidenceCountry
- unsupportedIdTypeResidenceCountry
- enhancedMeasuresNotReceived
- pibisi
- kycUpdateRequired
- overAge
- docDamaged
- livenessCopy
- docMissingImage
- livenessFraud
type: string
type: array
extraMeasurePending:
type: boolean
extraMeasuresNotApproved:
properties:
compliance:
items:
enum:
- MR2
type: string
type: array
required:
- compliance
type: object
image:
items:
enum:
- document
- selfie
type: string
type: array
kycExpress:
properties:
status:
enum:
- success
- rejected
- uncompleted
type: string
updatedAt:
format: date
type: string
type: object
questions:
type: boolean
risk:
properties:
action:
maxLength: 120
type: string
level:
enum:
- undefined
- low
- medium
- mediumHigh
- high
- unacceptable
type: string
maxPoints:
maximum: 10
minimum: 0
type: integer
minPoints:
maximum: 10
minimum: 0
type: integer
required:
- level
type: object
status:
enum:
- nodata
- pending
- verified
- error
type: string
subStatus:
enum:
- pending
- waitingId
- waitingUser
type: string
tier:
type: number
verified:
items:
enum:
- email
- phone
- identity
- questions
- form
- admin
- operator
- support
- support-lead
- support-light
- marketing
- accounting
- compliance
- compliance-light
- sales
- trading
- viewer
- listings
- api
type: string
type: array
required:
- status
- image
- disableProcess
type: object
description: Identity verification status.
'403':
content:
application/json:
example:
code: 403
description: invalid credentials
schema:
description: 'Returned with `403` when the request is rejected before being processed at all: the API key,
the signature or the nonce could not be validated. It is deliberately vague about which one
failed.
Note the status is `403` and not `401`, and that this envelope shares no field with any other
error shape in the API.
'
properties:
code:
description: Repeats the HTTP status code.
enum:
- 403
example: 403
type: integer
description:
description: Fixed message; it never carries detail about the specific failure.
example: invalid credentials
type: string
required:
- code
- description
type: object
description: Invalid credentials.
default:
content:
application/json:
schema:
properties:
data:
type: object
error:
type: string
message:
type: string
reqId:
type: string
statusCode:
type: number
required:
- message
- error
type: object
description: Unexpected error.
security:
- JwtAuth: []
- ApiKeyAuth: []
summary: Get identity verification status
tags:
- Verifier
x-product:
wallet: Account
operationId: getV1AccountVerifyIdentity
x-operation-id-source: derived
/v1/verifier/subaccount/file:
get:
description: 'Downloads an identity verification file (document image or selfie) for a
specific subaccount. The response is the raw binary file.'
parameters:
- description: Type of identity file to download.
in: query
name: identityFileType
required: true
schema:
enum:
- backDocument
- frontDocument
- selfie
- livenessFrontDocument
- livenessBackDocument
- livenessSelfie
type: string
- description: Identifier of the subaccount.
in: query
name: subAccountId
required: true
schema:
type: string
responses:
'200':
content:
application/octet-stream:
schema:
format: binary
type: string
description: The identity file binary content.
'403':
content:
application/json:
schema:
properties:
data:
type: object
error:
type: string
message:
type: string
reqId:
type: string
statusCode:
type: number
required:
- message
- error
type: object
description: Invalid credentials or user not authorized.
'404':
content:
application/json:
schema:
properties:
data:
type: object
error:
type: string
message:
type: string
reqId:
type: string
statusCode:
type: number
required:
- message
- error
type: object
description: User or file not found.
default:
content:
application/json:
schema:
properties:
data:
type: object
error:
type: string
message:
type: string
reqId:
type: string
statusCode:
type: number
required:
- message
- error
type: object
description: Unexpected error.
security:
- JwtAuth: []
- ApiKeyAuth: []
summary: Download subaccount identity file
tags:
- Verifier
x-product:
wallet: KYC
operationId: getV1VerifierSubaccountFile
x-operation-id-source: derived
components:
securitySchemes:
ApiKeyAuth:
description: 'For accessing these endpoints a valid API key must be sent in the *X-Api-Key* header.
'
in: header
name: X-Api-Key
type: apiKey
BasicAuth:
description: "Access control to the API is always controlled by a JWT token. To get this token you must log in through */v3/signin* (email and password).\n\nThe client sends requests with the Authorization header that contains the Basic word followed by a space and a base64-encoded username:password string.\nExample:\n Authorization: Basic ZGVtbzpwQDU1dzByZA==\n"
in: header
name: Authorization
type: apiKey
CustomApiKey:
description: 'For accessing a specific API endpoint of this type, a valid API key must be passed in the *Authorization* header.
'
in: header
name: Authorization
type: apiKey
JwtAuth:
description: "For accessing the API a valid JWT token must be passed in the *Authorization* header.\n\nA valid JWT token is generated by the API and returned after calling */v1/signin* with valid credentials.\n\nExample:\n Authorization: Bearer xxxxxx.yyyyyyy.zzzzzz\n"
in: header
name: Authorization
type: apiKey
JwtPreAuth:
description: "The pre-auth token proves the password only, while a sign-in waits for its second step. It is the\n*accessToken* returned with *sfa: true* by *POST /v4/signin* or *POST /v2/signin/oauth/{provider}*.\nSend it in the *Authorization* header as a Bearer token.\n\nIt is accepted only by these routes:\n - *POST /v1/auth/two-step-verification/initiate*\n - *POST /v1/auth/two-step-verification/reissue*\n - *POST /v1/auth/two-step-verification/verify*\n - *POST /v4/signin/sfa*\n\nsuite-auth verifies the token on every call (it is never cached). A refused token is answered with 403.\n\nExample:\n Authorization: Bearer xxxxxx.yyyyyyy.zzzzzz\n"
in: header
name: Authorization
type: apiKey
x-tagGroups:
- name: Basic Info
tags:
- Crypto Suite
- name: Crypto Suite Endpoints
tags:
- Account
- Accounting
- Affiliates
- Auth
- Blockchain Manager
- Brokerage
- Captcha
- Card
- Card Authorizator
- Card Loyalty
- Collection Orders
- Commerce
- Compliance
- Configuration
- Crypto Credentials
- Currency
- Currency Analytics
- Currency Collections
- Currency Favorites
- Earn
- External Onboarding
- Instant
- Junior
- Launchpad
- Loan
- Misc
- Notification
- Portfolio
- Portfolio Analytics
- Price Alert Scheduler
- Price Orders
- Price Watchdog
- Promotion
- Recurring Orders
- Pay
- Redeem Token
- Space Center
- Stocks
- Support
- Taxes
- Teller
- Terms and Conditions
- Travel Rule
- Trading
- Translations
- UX
- Verifier
- Wallet
- name: Deprecated
tags:
- Account Deprecated Methods
- Auth Deprecated Methods
- Currency Deprecated Methods
- Earn Deprecated Methods
- Verifier Deprecated Methods