4.5.35 dd. 09/03/2026#
Description#
- Implemented methods for working with contacts
- Extended the response of the GetContactInfo method
- Added a new status code
469to the response of the CheckAccount method - Added sorting of chats by last activity time in the GetChats method
- Optimized service performance
- Fixed an error where the instance switched to the
startingstatus after calling the StartAuthorization method - Fixed identified errors (24 pcs)
Attention#
Important changes that may affect your integration with the API and may require additional code modifications on your side:
- Added a new status code
469to the response of the CheckAccount method — handling of the new code is required on your side - Extended the response of the GetContactInfo method — new fields have been added:
isPremium,isVerified,isScam,description.
Tasks#
| No. | Number | Result | Documentation |
|---|---|---|---|
| 1 | TGM-256 | Implemented methods for working with contacts | Documentation |
| 2 | TGM-268 | Extended the response of the GetContactInfo method | Documentation |
| 3 | TGM-319 | Added a new error status code 469 for the CheckAccount method | Documentation |
| 4 | TGM-282 | Implemented support for the isForwarded and forwardingScore flags in the journal for textMessage | Documentation |
| 5 | TGM-299 | Implemented sorting of chats by last activity time in the response of the GetChats method | Documentation |
| 6 | TGM-308 | Implemented support for handling chat changes with the GetChats method | Documentation |
| 7 | TGM-186 | Optimized the performance of the CheckAccount method | |
| 8 | TGM-307 | Optimized chat synchronization | |
| 9 | TGM-281 | Optimized database performance | |
| 10 | TGM-278 | Optimized cache handling |
Issues#
| No. | Number | Description | Status |
|---|---|---|---|
| 1 | TGM-283 | Error writing the second and subsequent message edits to the journal | Fixed |
| 2 | TGM-285 | Error with an empty lastSeen value in the GetContactInfo method | Fixed |
| 3 | TGM-286 | Error where the instance switched to the suspended status when there were no restrictions on the account | Fixed |
| 4 | TGM-287 | Error with incorrect instance behavior when using the StartAuthorization method | Fixed |
| 5 | TGM-291 | Error where the instance switched to the blocked status when sending a message to a deleted account | Fixed |
| 6 | TGM-304 | Error writing empty chatType and statusMessage values to journals | Fixed |
| 7 | TGM-310 | ALLOW_PAYMENT_REQUIRED error when sending a message from the queue | Fixed |
| 8 | TGM-313 | Error downloading avatars and files | Fixed |
| 9 | TGM-314 | Error where the instance froze when calling the StartAuthorization method again | Fixed |
| 10 | TGM-315 | Error sending the first message by chatId | Fixed |
| 11 | TGM-318 | Error with the timestamp value when changing the message status to read | Fixed |
| 12 | TGM-322 | Error with an empty senderData value in the deletedMessage webhook | Fixed |
| 13 | TGM-216 | Error where idMessage does not change when sending and receiving messages | Fixed |
| 14 | TGM-280 | Error in the location data structure in journals when sending with the SendLocation method | Fixed |
| 15 | TGM-292 | Error with status 500 in the GetAccountSettings and GetAvatar methods | Fixed |
| 16 | TGM-294 | Error with instance authorization after calling the StartAuthorization method | Fixed |
| 17 | TGM-312 | Error where the webhook with the starting status was not sent when the server was unavailable | Fixed |
| 18 | TGM-305 | Error with duplicate messages in the database | Fixed |
| 19 | TGM-306 | Error when uploading files | Fixed |
| 20 | TGM-279 | Error in the contact data structure in webhooks and journals when sending with the SendContact method | Fixed |
| 21 | TGM-309 | Error sending a message by chatId | Fixed |
| 22 | TGM-311 | Error with lost notifications during instance synchronization | Fixed |
| 23 | TGM-320 | Error where the instance switched to the starting status after calling the StartAuthorization method | Fixed |
| 24 | TGM-323 | Error with lost authorization when Telegram is unavailable | Fixed |