> For the complete documentation index, see [llms.txt](https://apidocs.webcom.mobi/en/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://apidocs.webcom.mobi/en/sposoby-vzaimodeistviya-s-a2p-platformoi/json-specification/balance-check-request.md).

# Balance check request

## Balance check request

<mark style="color:green;">`POST`</mark> `http://lk.mysmpp.ru/json/balance.php`

#### Headers

| Name                                           | Type   | Description                    |
| ---------------------------------------------- | ------ | ------------------------------ |
| Content-type<mark style="color:red;">\*</mark> | String | **`text/json; charset=utf-8`** |

#### Request Body

| Name                                       | Type   | Description                                                                                        |
| ------------------------------------------ | ------ | -------------------------------------------------------------------------------------------------- |
| login<mark style="color:red;">\*</mark>    | String | Your login in the system                                                                           |
| token<mark style="color:red;">\*</mark>    | String | You can use a secret key instead of login and password. To obtain it, please contact your manager. |
| password<mark style="color:red;">\*</mark> | String | Your password in the system                                                                        |

{% tabs %}
{% tab title="200: OK In case the correct JSON document is received" %}

```json
{
    "money": "19023.9",
    "currency": "RUR",
    "information": 
        [
            {
                "type_sms": "sms",
                "area": "Tele2",
                "num_sms": "72029"
            }, 
            {
                "type_sms": "sms",
                "area": "Russia",
                "num_sms": "Unlim"
            }
        ]
}
```

{% endtab %}

{% tab title="400: Bad Request If an error occurs in the sent JSON document" %}

```json
{
    "error": "Error message"
}
```

{% endtab %}
{% endtabs %}

### Deciphering parameters in query responses

<table><thead><tr><th width="210.33333333333331">Parameter</th><th width="137">Data type</th><th>Description</th></tr></thead><tbody><tr><td>money</td><td>Int</td><td>Fund balance</td></tr><tr><td>currency</td><td>String</td><td>Currency</td></tr><tr><td>information.type_sms</td><td>String</td><td>Type of SMS</td></tr><tr><td>information.area</td><td>String</td><td>The direction in which a given quantity can be shippedво SMS</td></tr><tr><td>information.sms</td><td>Int</td><td>Number of available SMS messages for this destination</td></tr><tr><td>error</td><td>String</td><td><p></p><p>The error text can take the following values:</p><ul><li>Incorrect JSON document format </li><li>Your account is locked </li><li>Incorrect login or password </li><li>POST data is missing</li></ul></td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://apidocs.webcom.mobi/en/sposoby-vzaimodeistviya-s-a2p-platformoi/json-specification/balance-check-request.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.