MadelineProtoDocs/old_docs/API_docs_v75/methods/account_getNotifySettings.md

67 lines
1.4 KiB
Markdown
Raw Normal View History

2018-04-01 13:19:25 +02:00
---
2018-06-29 13:59:08 +02:00
title: account.getNotifySettings
description: Get notification settings
2018-04-04 19:52:48 +02:00
image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
2018-04-01 13:19:25 +02:00
---
2018-06-29 13:59:08 +02:00
# Method: account.getNotifySettings
2018-04-01 13:19:25 +02:00
[Back to methods index](index.md)
2018-06-29 13:59:08 +02:00
Get notification settings
2018-04-01 13:19:25 +02:00
### Parameters:
2018-08-29 11:18:25 +02:00
| Name | Type | Description | Required |
|----------|---------------|-------------|----------|
2018-08-30 20:01:58 +02:00
|peer|[Username, chat ID, Update, Message or InputNotifyPeer](../types/InputNotifyPeer.md) | Notification source | Yes|
2018-04-01 13:19:25 +02:00
2018-06-29 13:59:08 +02:00
### Return type: [PeerNotifySettings](../types/PeerNotifySettings.md)
2018-04-01 13:19:25 +02:00
### Can bots use this method: **NO**
### MadelineProto Example:
```php
2018-04-01 13:19:25 +02:00
if (!file_exists('madeline.php')) {
copy('https://phar.madelineproto.xyz/madeline.php', 'madeline.php');
}
include 'madeline.php';
$MadelineProto = new \danog\MadelineProto\API('session.madeline');
$MadelineProto->start();
2018-06-29 13:59:08 +02:00
$PeerNotifySettings = $MadelineProto->account->getNotifySettings(['peer' => InputNotifyPeer, ]);
2018-04-01 13:19:25 +02:00
```
### [PWRTelegram HTTP API](https://pwrtelegram.xyz) example (NOT FOR MadelineProto):
### As a user:
2018-06-29 13:59:08 +02:00
POST/GET to `https://api.pwrtelegram.xyz/userTOKEN/account.getNotifySettings`
2018-04-01 13:19:25 +02:00
Parameters:
2018-06-29 13:59:08 +02:00
peer - Json encoded InputNotifyPeer
2018-04-01 13:19:25 +02:00
Or, if you're into Lua:
```lua
2018-06-29 13:59:08 +02:00
PeerNotifySettings = account.getNotifySettings({peer=InputNotifyPeer, })
2018-04-01 13:19:25 +02:00
```
### Errors this method can return:
| Error | Description |
|----------|---------------|
2018-06-29 13:59:08 +02:00
|PEER_ID_INVALID|The provided peer id is invalid|
2018-04-01 13:19:25 +02:00