BigONE · Schema

Deposit

Deposit record details.

CompanyCryptocurrencyExchangeTradingDerivativesWalletsMarket Data

Properties

Name Type Description
id integer The unique deposit ID.
amount string The deposit amount.
confirms integer The number of blockchain confirmations received.
txid stringnull The blockchain transaction ID. Null for internal transfers.
is_internal boolean Whether this is an internal transfer (from another BigONE user).
inserted_at string The timestamp when the deposit was recorded (ISO 8601).
updated_at string The timestamp when the deposit was last updated (ISO 8601).
kind string The deposit type (e.g., "on_chain", "internal", "off_chain").
memo stringnull The memo or tag associated with the deposit (if applicable).
state string The current deposit state.
asset_symbol string The asset symbol (e.g., BTC, EOS).
target_account string The account that received the deposit.
View JSON Schema on GitHub

JSON Schema

bigone-deposit-schema.json Raw ↑
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "https://raw.githubusercontent.com/api-evangelist/bigone/main/json-schema/bigone-deposit-schema.json",
  "title": "Deposit",
  "description": "Deposit record details.",
  "x-generated": "2026-10-13",
  "x-method": "derived",
  "x-generator": "derive-json-schema.py",
  "x-source": "openapi/bigone-wallet-openapi.yml#/components/schemas/Deposit",
  "type": "object",
  "properties": {
    "id": {
      "type": "integer",
      "description": "The unique deposit ID.",
      "format": "int64"
    },
    "amount": {
      "type": "string",
      "description": "The deposit amount."
    },
    "confirms": {
      "type": "integer",
      "description": "The number of blockchain confirmations received.",
      "format": "int64"
    },
    "txid": {
      "type": [
        "string",
        "null"
      ],
      "description": "The blockchain transaction ID. Null for internal transfers."
    },
    "is_internal": {
      "type": "boolean",
      "description": "Whether this is an internal transfer (from another BigONE user)."
    },
    "inserted_at": {
      "type": "string",
      "description": "The timestamp when the deposit was recorded (ISO 8601).",
      "format": "date-time"
    },
    "updated_at": {
      "type": "string",
      "description": "The timestamp when the deposit was last updated (ISO 8601).",
      "format": "date-time"
    },
    "kind": {
      "type": "string",
      "description": "The deposit type (e.g., \"on_chain\", \"internal\", \"off_chain\")."
    },
    "memo": {
      "type": [
        "string",
        "null"
      ],
      "description": "The memo or tag associated with the deposit (if applicable)."
    },
    "state": {
      "type": "string",
      "description": "The current deposit state.",
      "enum": [
        "PENDING",
        "WITHHOLD",
        "CANCELLED",
        "COMPLETED"
      ]
    },
    "asset_symbol": {
      "type": "string",
      "description": "The asset symbol (e.g., BTC, EOS)."
    },
    "target_account": {
      "type": "string",
      "enum": [
        "SPOT",
        "FUND"
      ],
      "description": "The account that received the deposit."
    }
  }
}

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.
All 92 tools →

Call it yourself

curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/bigone-deposit"
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.