Adds a peer to a blocklist, see here » for more info.
API section: Working with contacts and top peers
contacts.block#2e2e8734 flags:# my_stories_from:flags.0?true id:InputPeer = Bool;
| Name | Type | Description |
|---|---|---|
| flags | # | Bit mask: a field written flags.N?T is present only when bit N is set. |
| my_stories_from | flags.0?true | |
| id | InputPeer | Identifier of the object — which object depends on the field's type. |
Read out of the handler itself — this is what the server actually returns for this method.
| Code | Type | What it means |
|---|---|---|
| 400 | PEER_ID_INVALID |
The peer or chat is invalid — or you have no access to it. |
| 400 | USER_ID_INVALID |
No user with this identifier exists. |
| Code | Type | What it means |
|---|---|---|
| 401 | AUTH_KEY_UNREGISTERED |
The server does not know this session: the key was revoked, expired, or the call was made before authorisation. |
| 401 | API_ID_INVALID |
This api_id was never issued or has been blocked. Keys come from my.ansible.su. |
| 400 | CONNECTION_LAYER_INVALID |
The client did not declare a layer, or declared one the server does not know. |
| 420 | FLOOD_WAIT_X |
Too often. Do not retry for X seconds — the number arrives in the error text. |
| 500 | INTERNAL |
A failure on our side. The request may be retried; if it keeps failing, it is a bug of ours. |