Skip to main content

wdg_telegram_types/
lib.rs

1type TelegramString=String;
2type TelegramInteger=i32;
3type TelegramFloat=f32;
4type TelegramBoolean=bool;
5type TelegramTrue=bool;
6
7/// This object represents a Telegram user or bot.
8pub struct User{
9	/// Unique identifier for this user or bot
10	pub _id: TelegramInteger,
11	/// True, if this user is a bot
12	pub _is_bot: TelegramBoolean,
13	/// User‘s or bot’s first name
14	pub _first_name: TelegramString,
15	/// Optional. User‘s or bot’s last name
16	pub _last_name: Option<TelegramString>,
17	/// Optional. User‘s or bot’s username
18	pub _username: Option<TelegramString>,
19	/// Optional. IETF language tag of the user's language
20	pub _language_code: Option<TelegramString>
21}
22
23/// This object represents a chat.
24pub struct Chat{
25	/// Unique identifier for this chat. This number may be greater than 32 bits and some programming languages may have difficulty/silent defects in interpreting it. But it is smaller than 52 bits, so a signed 64 bit integer or double-precision float type are safe for storing this identifier.
26	pub _id: TelegramInteger,
27	/// Type of chat, can be either “private”, “group”, “supergroup” or “channel”
28	pub _type: TelegramString,
29	/// Optional. Title, for supergroups, channels and group chats
30	pub _title: Option<TelegramString>,
31	/// Optional. Username, for private chats, supergroups and channels if available
32	pub _username: Option<TelegramString>,
33	/// Optional. First name of the other party in a private chat
34	pub _first_name: Option<TelegramString>,
35	/// Optional. Last name of the other party in a private chat
36	pub _last_name: Option<TelegramString>,
37	/// Optional. True if a group has ‘All Members Are Admins’ enabled.
38	pub _all_members_are_administrators: Option<TelegramBoolean>,
39	/// Optional. Chat photo. Returned only in getChat.
40	pub _photo: Option<ChatPhoto>,
41	/// Optional. Description, for supergroups and channel chats. Returned only in getChat.
42	pub _description: Option<TelegramString>,
43	/// Optional. Chat invite link, for supergroups and channel chats. Returned only in getChat.
44	pub _invite_link: Option<TelegramString>,
45	/// Optional. Pinned message, for supergroups. Returned only in getChat.
46	pub _pinned_message: Option<Box<Message>>
47}
48
49/// This object represents a chat photo.
50pub struct ChatPhoto{
51	/// Unique file identifier of small (160x160) chat photo. This file_id can be used only for photo download.
52	pub _small_file_id: TelegramString,
53	/// Unique file identifier of big (640x640) chat photo. This file_id can be used only for photo download.	
54	pub _big_file_id: TelegramString
55}
56
57/// This object represents a message.
58pub struct Message{
59	/// Unique message identifier inside this chat
60	pub _message_id: TelegramInteger,
61	/// Optional. Sender, empty for messages sent to channels
62	pub _from: Option<User>,
63	/// Date the message was sent in Unix time
64	pub _date: TelegramInteger,
65	/// Conversation the message belongs to
66	pub _chat: Chat,
67	/// Optional. For forwarded messages, sender of the original message
68	pub _forward_from: Option<User>,
69	/// Optional. For messages forwarded from channels, information about the original channel
70	pub _forward_from_chat: Option<Chat>,
71	/// Optional. For messages forwarded from channels, identifier of the original message in the channel
72	pub _forward_from_message_id: Option<TelegramInteger>,
73	/// Optional. For messages forwarded from channels, signature of the post author if present
74	pub _forward_signature: Option<TelegramString>,
75	/// Optional. For forwarded messages, date the original message was sent in Unix time
76	pub _forward_date: Option<TelegramInteger>,
77	/// Optional. For replies, the original message. Note that the Message object in this field will not contain further reply_to_message fields even if it itself is a reply.
78	pub _reply_to_message: Option<Box<Message>>,
79	/// Optional. Date the message was last edited in Unix time
80	pub _edit_date: Option<TelegramInteger>,
81	/// Optional. Signature of the post author for messages in channels
82	pub _author_signature: Option<TelegramString>,
83	/// Optional. For text messages, the actual UTF-8 text of the message, 0-4096 characters.
84	pub _text: Option<TelegramString>,
85	/// Optional. For text messages, special entities like usernames, URLs, bot commands, etc. that appear in the text
86	pub _entities: Option<Vec<MessageEntity>>,
87	/// Optional. Message is an audio file, information about the file
88	pub _audio: Option<Audio>,
89	/// Optional. Message is a general file, information about the file
90	pub _document: Option<Document>,
91	/// Optional. Message is a game, information about the game.
92	pub _game: Option<Game>,
93	/// Optional. Message is a photo, available sizes of the photo
94	pub _photo: Option<Vec<PhotoSize>>,
95	/// Optional. Message is a sticker, information about the sticker
96	pub _sticker: Option<Sticker>,
97	/// Optional. Message is a video, information about the video
98	pub _video: Option<Video>,
99	/// Optional. Message is a voice message, information about the file
100	pub _voice: Option<Voice>,
101	/// Optional. Message is a video note, information about the video message
102	pub _video_note: Option<VideoNote>,
103	/// Optional. Caption for the document, photo or video, 0-200 characters
104	pub _caption: Option<String>,
105	/// Optional. Message is a shared contact, information about the contact
106	pub _contact: Option<Contact>,
107	/// Optional. Message is a shared location, information about the location
108	pub _location: Option<Location>,
109	/// Optional. Message is a venue, information about the venue
110	pub _venue: Option<Venue>,
111	/// Optional. New members that were added to the group or supergroup and information about them (the bot itself may be one of these members)
112	pub _new_chat_members: Option<Vec<User>>,
113	/// Optional. A member was removed from the group, information about them (this member may be the bot itself)
114	pub _left_chat_member: Option<User>,
115	/// Optional. A chat title was changed to this value
116	pub _new_chat_title: Option<String>,
117	/// Optional. A chat photo was change to this value
118	pub _new_chat_photo: Option<Vec<PhotoSize>>,
119	/// Optional. Service message: the chat photo was deleted
120	pub _delete_chat_photo: Option<TelegramTrue>,
121	/// Optional. Service message: the group has been created
122	pub _group_chat_created: Option<TelegramTrue>,
123	/// Optional. Service message: the supergroup has been created. This field can‘t be received in a message coming through updates, because bot can’t be a member of a supergroup when it is created. It can only be found in reply_to_message if someone replies to a very first message in a directly created supergroup.
124	pub _supergroup_chat_created: Option<TelegramTrue>,
125	/// Optional. Service message: the channel has been created. This field can‘t be received in a message coming through updates, because bot can’t be a member of a channel when it is created. It can only be found in reply_to_message if someone replies to a very first message in a channel.
126	pub _channel_chat_created: Option<TelegramTrue>,
127	/// Optional. The group has been migrated to a supergroup with the specified identifier. This number may be greater than 32 bits and some programming languages may have difficulty/silent defects in interpreting it. But it is smaller than 52 bits, so a signed 64 bit integer or double-precision float type are safe for storing this identifier.
128	pub _migrate_to_chat_id: Option<TelegramInteger>,
129	/// Optional. The supergroup has been migrated from a group with the specified identifier. This number may be greater than 32 bits and some programming languages may have difficulty/silent defects in interpreting it. But it is smaller than 52 bits, so a signed 64 bit integer or double-precision float type are safe for storing this identifier.
130	pub _migrate_from_chat_id: Option<TelegramInteger>,
131	/// Optional. Specified message was pinned. Note that the Message object in this field will not contain further reply_to_message fields even if it is itself a reply.
132	pub _pinned_message: Option<Box<Message>>,
133	/// Optional. Message is an invoice for a payment, information about the invoice. More about payments »
134	pub _invoice: Option<Invoice>,
135	/// Optional. Message is a service message about a successful payment, information about the payment. More about payments 
136	pub _successful_payment: Option<SuccessfulPayment>
137}
138
139/// This object represents one special entity in a text message. For example, hashtags, usernames, URLs, etc.
140pub struct MessageEntity{
141	/// Type of the entity. Can be mention (@username), hashtag, bot_command, url, email, bold (bold text), italic (italic text), code (monowidth string), pre (monowidth block), text_link (for clickable text URLs), text_mention (for users without usernames)
142	pub _type: TelegramString,
143	/// Offset in UTF-16 code units to the start of the entity
144	pub _offset: TelegramInteger,
145	/// Length of the entity in UTF-16 code units
146	pub _length: TelegramInteger,
147	/// Optional. For “text_link” only, url that will be opened after user taps on the text
148	pub _url: Option<TelegramString>,
149	/// Optional. For “text_mention” only, the mentioned user
150	pub _user: Option<User>
151}
152
153/// This object represents an audio file to be treated as music by the Telegram clients.
154pub struct Audio{
155	/// Unique identifier for this file
156	pub _file_id: TelegramString,
157	/// Duration of the audio in seconds as defined by sender
158	pub _duration: TelegramInteger,
159	/// Optional. Performer of the audio as defined by sender or by audio tags
160	pub _performer: Option<TelegramString>,
161	/// Optional. Title of the audio as defined by sender or by audio tags	
162	pub _title: Option<TelegramString>,
163	/// Optional. MIME type of the file as defined by sender
164	pub _mime_type: Option<TelegramString>,
165	/// Optional. File size
166	pub _file_size: Option<TelegramInteger>
167}
168
169/// This object represents a general file (as opposed to photos, voice messages and audio files).
170pub struct Document{
171	/// Unique file identifier
172	pub _file_id: TelegramString,
173	/// Optional. Document thumbnail as defined by sender
174	pub _thumb: Option<PhotoSize>,
175	/// Optional. Original filename as defined by sender
176	pub _file_name: Option<TelegramString>,
177	/// Optional. MIME type of the file as defined by sender	
178	pub _mime_type: Option<TelegramString>,
179	/// Optional. File size
180	pub _file_size: Option<TelegramInteger>
181}
182
183/// This object represents one size of a photo or a file / sticker thumbnail.
184pub struct PhotoSize{
185	/// Unique identifier for this file
186	pub _file_id: TelegramString,
187	/// Photo width
188	pub _width: TelegramInteger,
189	/// Photo height
190	pub _height: TelegramInteger,
191	/// Optional. File size
192	pub _file_size: Option<TelegramInteger>
193}
194
195/// This object represents a game. Use BotFather to create and edit games, their short names will act as unique identifiers.
196pub struct Game{
197	/// Title of the game
198	pub _title: TelegramString,
199	/// Description of the game
200	pub _description: TelegramString,
201	/// Photo that will be displayed in the game message in chats.
202	pub _photo: Vec<PhotoSize>,
203	/// Optional. Brief description of the game or high scores included in the game message. Can be automatically edited to include current high scores for the game when the bot calls setGameScore, or manually edited using editMessageText. 0-4096 characters.
204	pub _text: Option<TelegramString>,
205	/// Optional. Special entities that appear in text, such as usernames, URLs, bot commands, etc.
206	pub _text_entities: Option<Vec<MessageEntity>>,
207	/// Optional. Animation that will be displayed in the game message in chats. Upload via BotFather
208	pub _animation: Option<Animation>
209}
210
211/// You can provide an animation for your game so that it looks stylish in chats (check out Lumberjack for an example). This object represents an animation file to be displayed in the message containing a game.
212pub struct Animation{
213	/// Unique file identifier
214	pub _file_id: TelegramString,
215	/// Optional. Animation thumbnail as defined by sender
216	pub _thumb: Option<PhotoSize>,
217	/// Optional. Original animation filename as defined by sender
218	pub _file_name: Option<TelegramString>,
219	/// Optional. MIME type of the file as defined by sender
220	pub _mime_type: Option<TelegramString>,
221	/// Optional. File size
222	pub _file_size: Option<TelegramInteger>
223}
224
225/// This object represents a sticker.
226pub struct Sticker{
227	/// Unique identifier for this file
228	pub _file_id: TelegramString,
229	/// Sticker width
230	pub _width: TelegramInteger,
231	/// Sticker height
232	pub _height: TelegramInteger,
233	/// Optional. Sticker thumbnail in the .webp or .jpg format
234	pub _thumb: Option<PhotoSize>,
235	/// Optional. Emoji associated with the sticker
236	pub _emoji: Option<TelegramString>,
237	/// Optional. Name of the sticker set to which the sticker belongs
238	pub _set_name: Option<TelegramString>,
239	/// Optional. For mask stickers, the position where the mask should be placed
240	pub _mask_position: Option<MaskPosition>,
241	/// Optional. File size
242	pub _file_size: Option<TelegramInteger>
243}
244
245/// This object describes the position on faces where a mask should be placed by default.
246pub struct MaskPosition{
247	/// The part of the face relative to which the mask should be placed. One of “forehead”, “eyes”, “mouth”, or “chin”.
248	pub _point: TelegramString,
249	/// Shift by X-axis measured in widths of the mask scaled to the face size, from left to right. For example, choosing -1.0 will place mask just to the left of the default mask position.
250	pub _x_shift: TelegramFloat,
251	/// Shift by Y-axis measured in heights of the mask scaled to the face size, from top to bottom. For example, 1.0 will place the mask just below the default mask position.
252	pub _y_shift: TelegramFloat,
253	/// Mask scaling coefficient. For example, 2.0 means double size.
254	pub _scale: TelegramFloat	
255}
256
257/// This object represents a video file.
258pub struct Video{
259	/// Unique identifier for this file
260	pub _file_id: TelegramString,
261	/// Video width as defined by sender
262	pub _width: TelegramInteger,
263	/// Video height as defined by sender
264	pub _height: TelegramInteger,
265	/// Duration of the video in seconds as defined by sender
266	pub _duration: TelegramInteger,
267	/// Optional. Video thumbnail
268	pub _thumb: Option<PhotoSize>,
269	/// Optional. Mime type of a file as defined by sender
270	pub _mime_type: Option<TelegramString>,
271	/// Optional. File size
272	pub _file_size: Option<TelegramInteger>
273}
274
275/// This object represents a voice note.
276pub struct Voice{
277	/// Unique identifier for this file
278	pub _file_id: TelegramString,
279	/// Duration of the audio in seconds as defined by sender
280	pub _duration: TelegramInteger,
281	/// Optional. MIME type of the file as defined by sender
282	pub _mime_type: Option<TelegramString>,
283	/// Optional. File size
284	pub _file_size: Option<TelegramInteger>
285}
286
287pub struct VideoNote{
288	/// Unique identifier for this file
289	pub _file_id: TelegramString,
290	/// Video width and height as defined by sender
291	pub _length:	TelegramInteger,
292	/// Duration of the video in seconds as defined by sender
293	pub _duration: TelegramInteger,
294	/// Optional. Video thumbnail
295	pub _thumb: Option<PhotoSize>,
296	/// Optional. File size
297	pub _file_size: Option<TelegramInteger>
298}
299
300/// This object represents a phone contact.
301pub struct Contact{
302	/// Contact's phone number
303	pub _phone_number: TelegramString,
304	/// Contact's first name
305	pub _first_name: TelegramString,
306	/// Optional. Contact's last name
307	pub _last_name: Option<TelegramString>,
308	/// Optional. Contact's user identifier in Telegram
309	pub _user_id: Option<TelegramInteger>
310}
311
312/// This object represents a point on the map.
313pub struct Location{
314	/// Longitude as defined by sender
315	pub _longitude: TelegramFloat,
316	/// Latitude as defined by sender
317	pub _latitude: TelegramFloat
318}
319
320/// This object represents a venue.
321pub struct Venue{
322	/// Venue location
323	pub _location: Location,
324	/// Name of the venue
325	pub _title: TelegramString,
326	/// Address of the venue
327	pub _address: TelegramString,
328	/// Optional. Foursquare identifier of the venue
329	pub _foursquare_id: Option<TelegramString>
330}
331
332/// This object contains basic information about an invoice.
333pub struct Invoice{
334	/// Product name
335	pub _title: TelegramString,
336	/// Product description
337	pub _description: TelegramString,
338	/// Unique bot deep-linking parameter that can be used to generate this invoice
339	pub _start_parameter: TelegramString,
340	/// Three-letter ISO 4217 currency code
341	pub _currency: TelegramString,
342	/// Total price in the smallest units of the currency (integer, not float/double). For example, for a price of US$ 1.45 pass amount = 145. See the exp parameter in currencies.json, it shows the number of digits past the decimal point for each currency (2 for the majority of currencies).
343	pub _total_amount: TelegramInteger
344}
345
346/// This object contains basic information about a successful payment.
347pub struct SuccessfulPayment{
348	/// Three-letter ISO 4217 currency code
349	pub _currency: TelegramString,
350	/// Total price in the smallest units of the currency (integer, not float/double). For example, for a price of US$ 1.45 pass amount = 145. See the exp parameter in currencies.json, it shows the number of digits past the decimal point for each currency (2 for the majority of currencies).
351	pub _total_amount: TelegramInteger,
352	/// Bot specified invoice payload
353	pub _invoice_payload: TelegramString,
354	/// Optional. Identifier of the shipping option chosen by the user
355	pub _shipping_option_id: Option<TelegramString>,
356	/// Optional. Order info provided by the user
357	pub _order_info: Option<OrderInfo>,
358	/// Telegram payment identifier
359	pub _telegram_payment_charge_id: TelegramString,
360	/// Provider payment identifier
361	pub _provider_payment_charge_id: TelegramString
362}
363
364/// This object represents information about an order.
365pub struct OrderInfo{
366	/// Optional. User name
367	pub _name: Option<TelegramString>,
368	/// Optional. User's phone number
369	pub _phone_number: Option<TelegramString>,
370	/// Optional. User email
371	pub _email: Option<TelegramString>,
372	/// Optional. User shipping address
373	pub _shipping_address: Option<ShippingAddress>
374}
375
376/// This object represents a shipping address.
377pub struct ShippingAddress{
378	/// ISO 3166-1 alpha-2 country code
379	pub _country_code: TelegramString,
380	/// State, if applicable
381	pub _state: TelegramString,
382	/// City
383	pub _city: TelegramString,
384	/// First line for the address
385	pub _street_line1: TelegramString,
386	/// Second line for the address
387	pub _street_line2: TelegramString,
388	/// Address post code
389	pub _post_code: TelegramString
390}
391
392/// This object represent a user's profile pictures.
393pub struct UserProfilePhotos{
394	/// Total number of profile pictures the target user has
395	pub _total_count: TelegramInteger,
396	/// Array of Array of PhotoSize	Requested profile pictures (in up to 4 sizes each)
397	pub _photos: Vec<Vec<PhotoSize>>
398}
399
400/// This object represents a custom keyboard with reply options (see Introduction to bots for details and examples).
401pub struct ReplyKeyboardMarkup{
402	/// Array of button rows, each represented by an Array of KeyboardButton objects
403	pub _keyboard: Vec<Vec<KeyboardButton>>,
404	/// Boolean	Optional. Requests clients to resize the keyboard vertically for optimal fit (e.g., make the keyboard smaller if there are just two rows of buttons). Defaults to false, in which case the custom keyboard is always of the same height as the app's standard keyboard.
405	pub _resize_keyboard: Option<TelegramBoolean>,
406	/// Optional. Requests clients to hide the keyboard as soon as it's been used. The keyboard will still be available, but clients will automatically display the usual letter-keyboard in the chat – the user can press a special button in the input field to see the custom keyboard again. Defaults to false.
407	pub _one_time_keyboard: Option<TelegramBoolean>,
408	/// Optional. Use this parameter if you want to show the keyboard to specific users only. Targets: 1) users that are @mentioned in the text of the Message object; 2) if the bot's message is a reply (has reply_to_message_id), sender of the original message.
409	/// Example: A user requests to change the bot‘s language, bot replies to the request with a keyboard to select the new language. Other users in the group don’t see the keyboard.
410	pub _selective: Option<TelegramBoolean>
411}
412
413/// This object represents one button of the reply keyboard. For simple text buttons String can be used instead of this object to specify text of the button. Optional fields are mutually exclusive.
414pub struct KeyboardButton{
415	/// Text of the button. If none of the optional fields are used, it will be sent to the bot as a message when the button is pressed
416	pub _text: TelegramString,
417	/// Optional. If True, the user's phone number will be sent as a contact when the button is pressed. Available in private chats only
418	pub _request_contact: Option<TelegramBoolean>,
419	/// Optional. If True, the user's current location will be sent when the button is pressed. Available in private chats only
420	pub _request_location: Option<TelegramBoolean>
421}
422
423/// Upon receiving a message with this object, Telegram clients will remove the current custom keyboard and display the default letter-keyboard. By default, custom keyboards are displayed until a new keyboard is sent by a bot. An exception is made for one-time keyboards that are hidden immediately after the user presses a button (see ReplyKeyboardMarkup).
424pub struct ReplyKeyboardRemove{
425	/// Requests clients to remove the custom keyboard (user will not be able to summon this keyboard; if you want to hide the keyboard from sight but keep it accessible, use one_time_keyboard in ReplyKeyboardMarkup)
426	pub _remove_keyboard: TelegramTrue,
427	/// Optional. Use this parameter if you want to remove the keyboard for specific users only. Targets: 1) users that are @mentioned in the text of the Message object; 2) if the bot's message is a reply (has reply_to_message_id), sender of the original message.
428	/// Example: A user votes in a poll, bot returns confirmation message in reply to the vote and removes the keyboard for that user, while still showing the keyboard with poll options to users who haven't voted yet.
429	pub _selective: Option<TelegramBoolean>
430}
431
432/// This object represents an inline keyboard that appears right next to the message it belongs to.
433pub struct InlineKeyboardMarkup{
434	/// Array of button rows, each represented by an Array of InlineKeyboardButton objects
435	pub _inline_keyboard: Vec<Vec<InlineKeyboardButton>>
436}
437
438/// This object represents one button of an inline keyboard. You must use exactly one of the optional fields.
439pub struct InlineKeyboardButton{
440	/// Label text on the button
441	pub _text:TelegramString,
442	/// Optional. HTTP url to be opened when button is pressed
443	pub _url: Option<TelegramString>,
444	/// Optional. Data to be sent in a callback query to the bot when button is pressed, 1-64 bytes
445	pub _callback_data: Option<TelegramString>,
446	/// Optional. If set, pressing the button will prompt the user to select one of their chats, open that chat and insert the bot‘s username and the specified inline query in the input field. Can be empty, in which case just the bot’s username will be inserted.
447	/// Note: This offers an easy way for users to start using your bot in inline mode when they are currently in a private chat with it. Especially useful when combined with switch_pm… actions – in this case the user will be automatically returned to the chat they switched from, skipping the chat selection screen.
448	pub _switch_inline_query: Option<TelegramString>,
449	/// Optional. If set, pressing the button will insert the bot‘s username and the specified inline query in the current chat's input field. Can be empty, in which case only the bot’s username will be inserted.
450	/// This offers a quick way for the user to open your bot in inline mode in the same chat – good for selecting something from multiple options.
451	pub _switch_inline_query_current_chat: Option<TelegramString>,
452	/// Optional. Description of the game that will be launched when the user presses the button.
453	/// NOTE: This type of button must always be the first button in the first row.
454	pub _callback_game: Option<CallbackGame>,
455	/// Optional. Specify True, to send a Pay button.
456	/// NOTE: This type of button must always be the first button in the first row.
457	pub _pay: Option<TelegramBoolean>
458}
459
460/// A placeholder, currently holds no information. Use BotFather to set up your game.
461pub struct CallbackGame{
462}
463
464/// This object represents an incoming callback query from a callback button in an inline keyboard. If the button that originated the query was attached to a message sent by the bot, the field message will be present. If the button was attached to a message sent via the bot (in inline mode), the field inline_message_id will be present. Exactly one of the fields data or game_short_name will be present.
465pub struct CallbackQuery{
466	/// Unique identifier for this query
467	pub _id: TelegramString,
468	/// Sender
469	pub _from: User,
470	/// Optional. Message with the callback button that originated the query. Note that message content and message date will not be available if the message is too old
471	pub _message: Option<Message>,
472	/// Optional. Identifier of the message sent via the bot in inline mode, that originated the query.
473	pub _inline_message_id: Option<TelegramString>,
474	/// Global identifier, uniquely corresponding to the chat to which the message with the callback button was sent. Useful for high scores in games.
475	pub _chat_instance: TelegramString,
476	/// Optional. Data associated with the callback button. Be aware that a bad client can send arbitrary data in this field.
477	pub _data: Option<TelegramString>,
478	/// Optional. Short name of a Game to be returned, serves as the unique identifier for the game
479	pub _game_short_name: Option<TelegramString>
480}
481
482/// Upon receiving a message with this object, Telegram clients will display a reply interface to the user (act as if the user has selected the bot‘s message and tapped ’Reply'). This can be extremely useful if you want to create user-friendly step-by-step interfaces without having to sacrifice privacy mode.
483pub struct ForceReply{
484	/// Shows reply interface to the user, as if they manually selected the bot‘s message and tapped ’Reply'
485	pub force_reply: TelegramTrue,
486	/// Optional. Use this parameter if you want to force reply from specific users only. Targets: 1) users that are @mentioned in the text of the Message object; 2) if the bot's message is a reply (has reply_to_message_id), sender of the original message.
487	pub selective: Option<TelegramBoolean>
488}
489
490/// This object contains information about one member of a chat.
491pub struct ChatMember{
492	/// Information about the user
493	pub _user: User,
494	/// The member's status in the chat. Can be “creator”, “administrator”, “member”, “restricted”, “left” or “kicked”
495	pub _status: TelegramString,
496	/// Optional. Restictred and kicked only. Date when restrictions will be lifted for this user, unix time
497	pub _until_date: Option<TelegramInteger>,
498	/// Optional. Administrators only. True, if the bot is allowed to edit administrator privileges of that user
499	pub _can_be_edited: Option<TelegramBoolean>,
500	/// Optional. Administrators only. True, if the administrator can change the chat title, photo and other settings
501	pub _can_change_info: Option<TelegramBoolean>,
502	/// Optional. Administrators only. True, if the administrator can post in the channel, channels only
503	pub _can_post_messages: Option<TelegramBoolean>,
504	/// Optional. Administrators only. True, if the administrator can edit messages of other users, channels only
505	pub _can_edit_messages: Option<TelegramBoolean>,
506	/// Optional. Administrators only. True, if the administrator can delete messages of other users
507	pub _can_delete_messages: Option<TelegramBoolean>,
508	/// Optional. Administrators only. True, if the administrator can invite new users to the chat
509	pub _can_invite_users: Option<TelegramBoolean>,
510	/// Optional. Administrators only. True, if the administrator can restrict, ban or unban chat members
511	pub _can_restrict_members: Option<TelegramBoolean>,
512	/// Optional. Administrators only. True, if the administrator can pin messages, supergroups only
513	pub _can_pin_messages: Option<TelegramBoolean>,
514	/// Optional. Administrators only. True, if the administrator can add new administrators with a subset of his own privileges or demote administrators that he has promoted, directly or indirectly (promoted by administrators that were appointed by the user)
515	pub _can_promote_members: Option<TelegramBoolean>,
516	/// Optional. Restricted only. True, if the user can send text messages, contacts, locations and venues
517	pub _can_send_messages: Option<TelegramBoolean>,
518	/// Optional. Restricted only. True, if the user can send audios, documents, photos, videos, video notes and voice notes, implies can_send_messages
519	pub _can_send_media_messages: Option<TelegramBoolean>,
520	/// Optional. Restricted only. True, if the user can send animations, games, stickers and use inline bots, implies can_send_media_messages
521	pub _can_send_other_messages: Option<TelegramBoolean>,
522	/// Optional. Restricted only. True, if user may add web page previews to his messages, implies can_send_media_messages
523	pub _can_add_web_page_previews: Option<TelegramBoolean>
524}
525
526/// Contains information about why a request was unsuccessfull.
527pub struct ResponseParameters{
528	/// Optional. The group has been migrated to a supergroup with the specified identifier. This number may be greater than 32 bits and some programming languages may have difficulty/silent defects in interpreting it. But it is smaller than 52 bits, so a signed 64 bit integer or double-precision float type are safe for storing this identifier.
529	pub _migrate_to_chat_id: Option<TelegramInteger>,
530	/// Optional. In case of exceeding flood control, the number of seconds left to wait before the request can be repeated
531	pub _retry_after: Option<TelegramInteger>
532}