diff --git a/src/libs/Vercel/Generated/Vercel.IMarketplaceClient.SubmitInvoice.g.cs b/src/libs/Vercel/Generated/Vercel.IMarketplaceClient.SubmitInvoice.g.cs
index 7d403fcb..91911673 100644
--- a/src/libs/Vercel/Generated/Vercel.IMarketplaceClient.SubmitInvoice.g.cs
+++ b/src/libs/Vercel/Generated/Vercel.IMarketplaceClient.SubmitInvoice.g.cs
@@ -6,7 +6,7 @@ public partial interface IMarketplaceClient
     {
         /// <summary>
         /// Submit Invoice<br/>
-        /// This endpoint allows the partner to submit an invoice to Vercel. The invoice is created in Vercel's billing system and sent to the customer. Depending on the type of billing plan, the invoice can be sent at a time of signup, at the start of the billing period, or at the end of the billing period.&lt;br/&gt; &lt;br/&gt; Use the `credentials.access_token` we provided in the [Upsert Installation](#upsert-installation) body to authorize this request. &lt;br/&gt; There are several limitations to the invoice submission:&lt;br/&gt; &lt;br/&gt; 1. A resource can only be billed once per the billing period and the billing plan.&lt;br/&gt; 2. The billing plan used to bill the resource must have been active for this resource during the billing period.&lt;br/&gt; 3. The billing plan used must be a subscription plan.&lt;br/&gt; 4. The interim usage data must be sent hourly for all types of subscriptions. See [Send subscription billing and usage data](#send-subscription-billing-and-usage-data) API on how to send interim billing and usage data.&lt;br/&gt;
+        /// This endpoint allows the partner to submit an invoice to Vercel. The invoice is created in Vercel's billing system and sent to the customer. Depending on the type of billing plan, the invoice can be sent at a time of signup, at the start of the billing period, or at the end of the billing period.&lt;br/&gt; &lt;br/&gt; Use the `credentials.access_token` we provided in the [Upsert Installation](#upsert-installation) body to authorize this request. &lt;br/&gt; There are several limitations to the invoice submission:&lt;br/&gt; &lt;br/&gt; 1. A resource can only be billed once per the billing period and the billing plan.&lt;br/&gt; 2. The billing plan used to bill the resource must have been active for this resource during the billing period.&lt;br/&gt; 3. The billing plan used must be a subscription plan.&lt;br/&gt; 4. The interim usage data must be sent hourly for all types of subscriptions. See [Send subscription billing and usage data](#send-subscription-billing-and-usage-data) API on how to send interim billing and usage data.&lt;br/&gt; 5. If provided, `externalId` must be unique for the installation.&lt;br/&gt;
         /// </summary>
         /// <param name="integrationConfigurationId"></param>
         /// <param name="request"></param>
@@ -21,7 +21,7 @@ public partial interface IMarketplaceClient
             global::System.Threading.CancellationToken cancellationToken = default);
         /// <summary>
         /// Submit Invoice<br/>
-        /// This endpoint allows the partner to submit an invoice to Vercel. The invoice is created in Vercel's billing system and sent to the customer. Depending on the type of billing plan, the invoice can be sent at a time of signup, at the start of the billing period, or at the end of the billing period.&lt;br/&gt; &lt;br/&gt; Use the `credentials.access_token` we provided in the [Upsert Installation](#upsert-installation) body to authorize this request. &lt;br/&gt; There are several limitations to the invoice submission:&lt;br/&gt; &lt;br/&gt; 1. A resource can only be billed once per the billing period and the billing plan.&lt;br/&gt; 2. The billing plan used to bill the resource must have been active for this resource during the billing period.&lt;br/&gt; 3. The billing plan used must be a subscription plan.&lt;br/&gt; 4. The interim usage data must be sent hourly for all types of subscriptions. See [Send subscription billing and usage data](#send-subscription-billing-and-usage-data) API on how to send interim billing and usage data.&lt;br/&gt;
+        /// This endpoint allows the partner to submit an invoice to Vercel. The invoice is created in Vercel's billing system and sent to the customer. Depending on the type of billing plan, the invoice can be sent at a time of signup, at the start of the billing period, or at the end of the billing period.&lt;br/&gt; &lt;br/&gt; Use the `credentials.access_token` we provided in the [Upsert Installation](#upsert-installation) body to authorize this request. &lt;br/&gt; There are several limitations to the invoice submission:&lt;br/&gt; &lt;br/&gt; 1. A resource can only be billed once per the billing period and the billing plan.&lt;br/&gt; 2. The billing plan used to bill the resource must have been active for this resource during the billing period.&lt;br/&gt; 3. The billing plan used must be a subscription plan.&lt;br/&gt; 4. The interim usage data must be sent hourly for all types of subscriptions. See [Send subscription billing and usage data](#send-subscription-billing-and-usage-data) API on how to send interim billing and usage data.&lt;br/&gt; 5. If provided, `externalId` must be unique for the installation.&lt;br/&gt;
         /// </summary>
         /// <param name="integrationConfigurationId"></param>
         /// <param name="request"></param>
@@ -36,10 +36,12 @@ public partial interface IMarketplaceClient
             global::System.Threading.CancellationToken cancellationToken = default);
         /// <summary>
         /// Submit Invoice<br/>
-        /// This endpoint allows the partner to submit an invoice to Vercel. The invoice is created in Vercel's billing system and sent to the customer. Depending on the type of billing plan, the invoice can be sent at a time of signup, at the start of the billing period, or at the end of the billing period.&lt;br/&gt; &lt;br/&gt; Use the `credentials.access_token` we provided in the [Upsert Installation](#upsert-installation) body to authorize this request. &lt;br/&gt; There are several limitations to the invoice submission:&lt;br/&gt; &lt;br/&gt; 1. A resource can only be billed once per the billing period and the billing plan.&lt;br/&gt; 2. The billing plan used to bill the resource must have been active for this resource during the billing period.&lt;br/&gt; 3. The billing plan used must be a subscription plan.&lt;br/&gt; 4. The interim usage data must be sent hourly for all types of subscriptions. See [Send subscription billing and usage data](#send-subscription-billing-and-usage-data) API on how to send interim billing and usage data.&lt;br/&gt;
+        /// This endpoint allows the partner to submit an invoice to Vercel. The invoice is created in Vercel's billing system and sent to the customer. Depending on the type of billing plan, the invoice can be sent at a time of signup, at the start of the billing period, or at the end of the billing period.&lt;br/&gt; &lt;br/&gt; Use the `credentials.access_token` we provided in the [Upsert Installation](#upsert-installation) body to authorize this request. &lt;br/&gt; There are several limitations to the invoice submission:&lt;br/&gt; &lt;br/&gt; 1. A resource can only be billed once per the billing period and the billing plan.&lt;br/&gt; 2. The billing plan used to bill the resource must have been active for this resource during the billing period.&lt;br/&gt; 3. The billing plan used must be a subscription plan.&lt;br/&gt; 4. The interim usage data must be sent hourly for all types of subscriptions. See [Send subscription billing and usage data](#send-subscription-billing-and-usage-data) API on how to send interim billing and usage data.&lt;br/&gt; 5. If provided, `externalId` must be unique for the installation.&lt;br/&gt;
         /// </summary>
         /// <param name="integrationConfigurationId"></param>
-        /// <param name="externalId"></param>
+        /// <param name="externalId">
+        /// Partner-provided invoice identifier. If provided, it must be unique for this installation.
+        /// </param>
         /// <param name="invoiceDate">
         /// Invoice date. Must be within the period's start and end.
         /// </param>
diff --git a/src/libs/Vercel/Generated/Vercel.MarketplaceClient.SubmitInvoice.g.cs b/src/libs/Vercel/Generated/Vercel.MarketplaceClient.SubmitInvoice.g.cs
index da0c53be..9c1aaf88 100644
--- a/src/libs/Vercel/Generated/Vercel.MarketplaceClient.SubmitInvoice.g.cs
+++ b/src/libs/Vercel/Generated/Vercel.MarketplaceClient.SubmitInvoice.g.cs
@@ -45,7 +45,7 @@ partial void ProcessSubmitInvoiceResponseContent(
 
         /// <summary>
         /// Submit Invoice<br/>
-        /// This endpoint allows the partner to submit an invoice to Vercel. The invoice is created in Vercel's billing system and sent to the customer. Depending on the type of billing plan, the invoice can be sent at a time of signup, at the start of the billing period, or at the end of the billing period.&lt;br/&gt; &lt;br/&gt; Use the `credentials.access_token` we provided in the [Upsert Installation](#upsert-installation) body to authorize this request. &lt;br/&gt; There are several limitations to the invoice submission:&lt;br/&gt; &lt;br/&gt; 1. A resource can only be billed once per the billing period and the billing plan.&lt;br/&gt; 2. The billing plan used to bill the resource must have been active for this resource during the billing period.&lt;br/&gt; 3. The billing plan used must be a subscription plan.&lt;br/&gt; 4. The interim usage data must be sent hourly for all types of subscriptions. See [Send subscription billing and usage data](#send-subscription-billing-and-usage-data) API on how to send interim billing and usage data.&lt;br/&gt;
+        /// This endpoint allows the partner to submit an invoice to Vercel. The invoice is created in Vercel's billing system and sent to the customer. Depending on the type of billing plan, the invoice can be sent at a time of signup, at the start of the billing period, or at the end of the billing period.&lt;br/&gt; &lt;br/&gt; Use the `credentials.access_token` we provided in the [Upsert Installation](#upsert-installation) body to authorize this request. &lt;br/&gt; There are several limitations to the invoice submission:&lt;br/&gt; &lt;br/&gt; 1. A resource can only be billed once per the billing period and the billing plan.&lt;br/&gt; 2. The billing plan used to bill the resource must have been active for this resource during the billing period.&lt;br/&gt; 3. The billing plan used must be a subscription plan.&lt;br/&gt; 4. The interim usage data must be sent hourly for all types of subscriptions. See [Send subscription billing and usage data](#send-subscription-billing-and-usage-data) API on how to send interim billing and usage data.&lt;br/&gt; 5. If provided, `externalId` must be unique for the installation.&lt;br/&gt;
         /// </summary>
         /// <param name="integrationConfigurationId"></param>
         /// <param name="request"></param>
@@ -71,7 +71,7 @@ partial void ProcessSubmitInvoiceResponseContent(
         }
         /// <summary>
         /// Submit Invoice<br/>
-        /// This endpoint allows the partner to submit an invoice to Vercel. The invoice is created in Vercel's billing system and sent to the customer. Depending on the type of billing plan, the invoice can be sent at a time of signup, at the start of the billing period, or at the end of the billing period.&lt;br/&gt; &lt;br/&gt; Use the `credentials.access_token` we provided in the [Upsert Installation](#upsert-installation) body to authorize this request. &lt;br/&gt; There are several limitations to the invoice submission:&lt;br/&gt; &lt;br/&gt; 1. A resource can only be billed once per the billing period and the billing plan.&lt;br/&gt; 2. The billing plan used to bill the resource must have been active for this resource during the billing period.&lt;br/&gt; 3. The billing plan used must be a subscription plan.&lt;br/&gt; 4. The interim usage data must be sent hourly for all types of subscriptions. See [Send subscription billing and usage data](#send-subscription-billing-and-usage-data) API on how to send interim billing and usage data.&lt;br/&gt;
+        /// This endpoint allows the partner to submit an invoice to Vercel. The invoice is created in Vercel's billing system and sent to the customer. Depending on the type of billing plan, the invoice can be sent at a time of signup, at the start of the billing period, or at the end of the billing period.&lt;br/&gt; &lt;br/&gt; Use the `credentials.access_token` we provided in the [Upsert Installation](#upsert-installation) body to authorize this request. &lt;br/&gt; There are several limitations to the invoice submission:&lt;br/&gt; &lt;br/&gt; 1. A resource can only be billed once per the billing period and the billing plan.&lt;br/&gt; 2. The billing plan used to bill the resource must have been active for this resource during the billing period.&lt;br/&gt; 3. The billing plan used must be a subscription plan.&lt;br/&gt; 4. The interim usage data must be sent hourly for all types of subscriptions. See [Send subscription billing and usage data](#send-subscription-billing-and-usage-data) API on how to send interim billing and usage data.&lt;br/&gt; 5. If provided, `externalId` must be unique for the installation.&lt;br/&gt;
         /// </summary>
         /// <param name="integrationConfigurationId"></param>
         /// <param name="request"></param>
@@ -604,10 +604,12 @@ partial void ProcessSubmitInvoiceResponseContent(
         }
         /// <summary>
         /// Submit Invoice<br/>
-        /// This endpoint allows the partner to submit an invoice to Vercel. The invoice is created in Vercel's billing system and sent to the customer. Depending on the type of billing plan, the invoice can be sent at a time of signup, at the start of the billing period, or at the end of the billing period.&lt;br/&gt; &lt;br/&gt; Use the `credentials.access_token` we provided in the [Upsert Installation](#upsert-installation) body to authorize this request. &lt;br/&gt; There are several limitations to the invoice submission:&lt;br/&gt; &lt;br/&gt; 1. A resource can only be billed once per the billing period and the billing plan.&lt;br/&gt; 2. The billing plan used to bill the resource must have been active for this resource during the billing period.&lt;br/&gt; 3. The billing plan used must be a subscription plan.&lt;br/&gt; 4. The interim usage data must be sent hourly for all types of subscriptions. See [Send subscription billing and usage data](#send-subscription-billing-and-usage-data) API on how to send interim billing and usage data.&lt;br/&gt;
+        /// This endpoint allows the partner to submit an invoice to Vercel. The invoice is created in Vercel's billing system and sent to the customer. Depending on the type of billing plan, the invoice can be sent at a time of signup, at the start of the billing period, or at the end of the billing period.&lt;br/&gt; &lt;br/&gt; Use the `credentials.access_token` we provided in the [Upsert Installation](#upsert-installation) body to authorize this request. &lt;br/&gt; There are several limitations to the invoice submission:&lt;br/&gt; &lt;br/&gt; 1. A resource can only be billed once per the billing period and the billing plan.&lt;br/&gt; 2. The billing plan used to bill the resource must have been active for this resource during the billing period.&lt;br/&gt; 3. The billing plan used must be a subscription plan.&lt;br/&gt; 4. The interim usage data must be sent hourly for all types of subscriptions. See [Send subscription billing and usage data](#send-subscription-billing-and-usage-data) API on how to send interim billing and usage data.&lt;br/&gt; 5. If provided, `externalId` must be unique for the installation.&lt;br/&gt;
         /// </summary>
         /// <param name="integrationConfigurationId"></param>
-        /// <param name="externalId"></param>
+        /// <param name="externalId">
+        /// Partner-provided invoice identifier. If provided, it must be unique for this installation.
+        /// </param>
         /// <param name="invoiceDate">
         /// Invoice date. Must be within the period's start and end.
         /// </param>
diff --git a/src/libs/Vercel/Generated/Vercel.Models.SubmitInvoiceRequest.g.cs b/src/libs/Vercel/Generated/Vercel.Models.SubmitInvoiceRequest.g.cs
index 296716b8..1a8986f7 100644
--- a/src/libs/Vercel/Generated/Vercel.Models.SubmitInvoiceRequest.g.cs
+++ b/src/libs/Vercel/Generated/Vercel.Models.SubmitInvoiceRequest.g.cs
@@ -9,7 +9,7 @@ namespace Vercel
     public sealed partial class SubmitInvoiceRequest
     {
         /// <summary>
-        /// 
+        /// Partner-provided invoice identifier. If provided, it must be unique for this installation.
         /// </summary>
         [global::System.Text.Json.Serialization.JsonPropertyName("externalId")]
         public string? ExternalId { get; set; }
@@ -75,7 +75,9 @@ public sealed partial class SubmitInvoiceRequest
         /// Subscription period for this billing cycle.
         /// </param>
         /// <param name="items"></param>
-        /// <param name="externalId"></param>
+        /// <param name="externalId">
+        /// Partner-provided invoice identifier. If provided, it must be unique for this installation.
+        /// </param>
         /// <param name="memo">
         /// Additional memo for the invoice.
         /// </param>
diff --git a/src/libs/Vercel/Generated/Vercel.ProjectsClient.UpdateProject.g.cs b/src/libs/Vercel/Generated/Vercel.ProjectsClient.UpdateProject.g.cs
index e5ddbcbe..d7c97d8f 100644
--- a/src/libs/Vercel/Generated/Vercel.ProjectsClient.UpdateProject.g.cs
+++ b/src/libs/Vercel/Generated/Vercel.ProjectsClient.UpdateProject.g.cs
@@ -577,38 +577,6 @@ partial void ProcessUpdateProjectResponseContent(
                                         h => h.Value));
                             }
                             // 
-                            if ((int)__response.StatusCode == 422)
-                            {
-                                string? __content_422 = null;
-                                global::System.Exception? __exception_422 = null;
-                                try
-                                {
-                                    if (__effectiveReadResponseAsString)
-                                    {
-                                        __content_422 = await __response.Content.ReadAsStringAsync(__effectiveCancellationToken).ConfigureAwait(false);
-                                    }
-                                    else
-                                    {
-                                        __content_422 = await __response.Content.ReadAsStringAsync(__effectiveCancellationToken).ConfigureAwait(false);
-                                    }
-                                }
-                                catch (global::System.Exception __ex)
-                                {
-                                    __exception_422 = __ex;
-                                }
-
-
-                                throw global::Vercel.ApiException.Create(
-                                    statusCode: __response.StatusCode,
-                                    message: __content_422 ?? __response.ReasonPhrase ?? string.Empty,
-                                    innerException: __exception_422,
-                                    responseBody: __content_422,
-                                    responseHeaders: global::System.Linq.Enumerable.ToDictionary(
-                                        __response.Headers,
-                                        h => h.Key,
-                                        h => h.Value));
-                            }
-                            // 
                             if ((int)__response.StatusCode == 428)
                             {
                                 string? __content_428 = null;
diff --git a/src/libs/Vercel/Generated/Vercel.TeamsClient.PatchTeam.g.cs b/src/libs/Vercel/Generated/Vercel.TeamsClient.PatchTeam.g.cs
index c8b83414..ae834ad3 100644
--- a/src/libs/Vercel/Generated/Vercel.TeamsClient.PatchTeam.g.cs
+++ b/src/libs/Vercel/Generated/Vercel.TeamsClient.PatchTeam.g.cs
@@ -495,38 +495,6 @@ partial void ProcessPatchTeamResponseContent(
                                         h => h.Value));
                             }
                             // 
-                            if ((int)__response.StatusCode == 422)
-                            {
-                                string? __content_422 = null;
-                                global::System.Exception? __exception_422 = null;
-                                try
-                                {
-                                    if (__effectiveReadResponseAsString)
-                                    {
-                                        __content_422 = await __response.Content.ReadAsStringAsync(__effectiveCancellationToken).ConfigureAwait(false);
-                                    }
-                                    else
-                                    {
-                                        __content_422 = await __response.Content.ReadAsStringAsync(__effectiveCancellationToken).ConfigureAwait(false);
-                                    }
-                                }
-                                catch (global::System.Exception __ex)
-                                {
-                                    __exception_422 = __ex;
-                                }
-
-
-                                throw global::Vercel.ApiException.Create(
-                                    statusCode: __response.StatusCode,
-                                    message: __content_422 ?? __response.ReasonPhrase ?? string.Empty,
-                                    innerException: __exception_422,
-                                    responseBody: __content_422,
-                                    responseHeaders: global::System.Linq.Enumerable.ToDictionary(
-                                        __response.Headers,
-                                        h => h.Key,
-                                        h => h.Value));
-                            }
-                            // 
                             if ((int)__response.StatusCode == 428)
                             {
                                 string? __content_428 = null;
diff --git a/src/libs/Vercel/openapi.yaml b/src/libs/Vercel/openapi.yaml
index bdedf6f0..ab246fb8 100644
--- a/src/libs/Vercel/openapi.yaml
+++ b/src/libs/Vercel/openapi.yaml
@@ -52672,7 +52672,7 @@
     },
     "/v1/installations/{integrationConfigurationId}/billing/invoices": {
       "post": {
-        "description": "This endpoint allows the partner to submit an invoice to Vercel. The invoice is created in Vercel's billing system and sent to the customer. Depending on the type of billing plan, the invoice can be sent at a time of signup, at the start of the billing period, or at the end of the billing period.<br/> <br/> Use the `credentials.access_token` we provided in the [Upsert Installation](#upsert-installation) body to authorize this request. <br/> There are several limitations to the invoice submission:<br/> <br/> 1. A resource can only be billed once per the billing period and the billing plan.<br/> 2. The billing plan used to bill the resource must have been active for this resource during the billing period.<br/> 3. The billing plan used must be a subscription plan.<br/> 4. The interim usage data must be sent hourly for all types of subscriptions. See [Send subscription billing and usage data](#send-subscription-billing-and-usage-data) API on how to send interim billing and usage data.<br/>",
+        "description": "This endpoint allows the partner to submit an invoice to Vercel. The invoice is created in Vercel's billing system and sent to the customer. Depending on the type of billing plan, the invoice can be sent at a time of signup, at the start of the billing period, or at the end of the billing period.<br/> <br/> Use the `credentials.access_token` we provided in the [Upsert Installation](#upsert-installation) body to authorize this request. <br/> There are several limitations to the invoice submission:<br/> <br/> 1. A resource can only be billed once per the billing period and the billing plan.<br/> 2. The billing plan used to bill the resource must have been active for this resource during the billing period.<br/> 3. The billing plan used must be a subscription plan.<br/> 4. The interim usage data must be sent hourly for all types of subscriptions. See [Send subscription billing and usage data](#send-subscription-billing-and-usage-data) API on how to send interim billing and usage data.<br/> 5. If provided, `externalId` must be unique for the installation.<br/>",
         "operationId": "submit-invoice",
         "security": [
           {
@@ -52745,7 +52745,8 @@
                 "type": "object",
                 "properties": {
                   "externalId": {
-                    "type": "string"
+                    "type": "string",
+                    "description": "Partner-provided invoice identifier. If provided, it must be unique for this installation."
                   },
                   "invoiceDate": {
                     "type": "string",
@@ -102420,9 +102421,6 @@
           "409": {
             "description": "The provided name for the project is already being used\nThe project is currently being transferred."
           },
-          "422": {
-            "description": ""
-          },
           "428": {
             "description": "Owner does not have protection add-on\nAdvanced Deployment Protection is not available for the user plan"
           }
@@ -138672,9 +138670,6 @@
           "403": {
             "description": "You do not have permission to access this resource.\nNot authorized to update the team. Must be an OWNER."
           },
-          "422": {
-            "description": ""
-          },
           "428": {
             "description": "Owner does not have protection add-on\nAdvanced Deployment Protection is not available for the user plan"
           }