From 2a945ad70681561ff563126227b3968807047895 Mon Sep 17 00:00:00 2001
From: "ci.datadog-api-spec" <packages@datadoghq.com>
Date: Thu, 29 Oct 2026 16:06:37 +0000
Subject: [PATCH] Regenerate client from commit 3a76da8 of spec repo

---
 .generator/schemas/v2/openapi.yaml            | 22 ++++++++++++++++---
 .../v2/api/rum_replay_sessions_api.rb         |  2 +-
 2 files changed, 20 insertions(+), 4 deletions(-)

diff --git a/.generator/schemas/v2/openapi.yaml b/.generator/schemas/v2/openapi.yaml
index d35fd19b9083..7fb39dd70328 100644
--- a/.generator/schemas/v2/openapi.yaml
+++ b/.generator/schemas/v2/openapi.yaml
@@ -223334,15 +223334,29 @@ paths:
             example: 1048576
             format: int64
             type: integer
-        - description: Paging token for pagination.
+        - description: |-
+            Token of the next page from the `X-Paging` header of the previous response.
+            Send it without changes, URL-encoded in the query string. Omit it to get the first page.
           in: query
           name: paging
           schema:
-            example: eyJuZXh0IjoiYWJjMTIzIn0
             type: string
       responses:
         "200":
           description: OK
+          headers:
+            X-Has-More-Segments-To-Fetch:
+              description: |-
+                `true` if the view has more segments to get.
+                To get them, send the request again with the `paging` query parameter until this header is `false`.
+              schema:
+                type: boolean
+            X-Paging:
+              description: |-
+                Token of the next page to send in the `paging` query parameter.
+                Present only when `X-Has-More-Segments-To-Fetch` is `true`.
+              schema:
+                type: string
         "429":
           $ref: "#/components/responses/TooManyRequestsResponse"
       security:
@@ -256339,7 +256353,9 @@ tags:
     name: Rum Replay Heatmaps
   - description: Create and manage playlists of RUM replay sessions. Organize, categorize, and share collections of replay sessions for analysis and collaboration.
     name: Rum Replay Playlists
-  - description: Retrieve segments for RUM replay sessions. Access session replay data stored in event platform or blob storage.
+  - description: |-
+      Retrieve segments for RUM replay sessions.
+      Access session replay data stored in event platform or blob storage.
     name: Rum Replay Sessions
   - description: Track and manage RUM replay session viewership. Monitor who watches replay sessions and maintain watch history for audit and analytics purposes.
     name: Rum Replay Viewership
diff --git a/lib/datadog_api_client/v2/api/rum_replay_sessions_api.rb b/lib/datadog_api_client/v2/api/rum_replay_sessions_api.rb
index 665a18c34987..53d4895cb899 100644
--- a/lib/datadog_api_client/v2/api/rum_replay_sessions_api.rb
+++ b/lib/datadog_api_client/v2/api/rum_replay_sessions_api.rb
@@ -41,7 +41,7 @@ def get_segments(view_id, session_id, opts = {})
     # @option opts [String] :source Storage source: 'event_platform' or 'blob'.
     # @option opts [Integer] :ts Server-side timestamp in milliseconds.
     # @option opts [Integer] :max_list_size Maximum size in bytes for the segment list.
-    # @option opts [String] :paging Paging token for pagination.
+    # @option opts [String] :paging Token of the next page from the `X-Paging` header of the previous response. Send it without changes, URL-encoded in the query string. Omit it to get the first page.
     # @return [Array<(nil, Integer, Hash)>] nil, response status code and response headers
     def get_segments_with_http_info(view_id, session_id, opts = {})