Returns information about the next messages of the specified type in the chat split by days.Returns the results in reverse chronological order. Can return partial results for the last returned day.
API section: Working with messages
messages.getSearchResultsCalendar#6aa3f6bd flags:# peer:InputPeer saved_peer_id:flags.2?InputPeer filter:MessagesFilter offset_id:int offset_date:int = messages.SearchResultsCalendar;
| Name | Type | Description |
|---|---|---|
| flags | # | Bit mask: a field written flags.N?T is present only when bit N is set. |
| peer | InputPeer | The user or chat the request is about. |
| saved_peer_id | flags.2?InputPeer | Section of Saved Messages the request is about. |
| filter | MessagesFilter | Selection filter. |
| offset_id | int | Identifier to continue the selection from. |
| offset_date | int | Date to continue the selection from. |
messages.SearchResultsCalendar
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. |