# Check a bot token

`POST /service/@id/tinopay/notification-apps/bot-info` · TinoPay, service owner's sign-in token

Step 1 when adding a notification app with your own bot: `type` (`telegram`, `zalo`) and the `bot_token` just entered, or `app_id` to use that app's stored token (when editing). Returns `{valid, bot_name, error}`: when `valid` is `false`, show `error`. See [Telegram, Zalo and Lark notifications](/en/docs/tinopay-notifications).

## HTTP request

| Item | Value |
| --- | --- |
| URL | `https://api.tino.vn/service/@id/tinopay/notification-apps/bot-info` |
| Method | `POST` |
| Authentication | the TinoPay service owner's sign-in token (`Authorization: Bearer <token>`); the `/v1` gateway does not expose TinoPay yet |
| Content-Type | `application/json` |

## Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `id` | path | int | yes | TinoPay service ID |
| `type` | body | string | — | telegram \| zalo |
| `bot_token` | body | string | — | — |
| `app_id` | body | int | — | — |

## Example request

```bash
curl -X POST "https://api.tino.vn/service/100001/tinopay/notification-apps/bot-info" \
  -H "Authorization: Bearer $TINO_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
  "type": "zalo",
  "bot_token": "<bot_token>"
}'
```

`$TINO_TOKEN` is the TinoPay service owner's sign-in token. Path parameters in the example are sample values.

SDK ([SDK & examples](/en/docs/sdk)): no dedicated function yet, use `client.request("POST", "/service/@id/tinopay/notification-apps/bot-info")`.

## Example response

```json
{
 "data": {
  "valid": true,
  "bot_name": "Bot Cửa hàng ABC",
  "error": null
 }
}
```

Sample built from the TinoPay API v1 documentation (Tino relays TinoPay data as is); values are examples.