# Update a notification app

`PATCH /service/@id/tinopay/notification-apps/@app` · TinoPay, service owner's sign-in token

Send only the fields to change, as a JSON body, never `type`. No `bot_token`: keep the stored token; a new string: replace it; `bot_token: null`: Telegram goes back to the shared bot (then `endpoint` must be a group ID `-…`); Zalo cannot drop its token. A `bank_account_id` that does not belong to the merchant: 404 `BANK_ACCOUNT_NOT_FOUND`.

## HTTP request

| Item | Value |
| --- | --- |
| URL | `https://api.tino.vn/service/@id/tinopay/notification-apps/@app` |
| Method | `PATCH` |
| 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 |
| `app` | path | int | yes | Notification app ID (`id` in the notification app list) |
| `name` | body | string | — | — |
| `endpoint` | body | string | — | — |
| `bot_token` | body | string | — | — |
| `bank_account_id` | body | string | — | — |
| `virtual_accounts` | body | array | — | — |
| `status` | body | string | — | active \| inactive |

## Example request

```bash
curl -X PATCH "https://api.tino.vn/service/100001/tinopay/notification-apps/7" \
  -H "Authorization: Bearer $TINO_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
  "status": "inactive"
}'
```

`$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("PATCH", "/service/@id/tinopay/notification-apps/@app")`.

## Example response

The source documentation does not show this route's answer. Success is `{"data": …}`; errors follow the common shape in [Getting started with TinoPay](/en/docs/tinopay-start#errors).