# Validating recipient's Binance ID

<mark style="color:green;">`POST`</mark> `/api/public/v1/payouts/binance_receiver/validate`

This endpoint validates the recipient's Binance ID.

Make sure to supply `application/json` in the `Content-Type` header.

**Headers**

| Name          | Value              |
| ------------- | ------------------ |
| Content-Type  | `application/json` |
| Authorization | `Bearer <api_key>` |

**Request Body**

<table><thead><tr><th width="126">Name</th><th width="111">Type</th><th width="105">Required</th><th>Description</th></tr></thead><tbody><tr><td><code>receiver_id</code></td><td>string</td><td>Yes</td><td>Recipient's Binance ID, e.g. <code>474748434</code>. It must always be numeric and can range from 8 to 10 digits. As the number of Binance users increases, it may grow to 11 or 12 digits in the future.</td></tr></tbody></table>

**Response**

{% tabs %}
{% tab title="HTTP 200" %}

```json
{
  "data": {},
  "status": "ok",
  "jsonapi": {
    "version": "1.0"
  }
}

// The Binance ID format is valid
```

{% endtab %}

{% tab title="HTTP 422" %}

```json
{
  "errors": [
    {
      "status": 422,
      "title": "Invalid receiver",
      "code": "binance_pay_invalid_receiver",
      "detail": "The provided Binance ID is not valid."
    }
  ]

// The Binance ID format is not valid
```

{% endtab %}
{% endtabs %}


---

# Agent Instructions: 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:

```
GET https://docs.txn.io/payouts/validating-recipients-binance-id.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.