Message is an audio file.
Signature of the post author for messages in channels
Caption for the animation, audio, document, photo, video or voice, 0-1024 characters
For messages with a caption, special entities like usernames, URLs, bot commands, etc. that appear in the caption
Conversation the message belongs to
The domain name of the website on which the user has logged in.
Date the message was sent in Unix time
Duration of the audio in seconds as defined by sender
Date the message was last edited in Unix time
Identifier for this file, which can be used to download or reuse the file
Original filename as defined by sender if available
Unique identifier for this file, which is supposed to be the same over time and for different bots. Can't be used to download or reuse the file.
For forwarded messages, date the original message was sent in Unix time
For forwarded messages, sender of the original message
For messages forwarded from channels, information about the original channel
For messages forwarded from channels, identifier of the original message in the channel
Sender's name for messages forwarded from users who disallow adding a link to their account in forwarded messages
For messages forwarded from channels, signature of the post author if present
Raw user object represent the sender, empty for messages sent to channels
The unique identifier of a media message group this message belongs to
Unique message identifier inside this chat
MIME type of the file as defined by sender
Telegram Passport data
Performer of the audio as defined by sender or by audio tags
Inline keyboard attached to the message. login_url buttons are represented as ordinary url buttons.
For replies, the original message. Note that the Message object in this field will not contain furth
File thumbnail as defined by sender if available
Title of the audio as defined by sender or by audio tags
The update's unique identifier. Update identifiers start from a certain positive number and increase sequentially. This ID becomes especially handy if you're using Webhooks, since it allows you to ignore repeated updates or to restore the correct update sequence, should they get out of order. If there are no new updates for at least a week, then identifier of the next update will be chosen randomly instead of sequentially.
Bot through which the message was sent
Generated using TypeDoc