feat(api): update API v2 field descriptions by laviniat1996 · Pull Request #1469 · ton-org/docs

laviniat1996 · 2025-11-28T03:29:27Z

github-actions · 2025-11-28T03:29:42Z

Skipping AI review because no docs changes in md, mdx, or docs.json

reveloper · 2025-12-04T07:15:39Z

ecosystem/api/toncenter/v2.json

        ],
+        "summary": "JSON-RPC endpoint",
+        "description": "All API methods are available through this single endpoint using JSON-RPC 2.0 protocol. Send the method name in the `method` field and parameters as a dictionary in `params`. Useful when you need to call multiple methods in sequence or prefer JSON-RPC over REST.",


Authorizations description shouldn't be empty:

Example of a good definition:

reveloper · 2025-12-04T07:45:38Z

ecosystem/api/toncenter/v2.json

+        "summary": "JSON-RPC endpoint",
+        "description": "All API methods are available through this single endpoint using JSON-RPC 2.0 protocol. Send the method name in the `method` field and parameters as a dictionary in `params`. Useful when you need to call multiple methods in sequence or prefer JSON-RPC over REST.",
+        "operationId": "jsonRPC_post",
+        "requestBody": {


https://companyname-a7d5b98e-fields.mintlify.app/ecosystem/api/toncenter/v2/rpc/json-rpc-endpoint

Result field seems strange and broken:

Does it really have two options?

This was all messed up. Basically any method can be sent as JSON RPC request. And the json file had all responses for all methods as a dropdown list in there, which is not ok

reveloper · 2025-12-04T08:05:20Z

ecosystem/api/toncenter/v2.json

        ],
+        "summary": "Detect address",


The field definition is wrong, which works from ANY form of TON Address:

example:

curl --request POST \ --url https://toncenter.com/api/v2/detectAddress \ --header 'Content-Type: application/json' \ --header 'X-API-Key: <api-key>' \ --data ' { "address": "0:c78b3eb54a55243d4efe411f0bb0101a8da61904a89c48212f81ff32006b2dc1" }

https://companyname-a7d5b98e-fields.mintlify.app/ecosystem/api/toncenter/v2/rpc/detect-address

reveloper · 2025-12-04T08:27:10Z

ecosystem/api/toncenter/v2.json

+        "summary": "Detect address",
+        "description": "Validates an address and returns it in all standard formats. Use this to convert between address formats or to validate user input. Returns raw format (0:abc...), base64 bounceable (EQ...), base64 non-bounceable (UQ...), and URL-safe variants.",
+        "operationId": "detectAddress_post",
+        "requestBody": {


Let's find a more detailed explanation of this field for devs. Even if this is not for external use, it should be documented clearly:

https://companyname-a7d5b98e-fields.mintlify.app/ecosystem/api/toncenter/v2/rpc/detect-address

reveloper · 2025-12-04T08:45:42Z

ecosystem/api/toncenter/v2.json

-        "description": "Similar to previous one but tries to parse additional information for known contract types. This method is based on tonlib's function *getAccountState*. For detecting wallets we recommend to use *getWalletInformation*.",
-        "operationId": "get_extended_address_information_getExtendedAddressInformation_get",
+        "summary": "Detect address",
+        "description": "Validates an address and returns it in all standard formats. Use this to convert between address formats or to validate user input. Returns raw format (0:abc), base64 bounceable (EQ), base64 non-bounceable (UQ), and URL-safe variants.",


All fields should be fully self-descriptive without dependency on other fields:

Example:
description: User-friendly bounceable address in standard base64 encoding.
description: User-friendly bounceable address, base64-encoded and safe for use in URLs.

reveloper · 2025-12-04T08:55:57Z

ecosystem/api/toncenter/v2.json

-        "operationId": "get_extended_address_information_getExtendedAddressInformation_get",
+        "summary": "Detect address",
+        "description": "Validates an address and returns it in all standard formats. Use this to convert between address formats or to validate user input. Returns raw format (0:abc), base64 bounceable (EQ), base64 non-bounceable (UQ), and URL-safe variants.",
+        "operationId": "detectAddress_get",


Since this is related to the user-friendly address flag, it should be accurately explained, that this is representation. This flag not 100% defined, whether the account of qiured address belongs only to the Testnet or Mainnet, because the address itself matches within both networks.

reveloper · 2025-12-08T09:57:29Z

ecosystem/api/toncenter/v2.json

        ],
+        "summary": "Detect address",
+        "description": "Validates an address and returns it in all standard formats. Use this to convert between address formats or to validate user input. Returns raw format (0:abc...), base64 bounceable (EQ...), base64 non-bounceable (UQ...), and URL-safe variants.",
+        "operationId": "detectAddress_post",


For the /api/v2/detectAddress method, address description:

It's better to make a compact definition and add a link:
Account address in raw format (e.g., 0:ca6e321c...) or User-friendly format (e.g., EQDKbjIcfM6ezt8KjKJJLshZJJSqX7XOA4ff-W72r5gqPrHF)

reveloper · 2025-12-08T10:06:42Z

ecosystem/api/toncenter/v2.json

+      "hash": {
+        "name": "hash",
+        "in": "query",
+        "description": "A 256-bit hash in hex (64 chars) or base64 (44 chars) format. Used to identify blocks, transactions, and messages uniquely.",


This description duplicated with another one in render:

reveloper · 2025-12-08T11:09:47Z

ecosystem/api/toncenter/v2.json

+            "type": "array",
+            "items": {
+              "$ref": "#/components/schemas/ExtraCurrencyBalance"
+


Let's define response description with the "Returns" verb. In this way, we avoid overusing "Response," and the description sounds more direct.
Example: Returns the hash of the requested resource in all supported formats (hex, base64, base64 URL-safe).

Can we remove the word "OK" from this description? "OK" is an excess word here.

reveloper · 2025-12-08T11:25:14Z

ecosystem/api/toncenter/v2.json

+            "type": "array",
+            "items": {
+              "$ref": "#/components/schemas/ExtraCurrencyBalance"
+


A Boolean parameter is better suited to describe straightforward boolean values:

Example: Returns true if the request succeeded; otherwise false. See the error field for details.

reveloper · 2025-12-08T11:29:00Z

ecosystem/api/toncenter/v2.json

+                }
+              }
+            ],
+            "description": "The response data. Only present when `ok` is true. "


true should be formatted as code.

reveloper · 2025-12-08T11:30:57Z

ecosystem/api/toncenter/v2.json

+          "b64": {
+            "type": "string",
+            "title": "base64 form",
+            "description": "Standard base64 encoding."


Add a full self-defined description for each child field.

reveloper · 2025-12-08T11:35:19Z

ecosystem/api/toncenter/v2.json

+        "summary": "Pack address",
+        "description": "Converts a raw address to user-friendly base64 format. Raw addresses use the format `workchain:hex` (e.g., `0:abc...`). The packed format is shorter and includes a checksum for error detection.",
+        "operationId": "packAddress_post",
+        "requestBody": {


Duplicated address field description

reveloper · 2025-12-09T07:41:25Z

ecosystem/api/toncenter/v2.json

+        "properties": {
+          "hash": {
+            "$ref": "#/components/schemas/TonHash",
+            "description": "Unique identifier hash for this object."


This object - unclear. Let's specify a list of potential entities here: message, transaction, account?

reveloper · 2025-12-09T08:12:11Z

ecosystem/api/toncenter/v2.json

+            "type": "array",
+            "items": {
+              "$ref": "#/components/schemas/ExtraCurrencyBalance"
+


If we have no child object specified, let's describe this in the overall description. Add self-completed description here, what will be in this data by type, encoding e.t.c.

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>

reveloper · 2026-02-19T05:03:37Z

https://companyname-a7d5b98e-fields.mintlify.app/ecosystem/api/toncenter/v2/accounts/get-address-information#response-result-balance This description seems very clear to me, but I'm afraid any potential reader who opens this method from the beginning will not be able to get how to interact with this data and where to get a complete explanation on decimals (for jettons) and TONs, nanotons terms. It will be much more helpful if we find related links on these terms and point to them on such a balanced field, or add a bit more information in plain text itself. I didn't find separate section in Jetton docs, but I had same task in my page. Maybe we can ask docs team add this as separate page or chapter in jetton documentation and then refer to this.

https://companyname-a7d5b98e-fields.mintlify.app/standard/tokens/jettons/overview
https://companyname-a7d5b98e-fields.mintlify.app/ecosystem/wallet-apps/deep-links#read-more:~:text=One%20whole%20Jetton%20for%20%3CAMOUNT%3E%20is%20defined%20by

reveloper · 2026-02-19T05:05:39Z

https://companyname-a7d5b98e-fields.mintlify.app/ecosystem/api/toncenter/v2/accounts/get-address-information
Descripted twice?

reveloper · 2026-02-19T05:19:00Z

Is it possible to share here an arbitrary example that appears to be real data? If so, is it worth separate task to make this for all methods? Does the OpenAPI v3 JSON content affect this somehow?

reveloper · 2026-02-19T05:25:10Z

https://companyname-a7d5b98e-fields.mintlify.app/ecosystem/api/toncenter/v2/accounts/get-extended-address-information#option-5

Can we enter self-described names here instead of "Option 1", "Option 2", etc.? text?

reveloper · 2026-02-19T05:29:00Z

Seems that we shouldn't provide this until we didn't prepare workable examples like
JavaScript - via @ton/ton
Java - via ton4j
Could you hide all languages and keep the visible curl only for now?
And create a separate task: make a workable example request field with fully supported libraries (@ton/ton, ton4j, ton-utils (Go), ton-utils(Python)).

laviniat1996 · 2026-02-19T14:13:13Z

Is it possible to share here an arbitrary example that appears to be real data? If so, is it worth separate task to make this for all methods? Does the OpenAPI v3 JSON content affect this somehow?

I think it's better to create a new task, as it would be a lot of examples which would make this PR even harder to review.

laviniat1996 · 2026-02-19T14:14:19Z

Seems that we shouldn't provide this until we didn't prepare workable examples like JavaScript - via @ton/ton Java - via ton4j Could you hide all languages and keep the visible curl only for now? And create a separate task: make a workable example request field with fully supported libraries (@ton/ton, ton4j, ton-utils (Go), ton-utils(Python)).

These code snippets are fully autogenerated by mintlify, I don't have control over them tbh

reveloper · 2026-02-26T20:56:57Z

ecosystem/api/toncenter/v2.json

@@ -1,3772 +1,8267 @@
 {
-  "openapi": "3.1.0",
+  "openapi": "3.1.1",


Response description seems duplicated in https://companyname-a7d5b98e-fields.mintlify.app/ecosystem/api/toncenter/v2/accounts/get-extended-address-information#parameter-seqno

Let's refactor to one informative sentence.

reveloper · 2026-02-26T21:09:00Z

ecosystem/api/toncenter/v2.json

      }
    },
-    "/getExtendedAddressInformation": {
+    "/api/v2/getExtendedAddressInformation": {


Give a descriptive name instead of "Option #"
In the description, recall how the option will be defined in the Toncenter api/v2.

https://companyname-a7d5b98e-fields.mintlify.app/ecosystem/api/toncenter/v2/accounts/get-extended-address-information#option-3

reveloper · 2026-02-26T21:11:59Z

ecosystem/api/toncenter/v2.json

      }
    },
-    "/getExtendedAddressInformation": {
+    "/api/v2/getExtendedAddressInformation": {
      "get": {
        "tags": [


Do we have information for the Testnet?

https://companyname-a7d5b98e-fields.mintlify.app/ecosystem/api/toncenter/v2/accounts/get-extended-address-information#response-result-account-state-one-of-2-wallet-id

reveloper · 2026-02-26T21:21:15Z

ecosystem/api/toncenter/v2.json

      "get": {
        "tags": [
          "Accounts"
        ],
-        "summary": "Get detailed account state (extended)",


Fix req/s. Should be RPS or requests per second.

https://companyname-a7d5b98e-fields.mintlify.app/ecosystem/api/toncenter/v2/accounts/get-address-balance

reveloper · 2026-02-26T21:26:12Z

ecosystem/api/toncenter/v2.json

-        "summary": "Get detailed account state (extended)",
-        "description": "Similar to previous one but tries to parse additional information for known contract types. This method is based on tonlib's function *getAccountState*. For detecting wallets we recommend to use *getWalletInformation*.",
-        "operationId": "get_extended_address_information_getExtendedAddressInformation_get",
+        "summary": "Get extended address information",


This field confuses some people with different methods.

We have very similar naming for different entities:

Masterchain seqno

Shardchain seqno

Wallet contract seqno

Custom contract seqno(?)

something else?

We can't change the field name, but let's always (for all seqno fields in docs) text completely which one we have in the description.

https://companyname-a7d5b98e-fields.mintlify.app/ecosystem/api/toncenter/v2/accounts/get-address-balance#parameter-seqno

reveloper · 2026-02-26T21:30:59Z

ecosystem/api/toncenter/v2.json

      }
    },
-    "/getAddressBalance": {
+    "/api/v2/getAddressState": {


Let's add a link to the address states' state documentation: https://docs.ton.org/foundations/status

https://companyname-a7d5b98e-fields.mintlify.app/ecosystem/api/toncenter/v2/accounts/get-address-state

reveloper · 2026-02-27T06:32:19Z

ecosystem/api/toncenter/v2.json

      }
    },
-    "/getAddressState": {
+    "/api/v2/getTokenData": {


Add accurate link to supported contract types will be helpful in the description and field:

https://companyname-a7d5b98e-fields.mintlify.app/ecosystem/api/toncenter/v2-tonlib-types#token-types-ton-center-extensions

reveloper · 2026-02-27T06:41:46Z

ecosystem/api/toncenter/v2.json

      }
    },
-    "/getAddressState": {
+    "/api/v2/getTokenData": {
      "get": {


Description a bit duplicated, can we make this:
Storage method for token (jetton) metadata content:
onchain - stored in contract data)
offchain - external URI

https://companyname-a7d5b98e-fields.mintlify.app/ecosystem/api/toncenter/v2/accounts/get-token-data#response-result-one-of-0-jetton-content-type

reveloper · 2026-02-27T06:46:44Z

ecosystem/api/toncenter/v2.json

      }
    },
-    "/packAddress": {
+    "/api/v2/getBlockTransactions": {


Please add formatting on number parameters in description

https://companyname-a7d5b98e-fields.mintlify.app/ecosystem/api/toncenter/v2/transactions/get-block-transactions#parameter-workchain

reveloper · 2026-02-27T06:52:41Z

ecosystem/api/toncenter/v2.json

      }
    },
-    "/packAddress": {
+    "/api/v2/getBlockTransactions": {
      "get": {


We have very similar naming for different entities:

Masterchain block sequence number

Shardchain block sequence number

Wallet contract (operation or transaction) sequence number

Custom contract (operation or transaction) sequence number(?)

something else?

We can't change the field name, but let's always (for all seqno fields in the docs) specify the exact one we have in the description.

https://companyname-a7d5b98e-fields.mintlify.app/ecosystem/api/toncenter/v2/transactions/get-block-transactions#parameter-seqno

reveloper · 2026-02-27T06:55:10Z

ecosystem/api/toncenter/v2.json

-        "operationId": "pack_address_packAddress_get",
+        "summary": "Get block transactions",
+        "description": "Returns a summary of transactions in a specific block. Each item contains the account address and transaction ID, but not full transaction details. Use `count` to limit results and `after_lt`/`after_hash` for pagination. Call getTransactions with each transaction ID to get full details.",
+        "operationId": "getBlockTransactions_get",


Lost formatting for root_hash, file_hash

https://companyname-a7d5b98e-fields.mintlify.app/ecosystem/api/toncenter/v2/transactions/get-block-transactions#parameter-file-hash

reveloper · 2026-02-27T08:03:43Z

ecosystem/api/toncenter/v2.json

      "get": {
        "tags": [
-          "Accounts"
+          "Transactions"


hash may be calculated within different algorithms, can we point to a specific one in our documentation, or at least text its name:

Extra: almost the same fields(hash and lt) described in a different way in English, make the same sentence structure here, to improve readability.

https://companyname-a7d5b98e-fields.mintlify.app/ecosystem/api/toncenter/v2/transactions/get-block-transactions-extended#response-result-transactions-items-transaction-id-hash

reveloper · 2026-02-27T08:06:41Z

ecosystem/api/toncenter/v2.json

        ],
-        "summary": "Convert user-friendly address to raw format",


Which one hash algorythm

https://companyname-a7d5b98e-fields.mintlify.app/ecosystem/api/toncenter/v2/transactions/get-block-transactions-extended#response-result-transactions-items-out-msgs-items-hash

reveloper · 2026-02-27T08:08:27Z

ecosystem/api/toncenter/v2.json

        ],
-        "summary": "Convert user-friendly address to raw format",
-        "description": "Convert an address from human-readable to raw format.",


Raw or a user-friendly format?

https://companyname-a7d5b98e-fields.mintlify.app/ecosystem/api/toncenter/v2/transactions/get-block-transactions-extended#response-result-transactions-items-out-msgs-items-destination-account-address

reveloper · 2026-02-27T08:10:49Z

ecosystem/api/toncenter/v2.json

-        "summary": "Convert user-friendly address to raw format",
-        "description": "Convert an address from human-readable to raw format.",
-        "operationId": "unpack_address_unpackAddress_get",
+        "summary": "Get block transactions (extended)",


Where from this currency id? Blockchain config? Something else? How is it defined?

https://companyname-a7d5b98e-fields.mintlify.app/ecosystem/api/toncenter/v2/transactions/get-block-transactions-extended#response-result-transactions-items-out-msgs-items-extra-currencies-items-id

reveloper · 2026-02-27T08:12:17Z

ecosystem/api/toncenter/v2.json

-        "description": "Convert an address from human-readable to raw format.",
-        "operationId": "unpack_address_unpackAddress_get",
+        "summary": "Get block transactions (extended)",
+        "description": "Returns full transaction objects for all transactions in a specific block. Each transaction includes complete data: inbound and outbound messages, fees, state changes, and BOC-encoded raw data. Use `count` to limit results and `after_lt`/`after_hash` for pagination when `incomplete` is true.",


Hardfixed in blockchain with 0, cannot be affected

https://companyname-a7d5b98e-fields.mintlify.app/ecosystem/api/toncenter/v2/transactions/get-block-transactions-extended#response-result-transactions-items-out-msgs-items-ihr-fee

reveloper · 2026-03-03T03:09:29Z

ecosystem/api/toncenter/v2.json

      }
    },
-    "/getMasterchainInfo": {
+    "/api/v2/getTransactions": {


Please add the hash algorithm name, which will help to get an idea of how it was calculated.

https://companyname-a7d5b98e-fields.mintlify.app/ecosystem/api/toncenter/v2/transactions/get-transactions#parameter-hash

reveloper · 2026-03-03T03:55:02Z

ecosystem/api/toncenter/v2.json

      }
    },
-    "/getMasterchainInfo": {
+    "/api/v2/getTransactions": {
      "get": {


Since Liteservers have no automation for cleaning data, we can text either:
"at least last two days", or "guaranteed last two days"
The word "About" may be read as some nodes may store less than two days of data.

https://companyname-a7d5b98e-fields.mintlify.app/ecosystem/api/toncenter/v2/transactions/get-transactions#parameter-archival

reveloper · 2026-03-03T04:02:04Z

ecosystem/api/toncenter/v2.json

      "get": {
        "tags": [
-          "Blocks"
+          "Transactions"


Can we rephrase this to a more detailed description:

Storage fees in nanotons that paid from the account balance (in .. phases) during this transaction.

https://companyname-a7d5b98e-fields.mintlify.app/ecosystem/api/toncenter/v2/transactions/get-transactions#response-result-items-fee

reveloper · 2026-03-03T04:12:55Z

ecosystem/api/toncenter/v2.json

      "get": {
        "tags": [
-          "Blocks"
+          "Transactions"
+        ],


Can we rephrase this to a more detailed description:

https://companyname-a7d5b98e-fields.mintlify.app/ecosystem/api/toncenter/v2/transactions/get-transactions#response-result-items-other-fee

reveloper · 2026-03-03T23:16:46Z

ecosystem/api/toncenter/v2.json

      }
    },
-    "/getTransactions": {


If text comment in message, provide text; but what will be otherwise, a void string?

https://companyname-a7d5b98e-fields.mintlify.app/ecosystem/api/toncenter/v2/transactions/get-transactions#response-result-items-in-msg-message

reveloper · 2026-03-03T23:26:56Z

ecosystem/api/toncenter/v2.json

      }
    },
-    "/getMasterchainBlockSignatures": {
+    "/api/v2/getTransactionsStd": {


Is it necessary to point to the version in the description? Seems to exceed information, which possibly may change:

https://companyname-a7d5b98e-fields.mintlify.app/ecosystem/api/toncenter/v2/transactions/get-transactions-standard#response-jsonrpc

reveloper · 2026-03-03T23:30:34Z

ecosystem/api/toncenter/v2.json

      }
    },
-    "/getMasterchainBlockSignatures": {
+    "/api/v2/getTransactionsStd": {
      "get": {


The description consists of two parts that are not completely synergetic. Can we improve this into a single connected text?

reveloper · 2026-03-04T01:07:12Z

ecosystem/api/toncenter/v2.json

      }
    },
-    "/getShardBlockProof": {
+    "/api/v2/tryLocateTx": {


Please unite the "Response" description in a single description.

https://companyname-a7d5b98e-fields.mintlify.app/ecosystem/api/toncenter/v2/transactions/try-locate-transaction#parameter-created-lt

reveloper · 2026-03-04T01:28:46Z

ecosystem/api/toncenter/v2.json

      }
    },
-    "/getShardBlockProof": {
+    "/api/v2/tryLocateTx": {
      "get": {


It's better to define, as "extra currencies", since "non-TON currencies" may be misread and mixed with jetton tokens, which may still appear in the same message.

https://companyname-a7d5b98e-fields.mintlify.app/ecosystem/api/toncenter/v2/transactions/try-locate-transaction#response-result-in-msg-extra-currencies

reveloper · 2026-03-04T01:50:16Z

ecosystem/api/toncenter/v2.json

      }
    },
-    "/getMasterchainInfo": {
+    "/api/v2/getTransactions": {


Please, rephrase this in synergetic text

https://companyname-a7d5b98e-fields.mintlify.app/ecosystem/api/toncenter/v2/blocks/get-masterchain-info#authorization-x-api-key

reveloper · 2026-03-04T02:04:35Z

ecosystem/api/toncenter/v2.json

      }
    },
-    "/getMasterchainInfo": {
+    "/api/v2/getTransactions": {


Please specify the hash algorithm

https://companyname-a7d5b98e-fields.mintlify.app/ecosystem/api/toncenter/v2/blocks/get-masterchain-info#response-result-state-root-hash

reveloper · 2026-03-04T02:18:03Z

ecosystem/api/toncenter/v2.json

      }
    },
-    "/getMasterchainBlockSignatures": {


Page broken?

https://companyname-a7d5b98e-fields.mintlify.app/ecosystem/api/toncenter/v2/blocks/get-masterchain-block-signatures

reveloper · 2026-03-04T03:02:18Z

ecosystem/api/toncenter/v2.json

      }
    },
-    "/getConfigAll": {
+    "/api/v2/getBlockHeader": {


Please, add formatting to variables:
workchain, shard, seqno, root_hash, file_hash, start_lt, and end_lt.

https://companyname-a7d5b98e-fields.mintlify.app/ecosystem/api/toncenter/v2/blocks/get-block-header#response-result-end-lt

reveloper · 2026-03-04T03:06:40Z

ecosystem/api/toncenter/v2.json

      }
    },
-    "/getConfigAll": {
+    "/api/v2/getBlockHeader": {
      "get": {


seqno always should be formatted as code in text

https://companyname-a7d5b98e-fields.mintlify.app/ecosystem/api/toncenter/v2/blocks/get-block-header#response-result-min-ref-mc-seqno

reveloper · 2026-03-04T03:12:57Z

ecosystem/api/toncenter/v2.json

      }
    },
-    "/tryLocateResultTx": {
+    "/api/v2/getOutMsgQueueSize": {


Rework the response description to one fit text.

https://companyname-a7d5b98e-fields.mintlify.app/ecosystem/api/toncenter/v2/blocks/get-outbound-message-queue-size#authorization-x-api-key

reveloper · 2026-03-04T03:18:35Z

ecosystem/api/toncenter/v2.json

      }
    },
-    "/sendBoc": {
+    "/api/v2/runGetMethod": {


Let's add the link to exit codes https://docs.ton.org/tvm/exit-codes#exit-codes

https://companyname-a7d5b98e-fields.mintlify.app/ecosystem/api/toncenter/v2/run-method/run-get-method#response-result-exit-code

reveloper · 2026-03-04T03:24:31Z

ecosystem/api/toncenter/v2.json

            "content": {
              "application/json": {
                "schema": {
-                  "$ref": "#/components/schemas/TonResponse"
+                  "$ref": "#/components/schemas/SendBocReturnHashResponse"


Please specify the hash algorithm in the description. Let's add a link to the normalized hash standard.
https://github.com/ton-blockchain/TEPs/blob/master/text/0467-normalized-message-hash.md

https://companyname-a7d5b98e-fields.mintlify.app/ecosystem/api/toncenter/v2/send/send-boc-return-hash#response-result-hash

laviniat1996 added 2 commits November 28, 2025 05:27

update field descriptions

00366ae

Merge branch 'main' into fields

b6eee23

laviniat1996 self-assigned this Nov 28, 2025

laviniat1996 marked this pull request as draft November 28, 2025 03:30

mintlify bot deployed to staging November 28, 2025 03:30 View deployment

laviniat1996 changed the title ~~update field descriptions~~ update API v2 field descriptions Nov 28, 2025

laviniat1996 added the 3p Reviewed by someone else (a third party). Used for filtering PRs. Don't mind this. label Dec 1, 2025

reveloper self-requested a review December 4, 2025 06:09

reveloper requested changes Dec 4, 2025

View reviewed changes

Merge branch 'main' into fields

87fe3f6

mintlify bot deployed to staging December 8, 2025 09:37 View deployment

reveloper requested changes Dec 8, 2025

View reviewed changes

reveloper requested changes Dec 9, 2025

View reviewed changes

Merge branch 'main' into fields

4e0cc6c

mintlify bot deployed to staging February 17, 2026 13:12 View deployment

error updates

eaef911

mintlify bot deployed to staging February 17, 2026 14:43 View deployment

updates

d0a488f

laviniat1996 changed the title ~~update API v2 field descriptions~~ docs (feat): update API v2 field descriptions Feb 17, 2026

laviniat1996 changed the title ~~docs (feat): update API v2 field descriptions~~ feat (docs): update API v2 field descriptions Feb 17, 2026

mintlify bot deployed to staging February 17, 2026 14:58 View deployment

laviniat1996 changed the title ~~feat (docs): update API v2 field descriptions~~ feat(docs): update API v2 field descriptions Feb 17, 2026

mintlify bot deployed to staging February 18, 2026 06:14 View deployment

updates

76f13c0

laviniat1996 force-pushed the fields branch from b2b2ae2 to 76f13c0 Compare February 18, 2026 08:07

Merge branch 'main' into fields

10e0c23

This comment has been minimized.

Sign in to view

laviniat1996 and others added 3 commits February 19, 2026 06:19

Update ecosystem/api/toncenter/v2.json

7df77e0

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>

Update ecosystem/api/toncenter/v2.json

bf12b55

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>

Update ecosystem/api/toncenter/v2.json

6e03f08

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>

mintlify bot deployed to staging February 19, 2026 04:20 View deployment

Merge branch 'main' into fields

051c8a3

mintlify bot deployed to staging February 19, 2026 04:20 View deployment

mintlify bot deployed to staging February 19, 2026 04:21 View deployment

mintlify bot deployed to staging February 19, 2026 04:22 View deployment

mintlify bot deployed to staging February 19, 2026 04:32 View deployment

laviniat1996 mentioned this pull request Feb 19, 2026

[Ecosystem > API > TON Center > API v2 > Tonlib Types] #1870

Open

reveloper requested changes Feb 26, 2026

View reviewed changes

reveloper requested changes Feb 27, 2026

View reviewed changes

remove tonlib types file

2692094

mintlify bot deployed to staging February 28, 2026 01:22 View deployment

reveloper requested changes Mar 3, 2026

View reviewed changes

reveloper requested changes Mar 4, 2026

View reviewed changes

laviniat1996 added 3 commits March 5, 2026 04:39

address comments

3db86db

Merge branch 'main' into fields

0a6fc7e

fixes

0f941ec

mintlify bot deployed to staging March 5, 2026 02:48 View deployment

Conversation

laviniat1996 commented Nov 28, 2025

Uh oh!

github-actions bot commented Nov 28, 2025

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

reveloper Dec 4, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

This comment has been minimized.

reveloper commented Feb 19, 2026

Uh oh!

reveloper commented Feb 19, 2026

Uh oh!

reveloper commented Feb 19, 2026

Uh oh!

reveloper commented Feb 19, 2026

Uh oh!

reveloper commented Feb 19, 2026

Uh oh!

laviniat1996 commented Feb 19, 2026

Uh oh!

laviniat1996 commented Feb 19, 2026

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

reveloper Dec 4, 2025 •

edited

Loading