feat: update to bot api 10.3

Author: Eptagone

README.md

@@ -2,18 +2,18 @@
 | -------------------------------------------------- | ------------------------ |
 
 [![NuGet version (Telegram.BotAPI)](https://img.shields.io/nuget/v/Telegram.BotAPI?style=flat-square&logo=nuget)](https://www.nuget.org/packages/Telegram.BotAPI/)
-[![Compatible with Bot API v10.2](https://img.shields.io/badge/Bot%20API%20version-v10.2-blue?style=flat-square)](https://core.telegram.org/bots/api#july-14-2026)
+[![Compatible with Bot API v10.3](https://img.shields.io/badge/Bot%20API%20version-v10.3-blue?style=flat-square)](https://core.telegram.org/bots/api#august-24-2026)
 
-**Telegram.BotAPI** is one of the most complete libraries available to interact with the Telegram Bot API in your .NET projects. It contains all the methods and types available in the Bot API 10.2 released on July 14, 2026.
+**Telegram.BotAPI** is one of the most complete libraries available to interact with the Telegram Bot API in your .NET projects. It contains all the methods and types available in the Bot API 10.3 released on August 24, 2026.
 
 [![Telegram Chat](https://img.shields.io/badge/Telegram.BotAPI%20--%20Chat-Join-blue?style=social&logo=telegram)](https://t.me/TBAPINET)
 
 ---
 
 ## Features
 
-- Contains pre-defined methods for all Bot API 10.2 methods.
-- Contains classes for each object type used in the Bot API 10.2.
+- Contains pre-defined methods for all Bot API 10.3 methods.
+- Contains classes for each object type used in the Bot API 10.3.
 - Sync and async methods.
 - Uses [System.Text.Json](https://www.nuget.org/packages/System.Text.Json/).
 

src/examples/readme.md

@@ -1,7 +1,7 @@
 # Telegram.BotAPI NET Examples
 
 [![NuGet version (Telegram.BotAPI)](https://img.shields.io/nuget/v/Telegram.BotAPI?style=flat-square&logo=nuget)](https://www.nuget.org/packages/Telegram.BotAPI/)
-[![Compatible with Bot API v10.2](https://img.shields.io/badge/Bot%20API%20version-v10.2-blue?style=flat-square)](https://core.telegram.org/bots/api#july-14-2026)
+[![Compatible with Bot API v10.3](https://img.shields.io/badge/Bot%20API%20version-v10.3-blue?style=flat-square)](https://core.telegram.org/bots/api#august-24-2026)
 
 ## Sample list
 

src/library/Telegram.BotAPI/AvailableMethods/Args/AnswerCallbackQueryArgs.cs

@@ -45,7 +45,7 @@ public AnswerCallbackQueryArgs(string callbackQueryId)
     public string? Url { get; set; }
 
     /// <summary>
-    /// The maximum amount of time in seconds that the result of the callback query may be cached client-side. Telegram apps will support caching starting in version 3.14. Defaults to 0.
+    /// The maximum amount of time in seconds that the result of the callback query may be cached client-side. Defaults to 0.
     /// </summary>
     [JsonPropertyName(PropertyNames.CacheTime)]
     public int? CacheTime { get; set; }

src/library/Telegram.BotAPI/AvailableMethods/Args/PromoteChatMemberArgs.cs

@@ -144,4 +144,10 @@ public PromoteChatMemberArgs(string chatId, long userId)
     /// </summary>
     [JsonPropertyName(PropertyNames.CanManageTags)]
     public bool? CanManageTags { get; set; }
+
+    /// <summary>
+    /// Pass <em>True</em> if the administrator can manage chat welcome messages or directly send them in the case of bots
+    /// </summary>
+    [JsonPropertyName(PropertyNames.CanSendWelcomeMessages)]
+    public bool? CanSendWelcomeMessages { get; set; }
 }

src/library/Telegram.BotAPI/AvailableMethods/Args/SendAnimationArgs.cs

@@ -80,16 +80,10 @@ public SendAnimationArgs(string chatId, string animation)
     public int? DirectMessagesTopicId { get; set; }
 
     /// <summary>
-    /// For outgoing ephemeral messages, unique identifier of the user who will receive the message; for group and supergroup chats only. It is not guaranteed that the user will receive the message, especially if they are offline. See <a href="https://core.telegram.org/bots/api#ephemeral-messages-and-commands">ephemeral message sending</a> for more details.
+    /// A JSON-serialized object containing the parameters of the ephemeral message to send
     /// </summary>
-    [JsonPropertyName(PropertyNames.ReceiverUserId)]
-    public long? ReceiverUserId { get; set; }
-
-    /// <summary>
-    /// For outgoing ephemeral messages, identifier of the callback query which triggerred the message if any
-    /// </summary>
-    [JsonPropertyName(PropertyNames.CallbackQueryId)]
-    public string? CallbackQueryId { get; set; }
+    [JsonPropertyName(PropertyNames.EphemeralMessageParameters)]
+    public EphemeralMessageParameters? EphemeralMessageParameters { get; set; }
 
     /// <summary>
     /// Animation to send. Pass a file_id as String to send an animation that exists on the Telegram servers (recommended), pass an HTTP URL as a String for Telegram to get an animation from the Internet, or upload a new animation using multipart/form-data. <a href="https://core.telegram.org/bots/api#sending-files">More information on Sending Files »</a>

src/library/Telegram.BotAPI/AvailableMethods/Args/SendAudioArgs.cs

@@ -80,16 +80,10 @@ public SendAudioArgs(string chatId, string audio)
     public int? DirectMessagesTopicId { get; set; }
 
     /// <summary>
-    /// For outgoing ephemeral messages, unique identifier of the user who will receive the message; for group and supergroup chats only. It is not guaranteed that the user will receive the message, especially if they are offline. See <a href="https://core.telegram.org/bots/api#ephemeral-messages-and-commands">ephemeral message sending</a> for more details.
+    /// A JSON-serialized object containing the parameters of the ephemeral message to send
     /// </summary>
-    [JsonPropertyName(PropertyNames.ReceiverUserId)]
-    public long? ReceiverUserId { get; set; }
-
-    /// <summary>
-    /// For outgoing ephemeral messages, identifier of the callback query which triggerred the message if any
-    /// </summary>
-    [JsonPropertyName(PropertyNames.CallbackQueryId)]
-    public string? CallbackQueryId { get; set; }
+    [JsonPropertyName(PropertyNames.EphemeralMessageParameters)]
+    public EphemeralMessageParameters? EphemeralMessageParameters { get; set; }
 
     /// <summary>
     /// Audio file to send. Pass a file_id as String to send an audio file that exists on the Telegram servers (recommended), pass an HTTP URL as a String for Telegram to get an audio file from the Internet, or upload a new one using multipart/form-data. <a href="https://core.telegram.org/bots/api#sending-files">More information on Sending Files »</a>

src/library/Telegram.BotAPI/AvailableMethods/Args/SendContactArgs.cs

@@ -62,16 +62,10 @@ public SendContactArgs(string chatId, string phoneNumber, string firstName)
     public int? DirectMessagesTopicId { get; set; }
 
     /// <summary>
-    /// For outgoing ephemeral messages, unique identifier of the user who will receive the message; for group and supergroup chats only. It is not guaranteed that the user will receive the message, especially if they are offline. See <a href="https://core.telegram.org/bots/api#ephemeral-messages-and-commands">ephemeral message sending</a> for more details.
+    /// A JSON-serialized object containing the parameters of the ephemeral message to send
     /// </summary>
-    [JsonPropertyName(PropertyNames.ReceiverUserId)]
-    public long? ReceiverUserId { get; set; }
-
-    /// <summary>
-    /// For outgoing ephemeral messages, identifier of the callback query which triggerred the message if any
-    /// </summary>
-    [JsonPropertyName(PropertyNames.CallbackQueryId)]
-    public string? CallbackQueryId { get; set; }
+    [JsonPropertyName(PropertyNames.EphemeralMessageParameters)]
+    public EphemeralMessageParameters? EphemeralMessageParameters { get; set; }
 
     /// <summary>
     /// Contact's phone number

src/library/Telegram.BotAPI/AvailableMethods/Args/SendDocumentArgs.cs

@@ -80,16 +80,10 @@ public SendDocumentArgs(string chatId, string document)
     public int? DirectMessagesTopicId { get; set; }
 
     /// <summary>
-    /// For outgoing ephemeral messages, unique identifier of the user who will receive the message; for group and supergroup chats only. It is not guaranteed that the user will receive the message, especially if they are offline. See <a href="https://core.telegram.org/bots/api#ephemeral-messages-and-commands">ephemeral message sending</a> for more details.
+    /// A JSON-serialized object containing the parameters of the ephemeral message to send
     /// </summary>
-    [JsonPropertyName(PropertyNames.ReceiverUserId)]
-    public long? ReceiverUserId { get; set; }
-
-    /// <summary>
-    /// For outgoing ephemeral messages, identifier of the callback query which triggerred the message if any
-    /// </summary>
-    [JsonPropertyName(PropertyNames.CallbackQueryId)]
-    public string? CallbackQueryId { get; set; }
+    [JsonPropertyName(PropertyNames.EphemeralMessageParameters)]
+    public EphemeralMessageParameters? EphemeralMessageParameters { get; set; }
 
     /// <summary>
     /// File to send. Pass a file_id as String to send a file that exists on the Telegram servers (recommended), pass an HTTP URL as a String for Telegram to get a file from the Internet, or upload a new one using multipart/form-data. <a href="https://core.telegram.org/bots/api#sending-files">More information on Sending Files »</a>

src/library/Telegram.BotAPI/AvailableMethods/Args/SendLivePhotoArgs.cs

@@ -140,16 +140,10 @@ public SendLivePhotoArgs(string chatId, string livePhoto, string photo)
     public int? DirectMessagesTopicId { get; set; }
 
     /// <summary>
-    /// For outgoing ephemeral messages, unique identifier of the user who will receive the message; for group and supergroup chats only. It is not guaranteed that the user will receive the message, especially if they are offline. See <a href="https://core.telegram.org/bots/api#ephemeral-messages-and-commands">ephemeral message sending</a> for more details.
+    /// A JSON-serialized object containing the parameters of the ephemeral message to send
     /// </summary>
-    [JsonPropertyName(PropertyNames.ReceiverUserId)]
-    public long? ReceiverUserId { get; set; }
-
-    /// <summary>
-    /// For outgoing ephemeral messages, identifier of the callback query which triggerred the message if any
-    /// </summary>
-    [JsonPropertyName(PropertyNames.CallbackQueryId)]
-    public string? CallbackQueryId { get; set; }
+    [JsonPropertyName(PropertyNames.EphemeralMessageParameters)]
+    public EphemeralMessageParameters? EphemeralMessageParameters { get; set; }
 
     /// <summary>
     /// Live photo video to send. The video must be no longer than 10 seconds and must not exceed 10 MB in size. Pass a file_id as String to send a video that exists on the Telegram servers (recommended) or upload a new video using multipart/form-data. <a href="https://core.telegram.org/bots/api#sending-files">More information on Sending Files »</a>. Sending live photos by a URL is currently unsupported.

src/library/Telegram.BotAPI/AvailableMethods/Args/SendLocationArgs.cs

@@ -62,16 +62,10 @@ public SendLocationArgs(string chatId, float latitude, float longitude)
     public int? DirectMessagesTopicId { get; set; }
 
     /// <summary>
-    /// For outgoing ephemeral messages, unique identifier of the user who will receive the message; for group and supergroup chats only. It is not guaranteed that the user will receive the message, especially if they are offline. See <a href="https://core.telegram.org/bots/api#ephemeral-messages-and-commands">ephemeral message sending</a> for more details.
+    /// A JSON-serialized object containing the parameters of the ephemeral message to send
     /// </summary>
-    [JsonPropertyName(PropertyNames.ReceiverUserId)]
-    public long? ReceiverUserId { get; set; }
-
-    /// <summary>
-    /// For outgoing ephemeral messages, identifier of the callback query which triggerred the message if any
-    /// </summary>
-    [JsonPropertyName(PropertyNames.CallbackQueryId)]
-    public string? CallbackQueryId { get; set; }
+    [JsonPropertyName(PropertyNames.EphemeralMessageParameters)]
+    public EphemeralMessageParameters? EphemeralMessageParameters { get; set; }
 
     /// <summary>
     /// Latitude of the location