Get messages in a reply thread
API section: Working with message threads
messages.getReplies#22ddd30c peer:InputPeer msg_id:int offset_id:int offset_date:int add_offset:int limit:int max_id:int min_id:int hash:long = messages.Messages;
| Name | Type | Description |
|---|---|---|
| peer | InputPeer | The user or chat the request is about. |
| msg_id | int | Message identifier within its chat. |
| offset_id | int | Identifier to continue the selection from. |
| offset_date | int | Date to continue the selection from. |
| add_offset | int | Extra shift relative to offset_id. |
| limit | int | Maximum number of records to return. |
| max_id | int | Upper bound on the identifier. |
| min_id | int | Lower bound on the identifier. |
| hash | long | Hash of what the client already has. If it matches, the server answers "not modified" and sends nothing again. |
This method has no errors of its own: it either answers or fails on the shared checks below.
| 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. |