metronome-sdk 1.0.0 → 2.1.0

data/lib/metronome_sdk/resources/v1/alerts.rb

@@ -7,16 +7,15 @@ module MetronomeSDK
         # Some parameter documentations has been truncated, see
         # {MetronomeSDK::Models::V1::AlertCreateParams} for more details.
         #
-        # Create a new alert to monitor customer spending, balances, and billing metrics
-        # in real-time. Metronome's alert system provides industry-leading speed with
-        # immediate evaluation capabilities, enabling you to proactively manage customer
-        # accounts and prevent revenue leakage.
+        # Create a new threshold notification to monitor customer spending, balances, and
+        # billing metrics in real-time. Metronome's notification system provides
+        # industry-leading speed with immediate evaluation capabilities, enabling you to
+        # proactively manage customer accounts and prevent revenue leakage.
         #
-        # This endpoint creates configurable alerts that continuously monitor various
-        # billing thresholds including spend limits, credit balances, commitment
-        # utilization, and invoice totals. Alerts can be configured globally for all
-        # customers or targeted to specific customer accounts. Custom fields can be used
-        # on certain alert types to further target alerts to groups of customers.
+        # This endpoint creates configurable threshold notifications that continuously
+        # monitor various billing thresholds including spend limits, credit balances,
+        # commitment utilization, and invoice totals. Threshold notifications can be
+        # configured globally for all customers or targeted to specific customer accounts.
         #
         # ### Use this endpoint to:
         #
@@ -32,52 +31,53 @@ module MetronomeSDK
         #
         # A successful response returns a CustomerAlert object containing:
         #
-        # - The alert configuration with its unique ID and current status
+        # - The threshold notification configuration with its unique ID and current status
         # - The customer's evaluation status (ok, in_alarm, or evaluating)
-        # - Alert metadata including type, threshold values, and update timestamps
+        # - Threshold notification metadata including type, threshold values, and update
+        #   timestamps
         #
         # ### Usage guidelines:
         #
         # - Immediate evaluation: Set `evaluate_on_create` : `true` (default) for instant
         #   evaluation against existing customers
-        # - Uniqueness constraints: Each alert must have a unique `uniqueness_key` within
-        #   your organization. Use `release_uniqueness_key` : `true` when archiving to
-        #   reuse keys
-        # - Alert type requirements: Different alert types require specific fields (e.g.,
-        #   `billable_metric_id` for usage alerts, `credit_type_id` for credit-based
-        #   alerts)
-        # - Webhook delivery: Alerts trigger webhook notifications for real-time
-        #   integration with your systems. Configure webhook endpoints before creating
-        #   alerts
-        # - Performance at scale: Metronome's event-driven architecture processes alert
-        #   evaluations in real-time as usage events stream in, unlike competitors who
-        #   rely on periodic polling or batch evaluation cycles
+        # - Uniqueness constraints: Each threshold notification must have a unique
+        #   `uniqueness_key` within your organization. Use `release_uniqueness_key` :
+        #   `true` when archiving to reuse keys
+        # - Notification type requirements: Different threshold notification types require
+        #   specific fields (e.g., `billable_metric_id` for usage notifications,
+        #   `credit_type_id` for credit-based threshold notifications)
+        # - Webhook delivery: Threshold notifications trigger webhook notifications for
+        #   real-time integration with your systems. Configure webhook endpoints before
+        #   creating threshold notifications
+        # - Performance at scale: Metronome's event-driven architecture processes
+        #   threshold notification evaluations in real-time as usage events stream in,
+        #   unlike competitors who rely on periodic polling or batch evaluation cycles
         #
         # @overload create(alert_type:, name:, threshold:, billable_metric_id: nil, credit_grant_type_filters: nil, credit_type_id: nil, custom_field_filters: nil, customer_id: nil, evaluate_on_create: nil, group_values: nil, invoice_types_filter: nil, plan_id: nil, uniqueness_key: nil, request_options: {})
         #
-        # @param alert_type [Symbol, MetronomeSDK::Models::V1::AlertCreateParams::AlertType] Type of the alert
+        # @param alert_type [Symbol, MetronomeSDK::Models::V1::AlertCreateParams::AlertType] Type of the threshold notification
         #
-        # @param name [String] Name of the alert
+        # @param name [String] Name of the threshold notification
         #
-        # @param threshold [Float] Threshold value of the alert policy. Depending upon the alert type, this number
+        # @param threshold [Float] Threshold value of the notification policy. Depending upon the notification typ
         #
-        # @param billable_metric_id [String] For alerts of type `usage_threshold_reached`, specifies which billable metric to
+        # @param billable_metric_id [String] For threshold notifications of type `usage_threshold_reached`, specifies which b
         #
-        # @param credit_grant_type_filters [Array<String>] An array of strings, representing a way to filter the credit grant this alert ap
+        # @param credit_grant_type_filters [Array<String>] An array of strings, representing a way to filter the credit grant this threshol
         #
-        # @param credit_type_id [String] ID of the credit's currency, defaults to USD. If the specific alert type require
+        # @param credit_type_id [String] ID of the credit's currency, defaults to USD. If the specific notification type
         #
-        # @param custom_field_filters [Array<MetronomeSDK::Models::V1::AlertCreateParams::CustomFieldFilter>] A list of custom field filters for alert types that support advanced filtering.
+        # @param custom_field_filters [Array<MetronomeSDK::Models::V1::AlertCreateParams::CustomFieldFilter>] A list of custom field filters for threshold notification types that support adv
         #
-        # @param customer_id [String] If provided, will create this alert for this specific customer. To create an ale
+        # @param customer_id [String] If provided, will create this threshold notification for this specific customer.
         #
-        # @param evaluate_on_create [Boolean] If true, the alert will evaluate immediately on customers that already meet the
+        # @param evaluate_on_create [Boolean] If true, the threshold notification will evaluate immediately on customers that
         #
-        # @param group_values [Array<MetronomeSDK::Models::V1::AlertCreateParams::GroupValue>] Only present for `spend_threshold_reached` alerts. Scope alert to a specific gro
+        # @param group_values [Array<MetronomeSDK::Models::V1::AlertCreateParams::GroupValue>] Only present for `spend_threshold_reached` notifications. Scope notification to
         #
-        # @param invoice_types_filter [Array<String>] Only supported for invoice_total_reached alerts. A list of invoice types to eval
+        # @param invoice_types_filter [Array<String>] Only supported for invoice_total_reached threshold notifications. A list of invo
         #
-        # @param plan_id [String] If provided, will create this alert for this specific plan. To create an alert f
+        # @param plan_id [String] If provided, will create this threshold notification for this specific plan. To
         #
         # @param uniqueness_key [String] Prevents the creation of duplicates. If a request to create a record is made wit
         #
@@ -97,39 +97,43 @@ module MetronomeSDK
           )
         end
 
-        # Permanently disable an alert and remove it from active monitoring across all
-        # customers. Archived alerts stop evaluating immediately and can optionally
-        # release their uniqueness key for reuse in future alert configurations.
+        # Some parameter documentations has been truncated, see
+        # {MetronomeSDK::Models::V1::AlertArchiveParams} for more details.
+        #
+        # Permanently disable a threshold notification and remove it from active
+        # monitoring across all customers. Archived threshold notifications stop
+        # evaluating immediately and can optionally release their uniqueness key for reuse
+        # in future threshold notification configurations.
         #
         # ### Use this endpoint to:
         #
-        # - Decommission alerts that are no longer needed
-        # - Clean up test or deprecated alert configurations
-        # - Free up uniqueness keys for reuse with new alerts
-        # - Stop alert evaluations without losing historical configuration data
+        # - Decommission threshold notifications that are no longer needed
+        # - Clean up test or deprecated threshold notification configurations
+        # - Free up uniqueness keys for reuse with new threshold notifications
+        # - Stop threshold notification evaluations without losing historical
+        #   configuration data
         # - Disable outdated monitoring rules during pricing model transitions
         #
         # ### Key response fields:
         #
-        # - data: Object containing the archived alert's ID
-        # - Alert evaluation stops immediately for all affected customers
-        # - Historical alert data and configurations remain accessible for audit purposes
+        # - data: Object containing the archived threshold notification's ID
         #
         # ### Usage guidelines:
         #
-        # - Irreversible for evaluation: Archived alerts cannot be re-enabled; create a
-        #   new alert to resume monitoring
+        # - Irreversible for evaluation: Archived threshold notifications cannot be
+        #   re-enabled; create a new threshold notification to resume monitoring
         # - Uniqueness key handling: Set `release_uniqueness_key` : `true` to reuse the
-        #   key in future alerts
-        # - Immediate effect: Alert evaluation stops instantly across all customers
-        # - Historical preservation: Archive operation maintains alert history and
-        #   configuration for compliance and auditing
+        #   key in future threshold notifications
+        # - Immediate effect: Threshold notification evaluation stops instantly across all
+        #   customers
+        # - Historical preservation: Archive operation maintains threshold notification
+        #   history and configuration for compliance and auditing
         #
         # @overload archive(id:, release_uniqueness_key: nil, request_options: {})
         #
-        # @param id [String] The Metronome ID of the alert
+        # @param id [String] The Metronome ID of the threshold notification
         #
-        # @param release_uniqueness_key [Boolean] If true, resets the uniqueness key on this alert so it can be re-used
+        # @param release_uniqueness_key [Boolean] If true, resets the uniqueness key on this threshold notification so it can be r
         #
         # @param request_options [MetronomeSDK::RequestOptions, Hash{Symbol=>Object}, nil]
         #

data/lib/metronome_sdk/resources/v1/contracts.rb

@@ -352,7 +352,7 @@ module MetronomeSDK
 
         # Amendments will be replaced by Contract editing. New clients should implement
         # using the `editContract` endpoint. Read more about the migration to contract
-        # editing [here](https://docs.metronome.com/migrate-amendments-to-edits/) and
+        # editing [here](/guides/implement-metronome/migrate-amendments-to-edits/) and
         # reach out to your Metronome representative for more details. Once contract
         # editing is enabled, access to this endpoint will be removed.
         #
@@ -514,7 +514,7 @@ module MetronomeSDK
         #   segments
         # - Manual adjustments: Includes all manual ledger entries, even future-dated ones
         #
-        # @overload list_balances(customer_id:, id: nil, covering_date: nil, effective_before: nil, include_archived: nil, include_balance: nil, include_contract_balances: nil, include_ledgers: nil, limit: nil, next_page: nil, starting_at: nil, request_options: {})
+        # @overload list_balances(customer_id:, id: nil, covering_date: nil, effective_before: nil, exclude_zero_balances: nil, include_archived: nil, include_balance: nil, include_contract_balances: nil, include_ledgers: nil, limit: nil, next_page: nil, starting_at: nil, request_options: {})
         #
         # @param customer_id [String]
         #
@@ -524,6 +524,8 @@ module MetronomeSDK
         #
         # @param effective_before [Time] Include only balances that have any access before the provided date (exclusive)
         #
+        # @param exclude_zero_balances [Boolean] Exclude balances with zero amounts from the response.
+        #
         # @param include_archived [Boolean] Include archived credits and credits from archived contracts.
         #
         # @param include_balance [Boolean] Include the balance of credits and commits in the response. Setting this flag ma
@@ -709,11 +711,12 @@ module MetronomeSDK
         # Some parameter documentations has been truncated, see
         # {MetronomeSDK::Models::V1::ContractUpdateEndDateParams} for more details.
         #
-        # Update or and an end date to a contract. Ending a contract early will impact
+        # Update or add an end date to a contract. Ending a contract early will impact
         # draft usage statements, truncate any terms, and remove upcoming scheduled
         # invoices. Moving the date into the future will only extend the contract length.
-        # Terms and scheduled invoices are not extended. Use this if a contract's end date
-        # has changed or if a perpetual contract ends.
+        # Terms and scheduled invoices are not extended. In-advance subscriptions will not
+        # be extended. Use this if a contract's end date has changed or if a perpetual
+        # contract ends.
         #
         # @overload update_end_date(contract_id:, customer_id:, allow_ending_before_finalized_invoice: nil, ending_before: nil, request_options: {})
         #

data/lib/metronome_sdk/resources/v1/credit_grants.rb

@@ -7,7 +7,8 @@ module MetronomeSDK
         # Some parameter documentations has been truncated, see
         # {MetronomeSDK::Models::V1::CreditGrantCreateParams} for more details.
         #
-        # Create a new credit grant
+        # Create a new credit grant. This is a Plans (deprecated) endpoint. New clients
+        # should implement using Contracts.
         #
         # @overload create(customer_id:, expires_at:, grant_amount:, name:, paid_amount:, priority:, credit_grant_type: nil, custom_fields: nil, effective_at: nil, invoice_date: nil, product_ids: nil, reason: nil, rollover_settings: nil, uniqueness_key: nil, request_options: {})
         #
@@ -58,7 +59,8 @@ module MetronomeSDK
         # Some parameter documentations has been truncated, see
         # {MetronomeSDK::Models::V1::CreditGrantListParams} for more details.
         #
-        # List credit grants. This list does not included voided grants.
+        # List credit grants. This list does not included voided grants. This is a Plans
+        # (deprecated) endpoint. New clients should implement using Contracts.
         #
         # @overload list(limit: nil, next_page: nil, credit_grant_ids: nil, credit_type_ids: nil, customer_ids: nil, effective_before: nil, not_expiring_before: nil, request_options: {})
         #
@@ -95,7 +97,8 @@ module MetronomeSDK
           )
         end
 
-        # Edit an existing credit grant
+        # Edit an existing credit grant. This is a Plans (deprecated) endpoint. New
+        # clients should implement using Contracts.
         #
         # @overload edit(id:, credit_grant_type: nil, expires_at: nil, name: nil, request_options: {})
         #
@@ -128,7 +131,8 @@ module MetronomeSDK
         #
         # Fetches a list of credit ledger entries. Returns lists of ledgers per customer.
         # Ledger entries are returned in chronological order. Ledger entries associated
-        # with voided credit grants are not included.
+        # with voided credit grants are not included. This is a Plans (deprecated)
+        # endpoint. New clients should implement using Contracts.
         #
         # @overload list_entries(next_page: nil, sort: nil, credit_type_ids: nil, customer_ids: nil, ending_before: nil, starting_on: nil, request_options: {})
         #
@@ -164,7 +168,8 @@ module MetronomeSDK
           )
         end
 
-        # Void a credit grant
+        # Void a credit grant. This is a Plans (deprecated) endpoint. New clients should
+        # implement using Contracts.
         #
         # @overload void(id:, release_uniqueness_key: nil, void_credit_purchase_invoice: nil, request_options: {})
         #

data/lib/metronome_sdk/resources/v1/customers/alerts.rb

@@ -8,17 +8,26 @@ module MetronomeSDK
           # Some parameter documentations has been truncated, see
           # {MetronomeSDK::Models::V1::Customers::AlertRetrieveParams} for more details.
           #
-          # Retrieve the real-time evaluation status for a specific alert-customer pair.
-          # This endpoint provides instant visibility into whether a customer has triggered
-          # an alert condition, enabling you to monitor account health and take proactive
-          # action based on current alert states.
+          # Retrieve the real-time evaluation status for a specific threshold
+          # notification-customer pair. This endpoint provides instant visibility into
+          # whether a customer has triggered a threshold notification condition, enabling
+          # you to monitor account health and take proactive action based on current
+          # threshold notification states.
           #
           # ### Use this endpoint to:
           #
-          # - Check if a specific customer is currently violating an alert threshold
+          # - Check if a specific customer is currently violating an threshold notification
           #   (`in_alarm` status)
-          # - Verify alert configuration details and threshold values for a customer
-          # - Integrate alert status checks into customer support tools or admin interfaces
+          # - Verify threshold notification configuration details and threshold values for a
+          #   customer
+          # - Monitor the evaluation state of newly created or recently modified threshold
+          #   notification
+          # - Build dashboards or automated workflows that respond to specific threshold
+          #   notification conditions
+          # - Validate threshold notification behavior before deploying to production
+          #   customers
+          # - Integrate threshold notification status checks into customer support tools or
+          #   admin interfaces
           #
           # ### Key response fields:
           #
@@ -27,40 +36,43 @@ module MetronomeSDK
           # - `customer_status`: The current evaluation state
           #
           # - `ok` - Customer is within acceptable thresholds
-          # - `in_alarm`- Customer has breached the alert threshold
-          # - `evaluating` - Alert has yet to be evaluated (typically due to a customer or
-          #   alert having just been created)
-          # - `null` - Alert has been archived
-          # - `triggered_by`: Additional context about what caused the alert to trigger
-          #   (when applicable)
-          # - alert: Complete alert configuration including:
-          #   - Alert ID, name, and type
+          # - `in_alarm` - Customer has breached the threshold for the notification
+          # - `evaluating` - Notification is currently being evaluated (typically during
+          #   initial setup)
+          # - `null` - Notification has been archived
+          # - `triggered_by`: Additional context about what caused the notification to
+          #   trigger (when applicable)
+          # - alert: Complete threshold notification configuration including:
+          #   - Notification ID, name, and type
           #   - Current threshold values and credit type information
-          #   - Alert status (enabled, disabled, or archived)
+          #   - Notification status (enabled, disabled, or archived)
           #   - Last update timestamp
           #   - Any applied filters (credit grant types, custom fields, group values)
           #
           # ### Usage guidelines:
           #
           # - Customer status: Returns the current evaluation state, not historical data.
-          #   For alert history, use webhook notifications or event logs
-          # - Archived alerts: Returns null for customer_status if the alert has been
-          #   archived, but still includes the alert configuration details
-          # - Integration patterns: This endpoint can be used to check a customer's alert
-          #   status, but shouldn't be scraped. You should instead rely on the webhook
-          #   notification to understand when customers are moved to IN_ALARM.
-          # - Error handling: Returns 404 if either the customer or alert ID doesn't exist
+          #   For threshold notification history, use webhook notifications or event logs
+          # - Required parameters: Both customer_id and alert_id must be valid UUIDs that
+          #   exist in your organization
+          # - Archived notifications: Returns null for customer_status if the notification
+          #   has been archived, but still includes the notification configuration details
+          # - Performance considerations: This endpoint queries live evaluation state,
+          #   making it ideal for real-time monitoring but not for bulk status checks
+          # - Integration patterns: Best used for on-demand status checks in response to
+          #   user actions or as part of targeted monitoring workflows
+          # - Error handling: Returns 404 if either the customer or alert_id doesn't exist
           #   or isn't accessible to your organization
           #
           # @overload retrieve(alert_id:, customer_id:, group_values: nil, plans_or_contracts: nil, request_options: {})
           #
-          # @param alert_id [String] The Metronome ID of the alert
+          # @param alert_id [String] The Metronome ID of the threshold notification
           #
           # @param customer_id [String] The Metronome ID of the customer
           #
-          # @param group_values [Array<MetronomeSDK::Models::V1::Customers::AlertRetrieveParams::GroupValue>] Only present for `spend_threshold_reached` alerts. Retrieve the alert for a spec
+          # @param group_values [Array<MetronomeSDK::Models::V1::Customers::AlertRetrieveParams::GroupValue>] Only present for `spend_threshold_reached` notifications. Retrieve the notificat
           #
-          # @param plans_or_contracts [Symbol, MetronomeSDK::Models::V1::Customers::AlertRetrieveParams::PlansOrContracts] When parallel alerts are enabled during migration, this flag denotes whether to
+          # @param plans_or_contracts [Symbol, MetronomeSDK::Models::V1::Customers::AlertRetrieveParams::PlansOrContracts] When parallel threshold notifications are enabled during migration, this flag de
           #
           # @param request_options [MetronomeSDK::RequestOptions, Hash{Symbol=>Object}, nil]
           #
@@ -81,31 +93,37 @@ module MetronomeSDK
           # Some parameter documentations has been truncated, see
           # {MetronomeSDK::Models::V1::Customers::AlertListParams} for more details.
           #
-          # Retrieve all alert configurations and their current statuses for a specific
-          # customer in a single API call. This endpoint provides a comprehensive view of
-          # all alerts monitoring a customer account.
+          # Retrieve all threshold notification configurations and their current statuses
+          # for a specific customer in a single API call. This endpoint provides a
+          # comprehensive view of all threshold notification monitoring a customer account.
           #
           # ### Use this endpoint to:
           #
-          # - Display all active alerts for a customer in dashboards or admin panels
-          # - Quickly identify which alerts a customer is currently triggering
-          # - Audit alert coverage for specific accounts
-          # - Filter alerts by status (enabled, disabled, or archived)
+          # - Display all active threshold notifications for a customer in dashboards or
+          #   admin panels
+          # - Quickly identify which threshold notifications a customer is currently
+          #   triggering
+          # - Audit threshold notification coverage for specific accounts
+          # - Filter threshold notifications by status (enabled, disabled, or archived)
           #
           # ### Key response fields:
           #
           # - data: Array of CustomerAlert objects, each containing:
           #   - Current evaluation status (`ok`, `in_alarm`, `evaluating`, or `null`)
-          #   - Complete alert configuration and threshold details
-          #   - Alert metadata including type, name, and last update time
-          # - `next_page`: Pagination cursor for retrieving additional results
+          #   - Complete threshold notification configuration and threshold details
+          #   - Threshold notification metadata including type, name, and last update time
+          # - next_page: Pagination cursor for retrieving additional results
           #
           # ### Usage guidelines:
           #
-          # - Default behavior: Returns only enabled alerts unless alert_statuses filter is
-          #   specified
+          # - Default behavior: Returns only enabled threshold notifications unless
+          #   `alert_statuses` filter is specified
           # - Pagination: Use the `next_page` cursor to retrieve all results for customers
-          #   with many alerts
+          #   with many notifications
+          # - Performance: Efficiently retrieves multiple threshold notification statuses in
+          #   a single request instead of making individual calls
+          # - Filtering: Pass the `alert_statuses` array to include disabled or archived
+          #   threshold notifications in results
           #
           # @overload list(customer_id:, next_page: nil, alert_statuses: nil, request_options: {})
           #
@@ -113,7 +131,7 @@ module MetronomeSDK
           #
           # @param next_page [String] Query param: Cursor that indicates where the next page of results should start.
           #
-          # @param alert_statuses [Array<Symbol, MetronomeSDK::Models::V1::Customers::AlertListParams::AlertStatus>] Body param: Optionally filter by alert status. If absent, only enabled alerts wi
+          # @param alert_statuses [Array<Symbol, MetronomeSDK::Models::V1::Customers::AlertListParams::AlertStatus>] Body param: Optionally filter by threshold notification status. If absent, only
           #
           # @param request_options [MetronomeSDK::RequestOptions, Hash{Symbol=>Object}, nil]
           #
@@ -134,23 +152,24 @@ module MetronomeSDK
             )
           end
 
-          # Force an immediate re-evaluation of a specific alert for a customer, clearing
-          # any previous state and triggering a fresh assessment against current thresholds.
-          # This endpoint ensures alert accuracy after configuration changes or data
-          # corrections.
+          # Force an immediate re-evaluation of a specific threshold notification for a
+          # customer, clearing any previous state and triggering a fresh assessment against
+          # current thresholds. This endpoint ensures threshold notification accuracy after
+          # configuration changes or data corrections.
           #
           # ### Use this endpoint to:
           #
-          # - Clear false positive alerts after fixing data issues
-          # - Re-evaluate alerts after adjusting customer balances or credits
-          # - Test alert behavior during development and debugging
-          # - Resolve stuck alerts that may be in an incorrect state
+          # - Clear false positive threshold notifications after fixing data issues
+          # - Re-evaluate threshold notifications after adjusting customer balances or
+          #   credits
+          # - Test threshold notification behavior during development and debugging
+          # - Resolve stuck threshold notification that may be in an incorrect state
           # - Trigger immediate evaluation after threshold modifications
           #
           # ### Key response fields:
           #
-          # - 200 Success: Confirmation that the alert has been reset and re-evaluation
-          #   initiated
+          # - 200 Success: Confirmation that the threshold notification has been reset and
+          #   re-evaluation initiated
           # - No response body is returned - the operation completes asynchronously
           #
           # ### Usage guidelines:
@@ -165,7 +184,7 @@ module MetronomeSDK
           #
           # @overload reset(alert_id:, customer_id:, request_options: {})
           #
-          # @param alert_id [String] The Metronome ID of the alert
+          # @param alert_id [String] The Metronome ID of the threshold notification
           #
           # @param customer_id [String] The Metronome ID of the customer
           #

data/lib/metronome_sdk/resources/v1/customers/billing_config.rb

@@ -9,7 +9,8 @@ module MetronomeSDK
           # {MetronomeSDK::Models::V1::Customers::BillingConfigCreateParams} for more
           # details.
           #
-          # Set the billing configuration for a given customer.
+          # Set the billing configuration for a given customer. This is a Plans (deprecated)
+          # endpoint. New clients should implement using Contracts.
           #
           # @overload create(customer_id:, billing_provider_type:, billing_provider_customer_id:, aws_product_code: nil, aws_region: nil, stripe_collection_method: nil, request_options: {})
           #
@@ -23,7 +24,7 @@ module MetronomeSDK
           #
           # @param aws_region [Symbol, MetronomeSDK::Models::V1::Customers::BillingConfigCreateParams::AwsRegion] Body param:
           #
-          # @param stripe_collection_method [Symbol, MetronomeSDK::Models::V1::Customers::BillingConfigCreateParams::StripeCollectionMethod] Body param:
+          # @param stripe_collection_method [Symbol, MetronomeSDK::Models::V1::Customers::BillingConfigCreateParams::StripeCollectionMethod] Body param: The collection method for the customer's invoices.
           #
           # @param request_options [MetronomeSDK::RequestOptions, Hash{Symbol=>Object}, nil]
           #
@@ -49,7 +50,8 @@ module MetronomeSDK
             )
           end
 
-          # Fetch the billing configuration for the given customer.
+          # Fetch the billing configuration for the given customer. This is a Plans
+          # (deprecated) endpoint. New clients should implement using Contracts.
           #
           # @overload retrieve(customer_id:, billing_provider_type:, request_options: {})
           #
@@ -81,7 +83,8 @@ module MetronomeSDK
           end
 
           # Delete the billing configuration for a given customer. Note: this is unsupported
-          # for Azure and AWS Marketplace customers.
+          # for Azure and AWS Marketplace customers. This is a Plans (deprecated) endpoint.
+          # New clients should implement using Contracts.
           #
           # @overload delete(customer_id:, billing_provider_type:, request_options: {})
           #

data/lib/metronome_sdk/resources/v1/customers/commits.rb

@@ -37,7 +37,8 @@ module MetronomeSDK
           # #### Billing configuration:
           #
           # - invoice_contract_id is required for postpaid commits and for prepaid commits
-          #   with billing (only optional for free prepaid commits)
+          #   with billing (only optional for free prepaid commits) unless do_not_invoice is
+          #   set to true
           # - For postpaid commits: access_schedule and invoice_schedule must have matching
           #   amounts
           # - For postpaid commits: only one schedule item is allowed in both schedules.

data/lib/metronome_sdk/resources/v1/customers/invoices.rb

@@ -175,7 +175,8 @@ module MetronomeSDK
           # Some parameter documentations has been truncated, see
           # {MetronomeSDK::Models::V1::Customers::InvoiceAddChargeParams} for more details.
           #
-          # Add a one time charge to the specified invoice
+          # Add a one time charge to the specified invoice. This is a Plans (deprecated)
+          # endpoint. New clients should implement using Contracts.
           #
           # @overload add_charge(customer_id:, charge_id:, customer_plan_id:, description:, invoice_start_timestamp:, price:, quantity:, request_options: {})
           #
@@ -299,6 +300,61 @@ module MetronomeSDK
             )
           end
 
+          # Retrieve a PDF version of a specific invoice by its unique identifier. This
+          # endpoint generates a professionally formatted invoice document suitable for
+          # sharing with customers, accounting teams, or for record-keeping purposes.
+          #
+          # ### Use this endpoint to:
+          #
+          # - Provide customers with downloadable or emailable copies of their invoices
+          # - Support accounting and finance teams with official billing documents
+          # - Maintain accurate records of billing transactions for audits and compliance
+          #
+          # ### Key response details:
+          #
+          # - The response is a binary PDF file representing the full invoice
+          # - The PDF includes all standard invoice information such as line items, totals,
+          #   billing period, and customer details
+          # - The document is formatted for clarity and professionalism, suitable for
+          #   official use
+          #
+          # ### Usage guidelines:
+          #
+          # - Ensure the `invoice_id` corresponds to an existing invoice for the specified
+          #   `customer_id`
+          # - The PDF is generated on-demand; frequent requests for the same invoice may
+          #   impact performance
+          # - Use appropriate headers to handle the binary response in your application
+          #   (e.g., setting `Content-Type: application/pdf`)
+          #
+          # @overload retrieve_pdf(customer_id:, invoice_id:, request_options: {})
+          #
+          # @param customer_id [String]
+          # @param invoice_id [String]
+          # @param request_options [MetronomeSDK::RequestOptions, Hash{Symbol=>Object}, nil]
+          #
+          # @return [StringIO]
+          #
+          # @see MetronomeSDK::Models::V1::Customers::InvoiceRetrievePdfParams
+          def retrieve_pdf(params)
+            parsed, options = MetronomeSDK::V1::Customers::InvoiceRetrievePdfParams.dump_request(params)
+            customer_id =
+              parsed.delete(:customer_id) do
+                raise ArgumentError.new("missing required path argument #{_1}")
+              end
+            invoice_id =
+              parsed.delete(:invoice_id) do
+                raise ArgumentError.new("missing required path argument #{_1}")
+              end
+            @client.request(
+              method: :get,
+              path: ["v1/customers/%1$s/invoices/%2$s/pdf", customer_id, invoice_id],
+              headers: {"accept" => "application/pdf"},
+              model: StringIO,
+              options: options
+            )
+          end
+
           # @api private
           #
           # @param client [MetronomeSDK::Client]

data/lib/metronome_sdk/resources/v1/customers/plans.rb

@@ -5,7 +5,8 @@ module MetronomeSDK
     class V1
       class Customers
         class Plans
-          # List the given customer's plans in reverse-chronological order.
+          # List the given customer's plans in reverse-chronological order. This is a Plans
+          # (deprecated) endpoint. New clients should implement using Contracts.
           #
           # @overload list(customer_id:, limit: nil, next_page: nil, request_options: {})
           #
@@ -41,7 +42,8 @@ module MetronomeSDK
           #
           # Associate an existing customer with a plan for a specified date range. See the
           # [price adjustments documentation](https://plans-docs.metronome.com/pricing/managing-plans/#price-adjustments)
-          # for details on the price adjustments.
+          # for details on the price adjustments. This is a Plans (deprecated) endpoint. New
+          # clients should implement using Contracts.
           #
           # @overload add(customer_id:, plan_id:, starting_on:, ending_before: nil, net_payment_terms_days: nil, overage_rate_adjustments: nil, price_adjustments: nil, trial_spec: nil, request_options: {})
           #
@@ -84,7 +86,8 @@ module MetronomeSDK
           # Some parameter documentations has been truncated, see
           # {MetronomeSDK::Models::V1::Customers::PlanEndParams} for more details.
           #
-          # Change the end date of a customer's plan.
+          # Change the end date of a customer's plan. This is a Plans (deprecated) endpoint.
+          # New clients should implement using Contracts.
           #
           # @overload end_(customer_id:, customer_plan_id:, ending_before: nil, void_invoices: nil, void_stripe_invoices: nil, request_options: {})
           #
@@ -124,7 +127,8 @@ module MetronomeSDK
 
           # Lists a customer plans adjustments. See the
           # [price adjustments documentation](https://plans-docs.metronome.com/pricing/managing-plans/#price-adjustments)
-          # for details.
+          # for details. This is a Plans (deprecated) endpoint. New clients should implement
+          # using Contracts.
           #
           # @overload list_price_adjustments(customer_id:, customer_plan_id:, limit: nil, next_page: nil, request_options: {})
           #