Export a folder », creating a chat folder deep link ».
API section: Working with folders
chatlists.exportChatlistInvite#8472478e chatlist:InputChatlist title:string peers:Vector<InputPeer> = chatlists.ExportedChatlistInvite;
| Name | Type | Description |
|---|---|---|
| chatlist | InputChatlist | |
| title | string | Title. |
| peers | Vector<InputPeer> | A list of users and chats. |
chatlists.ExportedChatlistInvite
Read out of the handler itself — this is what the server actually returns for this method.
| Code | Type | What it means |
|---|---|---|
| 400 | FILTER_ID_INVALID |
No folder with this identifier exists. |
| 400 | INVITES_TOO_MUCH |
The limit of invite links has been reached. |
| 400 | PEER_ID_INVALID |
The peer or chat is invalid — or you have no access to it. |
| 400 | PEERS_LIST_EMPTY |
The list of recipients is empty. |
| 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. |