HitBTC · Schema
Subaccount created
The result of the subaccount creation. Every field is known at the creation time, therefore all of them are always present.
CompanyCryptocurrencyCryptocurrency ExchangeTradingMarket DataFuturesWallets
Properties
| Name | Type | Description |
|---|---|---|
| sub_account_id | string | Subaccount external identifier. |
| string | User email address. | |
| status | string | Account status. After the creation it is always `"new"`. Values: * `new`—account is created, but not confirmed by email; * `active`—account is fully functioning (it is normally accomplished after emai |
| sub_account_status | string | The lifecycle status of the subaccount itself, not of its holder. After the creation it is always `"invited"`. Values: * `invited`—the subaccount is created, the invitation has not been accepted yet; |
| created_at | string | Date and time of the creation. |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://raw.githubusercontent.com/api-evangelist/hitbtc/main/json-schema/hitbtc-wallet-subaccount-created-schema.json",
"title": "Subaccount created",
"description": "The result of the subaccount creation. Every field is known at the creation time, therefore all of them are always present.\n",
"x-generated": "2026-10-13",
"x-method": "derived",
"x-generator": "derive-json-schema.py",
"x-source": "openapi/hitbtc-openapi.yml#/components/schemas/wallet_SubaccountCreated",
"required": [
"sub_account_id",
"email",
"status",
"sub_account_status",
"created_at"
],
"type": "object",
"properties": {
"sub_account_id": {
"type": "string",
"description": "Subaccount external identifier."
},
"email": {
"type": "string",
"format": "email",
"description": "User email address."
},
"status": {
"type": "string",
"enum": [
"new",
"active",
"disable"
],
"description": "Account status. After the creation it is always `\"new\"`.\n\nValues:\n * `new`—account is created, but not confirmed by email;\n * `active`—account is fully functioning (it is normally accomplished after email confirmation);\n * `disable`—account is disabled (the user cannot initiate account deactivation — it can only be done by the CRM operator).\n"
},
"sub_account_status": {
"type": "string",
"enum": [
"invited",
"active",
"frozen",
"frozen_invited"
],
"description": "The lifecycle status of the subaccount itself, not of its holder. After the creation it is always `\"invited\"`.\n\nValues:\n * `invited`—the subaccount is created, the invitation has not been accepted yet;\n * `active`—the subaccount is active, the transition happens on its first sign-in;\n * `frozen`—the subaccount is frozen by the super account;\n * `frozen_invited`—the subaccount is frozen before the invitation was accepted.\n"
},
"created_at": {
"type": "string",
"description": "Date and time of the creation."
}
}
}
Work with this as data
Every JSON Schema 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 schemas
4 MCP tools reach this
find_json_schemasBrowse and filter every JSON Schema in the catalog.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 JSON Schema
curl "https://apis.io/api/v1/json-schemas/hitbtc-wallet-subaccount-created"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
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.