# Python client library 3.14.0 changelog ## zuora_sdk/__init__ * Removed import for AssociationRule, ExpandedDailyConsumptionSummary, ExpandedInvoiceSchedule, ExpandedInvoiceScheduleBooking, ExpandedInvoiceScheduleItem, ExpandedPrepaidBalance, ExpandedPrepaidBalanceFund, ExpandedPrepaidBalanceTransaction, ExpandedValidityPeriodSummary, QueryDailyConsumptionSummarysResponse, QueryInvoiceSchedulesResponse, QueryPrepaidBalanceFundsResponse, QueryPrepaidBalanceTransactionsResponse, QueryPrepaidBalancesResponse, and QueryValidityPeriodSummarysResponse. * Added import for BulkPaymentOptionItem, BulkPaymentProfileRequest, BulkPaymentProfileResponse, BulkPaymentProfileResponseReasonsInner, ChargeRemoval, CreateHostedPageRequest, CreateHostedPageResponse, ExpandedCommitmentAssociatedAccount, ExpandedCommitmentAssociatedItem, ExpandedCommitmentSchedule, ExpandedCommitmentTransaction, QueryCommitmentAssociatedAccountsResponse, QueryCommitmentAssociatedItemsResponse, QueryCommitmentSchedulesResponse, and QueryCommitmentTransactionsResponse. * Renamed import from GetDataLabelingJobResponseProgress to GetDataLabelingJobResponseAllOfProgress. ## credit_memos_api * Added a new optional parameter `should_include_acknowledged` to fetch notifications marked as acknowledged along with unacknowledged ones. ## custom_object_records_api * The `ids` parameter type has changed from `Optional[StrictStr]` to `Optional[List[StrictStr]]`. This requires developers to update their code to pass a list of strings instead of a single string. * Added support for multiple `ids` in query parameters by changing the collection format to `multi`. ## debit_memos_api * Added a new optional parameter `should_include_acknowledged` to fetch notifications marked as acknowledged along with unacknowledged ones. ## hosted_pages_api * Added `create_hosted_page` method to create a new hosted payment page with customizable configurations. * Added `create_hosted_page_with_http_info` method to create a new hosted payment page and retrieve HTTP response information. ## invoices_api * Added a new optional parameter `should_include_acknowledged` to fetch notifications marked as acknowledged along with unacknowledged ones. ## object_queries_api * Removed parameter `include_null_fields` from several methods. * Added new models: ExpandedCommitmentAssociatedAccount, ExpandedCommitmentAssociatedItem, ExpandedCommitmentSchedule, ExpandedCommitmentTransaction. * Added new response models: QueryCommitmentAssociatedAccountsResponse, QueryCommitmentAssociatedItemsResponse, QueryCommitmentSchedulesResponse, QueryCommitmentTransactionsResponse. * Added support for querying custom objects with the method `query_custom_objects`. * Added method `query_payment_schedule_items_with_http_info` for querying payment schedule items with filters, expands, and sort capabilities. * Added method `query_payment_schedules` for querying payment schedules with filters, expands, and sort capabilities. * Added method `query_payments` for querying payments with filters, expands, and sort capabilities. ## payment_schedules_api * Added `delete_payment_schedule` method to delete a payment schedule by its key. * Added `delete_payment_schedule_with_http_info` method to delete a payment schedule with additional HTTP info. * Added `delete_payment_schedule_item` method to delete a payment schedule item by its ID. * Added `delete_payment_schedule_item_with_http_info` method to delete a payment schedule item with additional HTTP info. ## payments_api * Added `bulk_upsert_payment_profiles` method to bulk create or update payment profiles, allowing up to 50 profiles in a single call. * Introduced `bulk_upsert_payment_profiles_with_http_info` method for bulk operations with detailed HTTP response information. ## account_summary_response * Added new fields: `processId`, `requestId`, `reasons`, and `success` to AccountSummaryResponse model. ## billing_document_query_response_element * Added `process_id` and `request_id` fields to track process and request identifiers. * Introduced `reasons` field to capture a list of failure reasons using the `FailedReason` model. * Modified `success` field to default to `true` if not explicitly set. ## cancel_authorization_response * Added `process_id` and `request_id` fields to the CancelAuthorizationResponse model. * Introduced `reasons` field, which is a list of FailedReason objects, to provide detailed failure reasons. * Default value for `success` field is now set to True if not provided. ## cancel_subscription_response * Added `process_id` and `request_id` fields to track process and request identifiers. * Introduced `reasons` field to capture a list of failed reasons using the `FailedReason` model. * Modified `success` field to default to True, indicating the call succeeded unless specified otherwise. ## commitment_base_attributes * Removed the `association_rules` attribute from the CommitmentBaseAttributes model. This may require updates to code that previously utilized this attribute. ## commitment_input * Removed the `association_rules` field from the CommitmentInput model, which may require updates to code that relied on this field. * Changed `period_alignment_option` to be optional with a default value of PeriodAlignmentOptionEnum.COMMITMENTSTARTDATE. This may affect code that assumed this field was mandatory. ## commitment_schedule_attributes * Default value for `amountBase` is now set to `AmountBaseEnum.COMMITMENTPERIOD` if not provided. * Default value for `periodType` is now set to `PeriodTypeEnum.MONTH` if not provided. ## commitment_schedule_input * Default value for `amountBase` is now set to `AmountBaseEnum.COMMITMENTPERIOD` if not provided. * Default value for `periodType` is now set to `PeriodTypeEnum.MONTH` if not provided. ## commitment_schedule_output * Default values have been added for `amountBase` and `periodType`. `amountBase` now defaults to `AmountBaseEnum.COMMITMENTPERIOD` and `periodType` defaults to `PeriodTypeEnum.MONTH`. ## create_accounting_code_response * Added `process_id` and `request_id` fields to track the process and request identifiers. * Introduced `reasons` field to capture a list of `FailedReason` objects, providing more detailed error information. * Default value for `success` field is now set to True if not explicitly provided. ## create_accounting_period_response * Added `process_id` field to track the process handling the operation. * Added `request_id` field for unique request identification. * Introduced `reasons` field to provide a list of failure reasons using the `FailedReason` model. * Default value for `success` field is now set to True if not provided. ## create_billing_document_files_deletion_job_response * Added `process_id` and `request_id` fields to track the process and request identifiers. * Introduced `reasons` field to provide detailed failure reasons. * Default value for `success` field is now set to True. ## create_billing_preview_response * Added `processId` and `requestId` fields to track the process and request identifiers. * Introduced `reasons` field to provide a list of failure reasons using the `FailedReason` model. * Default value for `success` field is now set to true. ## create_invoice_collect_response * Added `processId` and `requestId` fields to track the process and request identifiers. * Introduced `reasons` field to provide detailed failure reasons using the `FailedReason` model. * Default value for `success` field is now set to True. ## create_journal_entry_response * Added `process_id` field to track the process handling the operation. * Added `request_id` field for unique request identification. * Introduced `reasons` field to capture a list of failure reasons using the `FailedReason` model. * Default value for `success` field is now set to True. ## create_journal_run_response * Added `process_id` field to track the process handling the operation. * Added `request_id` field for unique request identification. * Introduced `reasons` field to provide a list of failure reasons using the `FailedReason` model. * Default value for `success` field is now set to True if not provided. ## create_mass_update_response * Added `process_id` field to track the process handling the operation. * Added `request_id` field for unique request identification. * Introduced `reasons` field to capture a list of failed reasons using the `FailedReason` model. * Default value for `success` field is now set to True. ## create_order_rate_plan_update * Added `chargeOverrides` field to support specifying charges to be added or modified in the rate plan. * Added `chargeRemovals` field to support specifying charges to be removed from the bundle rate plan. ## create_order_update_product * Added `chargeOverrides` field to support specifying charges to be added or modified in the rate plan. * Added `chargeRemovals` field to support specifying charges to be removed from the bundle rate plan. ## create_payment_method_decryption_response * Added `process_id` field to track the process handling the operation. * Added `request_id` field for unique request identification. * Introduced `reasons` field to provide detailed failure reasons using the `FailedReason` model. * Default value for `success` field is now set to True if not provided. ## create_payment_predebit_notify_response * Added new fields: `process_id`, `request_id`, `reasons`, and `success` to the CreatePaymentPredebitNotifyResponse model. * Enhanced the `to_dict` method to include a custom serialization for the `reasons` field. ## create_payment_run_request * Added `advancedFilter` field to the CreatePaymentRunRequest model, allowing for advanced filtering of invoices when `useCustomPaymentMethods` is enabled. ## create_payment_schedules_response * Added `process_id` and `request_id` fields to track the process and request identifiers. * Introduced `reasons` field to provide detailed failure reasons. * Default value for `success` field is now set to True. ## create_sequence_sets_response * Added `process_id` and `request_id` fields to track process and request identifiers. * Introduced `reasons` field to capture a list of failure reasons using the `FailedReason` model. * Default value for `success` field is now set to True. ## create_subscription_response * Added `process_id` field to track the process handling the operation. * Added `request_id` field for unique request identification. * Introduced `reasons` field to capture a list of failure reasons using the `FailedReason` model. * Modified `success` field to default to True, indicating the success status of the call. ## create_update_stored_credential_profile_response * Added `process_id` field to track the process handling the operation. * Added `request_id` field for unique request identification. * Introduced `reasons` field to capture a list of failure reasons. * Default value for `success` field is now set to True. ## credit_memos_response * Added `process_id` and `request_id` fields to track process and request identifiers. * Introduced `reasons` field to capture a list of `FailedReason` objects, providing more detailed error information. * Default value for `success` field is now set to True, indicating successful operation by default. ## decrypt_rsa_signature_response * Added new fields: `process_id`, `request_id`, and `reasons` to the DecryptRSASignatureResponse model. * Enhanced the `to_dict` method to include a custom serialization for the `reasons` field. ## delete_order_async_response * Added `processId` and `requestId` fields to track the process and request identifiers. * Introduced `reasons` field to capture a list of failure reasons using the `FailedReason` model. * Default value for `success` field is now set to True if not provided. ## expanded_commitment * Added new fields: `start_date`, `end_date`, `total_amount`, `account_id`, `period_alignment_option`, and `specific_period_alignment_date` to the ExpandedCommitment model. * Introduced associations with ExpandedAccount, ExpandedCommitmentSchedule, ExpandedCommitmentAssociatedAccount, and ExpandedCommitmentAssociatedItem models. * Enhanced `to_dict` method to include new fields and associations, providing more detailed serialization. * Updated `from_dict` method to handle deserialization of new fields and associated models. ## expanded_commitment_period * Added new optional fields: `status`, `commitment_number`, `schedule_id`, `schedule_number`, `commitment_type`, `commitment_priority`, `account_id`, `is_prorated`, `billed_total_spending`, `account`, and `commitment_transactions`. * Integration with ExpandedAccount and ExpandedCommitmentTransaction models, allowing for nested data structures. ## expanded_credit_memo_item * Removed `invoice_schedule` and `invoice_schedule_item` fields from the ExpandedCreditMemoItem model. ## expanded_invoice_item * Removed `invoice_schedule` and `invoice_schedule_item` fields from the ExpandedInvoiceItem model. * Removed import statements for ExpandedInvoiceSchedule and ExpandedInvoiceScheduleItem. ## expanded_rate_plan_charge * Added `is_unbilled` field to the ExpandedRatePlanCharge model. * Added `is_allocation_eligible` field to the ExpandedRatePlanCharge model. ## expanded_subscription * Added `sold_to_contact` field to the ExpandedSubscription model, allowing developers to specify and retrieve the sold-to contact information. ## get_accounting_code_response * Added `processId` and `requestId` fields to track the process and request identifiers. * Introduced `reasons` field to provide a list of failure reasons using the `FailedReason` model. * Updated `success` field to default to True, indicating the success status of the call. ## get_accounting_codes_response * Added `processId` and `requestId` fields to track the process and request identifiers. * Introduced `reasons` field to capture a list of failure reasons using the `FailedReason` model. * Modified `success` field to default to true if not explicitly set. ## get_accounting_period_response * Added `processId` field to track the process handling the operation. * Added `requestId` field for unique request identification. * Introduced `reasons` field to capture a list of failure reasons using the `FailedReason` model. * Enhanced `success` field to default to True, indicating the success of the call. ## get_accounting_periods_response * Added `processId` and `requestId` fields to track the process and request identifiers. * Introduced `reasons` field to capture a list of failure reasons using the `FailedReason` model. * Default value for `success` field is now set to True. ## get_async_order_job_response * Added `processId` and `requestId` fields to track the process and request identifiers. * Introduced `reasons` field to capture a list of failure reasons using the `FailedReason` model. * Default value for `success` field is now set to True, indicating the call succeeded unless specified otherwise. ## get_billing_document_files_deletion_job_response * Added `processId` and `requestId` fields to track the process and request identifiers. * Introduced `reasons` field to provide detailed failure reasons using the FailedReason model. * Default value for `success` field is now set to True, indicating successful operation by default. ## get_billing_preview_run_response * Added `processId` field to track the process handling the operation. * Added `requestId` field for unique request identification. * Added `reasons` field to capture failure reasons using the `FailedReason` model. * Added `success` field to indicate if the call succeeded. ## get_bulk_pdf_generation_job_response * Added `processId` and `requestId` fields to track the process and request identifiers. * Introduced `reasons` field to capture a list of failure reasons using the new `FailedReason` model. * Modified `success` field to default to True, indicating the call's success status. ## get_callout_history_vos_type * Added `process_id` and `request_id` fields to track process and request identifiers. * Introduced `reasons` field to capture a list of `FailedReason` objects. * Default value for `success` field is now set to `True`. ## get_commitment_output * Removed the `association_rules` field from the GetCommitmentOutput model, which may affect any code relying on this field. * Changed the default value of `period_alignment_option` to PeriodAlignmentOptionEnum.COMMITMENTSTARTDATE if not provided. ## get_credit_memo_item_parts_response * Added `processId` and `requestId` fields to track the process and request identifiers. * Introduced `reasons` field to capture a list of `FailedReason` objects, providing more detailed error information. * Default value for `success` field is now set to `True`. ## get_credit_memo_parts_response * Added `process_id` and `request_id` fields to track the process and request identifiers. * Introduced `reasons` field to capture a list of failed reasons using the `FailedReason` model. * Default value for `success` field is now set to True. ## get_credit_memo_pdf_status_batch_response * Added `process_id` and `request_id` fields to track the process and request identifiers. * Introduced `reasons` field to capture a list of failure reasons using the `FailedReason` model. * Default value for `success` field is now set to True. ## get_custom_exchange_rates_type * Added `process_id` and `request_id` fields to track the process and request identifiers. * Introduced `reasons` field to capture a list of failure reasons using the `FailedReason` model. * Modified `success` field to default to `True` if not explicitly set. ## get_data_labeling_job_response * The `progress` field type has changed from GetDataLabelingJobResponseProgress to GetDataLabelingJobResponseAllOfProgress. * Added `process_id` field to track the process handling the operation. * Added `request_id` field for unique request identification. * Added `reasons` field to capture a list of FailedReason objects. * The `success` field now defaults to True if not specified. ## get_debit_memo_application_parts_response * Added `processId` and `requestId` fields to track the process and request identifiers. * Introduced `reasons` field to capture a list of failure reasons using the `FailedReason` model. * Modified `success` field to default to True if not explicitly set. ## get_debit_memo_pdf_status_batch_response * Added `process_id` and `request_id` fields to track process and request identifiers. * Introduced `reasons` field to capture a list of failure reasons. * Default value for `success` field is now set to True. ## get_email_history_vos_type * Added `process_id` and `request_id` fields to track process and request identifiers. * Introduced `reasons` field to capture a list of failure reasons using the `FailedReason` model. * Default value for `success` field is now set to True. ## get_invoice_application_parts_request * Added `process_id` and `request_id` fields to track the process and request identifiers. * Introduced `reasons` field to capture a list of failure reasons using the `FailedReason` model. * Modified `success` field to default to true, indicating the call succeeded unless specified otherwise. ## get_invoice_pdf_status_batch_response * Added `process_id` and `request_id` fields to track the process and request identifiers. * Introduced `reasons` field to capture a list of failure reasons using the `FailedReason` model. * Default value for `success` field is now set to True. ## get_journal_entries_in_journal_run_response * Added `processId` and `requestId` fields to the response model for tracking process and request identifiers. * Introduced `reasons` field to capture a list of failure reasons using the `FailedReason` model. * Modified `success` field to default to `true` if not explicitly set. ## get_journal_entry_detail_response * Added `processId` field to track the ID of the process handling the operation. * Added `requestId` field for unique request identification. * Introduced `reasons` field to capture a list of failure reasons using the `FailedReason` model. * Added `success` field to indicate whether the call succeeded, defaulting to true. ## get_mass_update_response * Added `process_id` field to track the process handling the operation. * Added `request_id` field for unique request identification. * Introduced `reasons` field to capture a list of failure reasons using the `FailedReason` model. * Modified `success` field to default to true, indicating the success of the call. ## get_payment_item_part_response * Added `process_id` and `request_id` fields to track the process and request identifiers. * Introduced `reasons` field to capture a list of failure reasons using the `FailedReason` model. * Modified `success` field default value to True, indicating the call succeeded by default. ## get_payment_item_parts_response * Added `process_id` and `request_id` fields to track the process and request identifiers. * Introduced `reasons` field to capture a list of failure reasons using the `FailedReason` model. * Default value for `success` field is now set to True, indicating successful processing by default. ## get_payment_part_response * Added `processId` and `requestId` fields to track the process and request identifiers. * Introduced `reasons` field which is a list of `FailedReason` objects to provide detailed failure reasons. * Default value for `success` field changed to True. ## get_payment_parts_response * Added `process_id` and `request_id` fields to track process and request identifiers. * Introduced `reasons` field to capture a list of failure reasons using the `FailedReason` model. * Default value for `success` field is now set to True. ## get_payment_run_data_array_response * Added `process_id` and `request_id` fields to the GetPaymentRunDataArrayResponse model, allowing developers to access process and request identifiers. * Introduced `reasons` field as a list of FailedReason objects, providing detailed failure reasons. * Default value for `success` field is now set to True, indicating successful processing by default. ## get_payment_run_summary_response * Added `process_id` and `request_id` fields to the GetPaymentRunSummaryResponse model, allowing developers to access process and request identifiers. * Introduced `reasons` field, which is a list of FailedReason objects, providing detailed failure reasons. * Modified `success` field to default to True, indicating the success status of the call. ## get_payment_runs_response * Added `process_id` field to track the process handling the operation. * Added `request_id` field for unique request identification. * Introduced `reasons` field to capture a list of failure reasons. * Modified `success` field to default to True, indicating the call succeeded unless specified otherwise. ## get_payment_schedule_statistic_response * Added `process_id` and `request_id` fields to track process and request identifiers. * Introduced `reasons` field to capture a list of failure reasons using the `FailedReason` model. * Default value for `success` field is now set to True. ## get_product_rate_plan_response * Added `process_id` and `request_id` fields to track the process and request identifiers. * Introduced `reasons` field to capture a list of failure reasons using the `FailedReason` model. * Included `success` field to indicate if the request was processed successfully. ## get_product_rate_plans_by_external_id_response * Added `process_id` and `request_id` fields to track the process and request identifiers. * Introduced `reasons` field to capture a list of failure reasons using the `FailedReason` model. * Default value for `success` field is now set to True. ## get_product_rate_plans_by_product_response * Added `process_id` and `request_id` fields to track the process and request identifiers. * Introduced `reasons` field to capture a list of failure reasons using the `FailedReason` model. * Default value for `success` field is now set to True. ## get_refund_item_parts_response * Added `process_id` and `request_id` fields to the GetRefundItemPartsResponse model, providing additional context for operations. * Introduced `reasons` field, which is a list of FailedReason objects, to provide detailed failure reasons. * Modified `success` field default value to True, indicating successful processing by default. ## get_refund_parts_response * Added `process_id` and `request_id` fields to the GetRefundPartsResponse model. * Introduced `reasons` field which is a list of FailedReason objects. * The `success` field now defaults to True if not provided. ## get_refunds_response * Added `process_id` and `request_id` fields to track the process and request identifiers. * Introduced `reasons` field to capture a list of failed reasons. * Default value for `success` field is now set to True. ## get_sequence_sets_response * Added `process_id` and `request_id` fields to the GetSequenceSetsResponse model. * Introduced `reasons` field, which is a list of FailedReason objects, to the GetSequenceSetsResponse model. * Default value for `success` field is now set to True if not provided. ## get_subscription_rate_plan * Added `product_rate_plan_type` field to specify the type of the product rate plan. * Added `original_rate_plan_id` field to capture the original rate plan ID. ## get_subscription_rate_plan_charges_with_all_segments * Added `isLastSegment` field to indicate if the charge segment is the last segment. * Added `optional` field to indicate if the charge is optional in a bundle rate plan. * Added `status` field with possible values `removeDirectly` and `deleteWithRatePlan`. ## get_subscriptions_response * Added `process_id` and `request_id` fields to track the process and request identifiers. * Introduced `reasons` field to capture a list of failure reasons using the `FailedReason` model. * Default value for `success` field is now set to True, indicating successful processing by default. ## get_taxation_items_response * Added `processId` and `requestId` fields to the GetTaxationItemsResponse model, providing additional identifiers for process and request tracking. * Introduced `reasons` field, which is a list of FailedReason objects, allowing for detailed failure information. ## get_usage_rate_detail_request * Added `process_id` and `request_id` fields to track the process and request identifiers. * Introduced `reasons` field, which is a list of `FailedReason` objects, to provide detailed failure reasons. * Default value for `success` field is now set to True, indicating the call succeeded unless specified otherwise. ## get_usages_by_account_response * Added `process_id` field to track the process handling the operation. * Added `request_id` field for unique request identification. * Introduced `reasons` field to capture failure reasons. * Default value for `success` field is now set to True. ## hosted_pages_response * Added new fields `processId` and `requestId` to the HostedPagesResponse model, providing additional identifiers for processes and requests. * Introduced a new `reasons` field in the HostedPagesResponse model, which is a list of FailedReason objects, allowing for detailed error reporting. * Changed the default value of the `success` field to True, indicating that requests are assumed successful unless specified otherwise. ## invoice_schedule * Added `organizationLabel` as a new optional field in the InvoiceSchedule model. ## invoice_schedule_item * Added `organizationLabel` field to the InvoiceScheduleItem model, allowing developers to specify an organization label. ## invoice_schedule_response * Added `organizationLabel` as a new optional field in the InvoiceScheduleResponse model. ## order_action_update_product * Added `chargeRemovals` field to support removal of charges in the `updateProduct` order action. * Added `chargeOverrides` field to allow adding or modifying charges in the rate plan for the `updateProduct` order action. ## payment_gateways_response * Added `process_id` and `request_id` fields to the PaymentGatewaysResponse model. * Introduced `reasons` field, which is a list of FailedReason objects, to the PaymentGatewaysResponse model. * Modified `success` field to default to True if not provided. ## payment_method_updater_instances_response * Added `process_id` and `request_id` fields to track the process and request identifiers. * Introduced `reasons` field to capture a list of `FailedReason` objects, providing more detailed error information. ## payment_run * Added `advanced_filter` field to the PaymentRun model, allowing for advanced filtering of invoices when `useCustomPaymentMethods` is enabled. ## payment_run_response * Added `advanced_filter` field to the PaymentRunResponse model, allowing for advanced filtering of invoices when `useCustomPaymentMethods` is enabled. ## preview_order_rate_plan_update * Added `chargeOverrides` field to support specifying charge overrides for the UpdateProduct order action. * Added `chargeRemovals` field to support specifying charge removals for the UpdateProduct order action. ## preview_subscription_response * Added new fields: `process_id`, `request_id`, `reasons`, and `success` to the PreviewSubscriptionResponse model. ## put_revpro_acc_code_response * Added `process_id` and `request_id` fields to the PutRevproAccCodeResponse model for tracking process and request identifiers. * Introduced `reasons` field in the PutRevproAccCodeResponse model to provide detailed failure reasons using the FailedReason model. ## rate_plan_charge_segment * Added `isLastSegment` field to indicate if the charge segment is the last segment. * Added `optional` field to indicate if the charge is optional in a bundle rate plan. * Added `status` field to represent the status of the charge with possible values `removeDirectly` and `deleteWithRatePlan`. ## rate_plan_charge_segment_info * Added `isLastSegment` field to indicate if the charge segment is the last segment. * Added `optional` field to indicate if the charge is optional in a bundle rate plan. * Added `status` field to represent the status of the charge with possible values `removeDirectly` and `deleteWithRatePlan`. ## rate_plan_update * Added `charge_removals` field to support specifying charges to be removed from the bundle rate plan. * Added `charge_overrides` field to support specifying charges to be added or modified in the rate plan. ## regenerate_rev_rec_events_response * Added `request_id` field to provide a unique request identifier. * Introduced `reasons` field, which is a list of `FailedReason` objects, to provide detailed failure reasons. ## regenerate_transaction_object_response * Added `request_id` field to provide a unique request identifier. * Introduced `reasons` field which is a list of `FailedReason` objects to provide detailed failure reasons. * Changed default value of `success` field to True. ## renew_subscription_response * Added `processId` and `requestId` fields to track the process and request identifiers. * Introduced `reasons` field to capture a list of failure reasons using the FailedReason model. * Default value for `success` field is now set to True if not provided. ## resume_subscription_response * Added `process_id` and `request_id` fields to track process and request identifiers. * Introduced `reasons` field to capture a list of failure reasons using the `FailedReason` model. * Default value for `success` field is now set to True if not provided. ## retry_payment_schedule_item_response * Added `process_id` and `request_id` fields to track the process and request identifiers. * Introduced `reasons` field to provide a list of failure reasons using the `FailedReason` model. * Default value for `success` field is now set to True. ## rsa_signature_response * Added `processId` and `requestId` fields to the RSASignatureResponse model. * Introduced `reasons` field, which is a list of FailedReason objects, to provide detailed failure reasons. * Default value for `success` field is now set to True if not provided. ## stored_credential_profiles_response * Added `process_id` and `request_id` fields to track process and request identifiers. * Introduced `reasons` field to capture a list of failure reasons using the `FailedReason` model. * Default value for `success` field is now set to True. ## submit_data_labeling_job_response * Added `process_id` field to track the process handling the operation. * Added `request_id` field for unique request identification. * Introduced `reasons` field to capture a list of failure reasons. * Default value for `success` field is now set to True. ## subscription_rate_plan * Added `product_rate_plan_type` field to SubscriptionRatePlan model. * Added `original_rate_plan_id` field to SubscriptionRatePlan model. ## suspend_subscription_response * Added `process_id` and `request_id` fields to track process and request identifiers. * Introduced `reasons` field to capture a list of failure reasons using the `FailedReason` model. * Added `success` field with a default value of True to indicate the success status of the call. ## update_payment_run_request * Added `advancedFilter` field to the UpdatePaymentRunRequest model, allowing for advanced filtering of invoices when `useCustomPaymentMethods` is enabled. ## update_sequence_set_response * Added `process_id` and `request_id` fields to track process and request identifiers. * Introduced `reasons` field to capture a list of `FailedReason` objects, providing more detailed error information. ## update_subscription_response * Added `process_id` field to track the process handling the operation. * Added `request_id` field for unique request identification. * Added `reasons` field to capture a list of failure reasons. * Updated `success` field to default to True, indicating the call succeeded. ## upload_file_response * Added `process_id` field to track the process handling the operation. * Added `request_id` field for unique request identification. * Introduced `reasons` field to provide detailed failure reasons using the `FailedReason` model. * Default value for `success` field is now set to True. ## upload_usage_file_response * Added `processId` and `requestId` fields to track the process and request identifiers. * Introduced `reasons` field to capture a list of failure reasons using the `FailedReason` model. * Default value for `success` field is now set to True. ## upsert_create_commitment_input * Removed `association_rules` field from UpsertCreateCommitmentInput model, which may affect any code relying on this field. * Changed `period_alignment_option` field to be optional with a default value of PeriodAlignmentOptionEnum.COMMITMENTSTARTDATE. ## upsert_create_commitment_schedule_input * Default value for `amountBase` is now set to `AmountBaseEnum.COMMITMENTPERIOD` if not provided. * Default value for `periodType` is now set to `PeriodTypeEnum.MONTH` if not provided. ## verify_payment_method_response * Added `process_id` and `request_id` fields to track the process and request identifiers. * Introduced `reasons` field to capture a list of failure reasons using the `FailedReason` model. * Default value for `success` field is now set to True if not provided. ## write_off_invoice_response * Added `process_id` and `request_id` fields to track process and request identifiers. * Introduced `reasons` field to capture a list of `FailedReason` objects. * Default value for `success` field is now set to True.