From f073f2fc996db99a49e43b9c848a55eb78d650ea Mon Sep 17 00:00:00 2001 From: James Sandford Date: Mon, 15 Jun 2026 16:14:45 +0100 Subject: [PATCH 1/2] Add `include_object_timerange` option to webhooks, matching that on the HTTP API sem-ver: feature --- api/schemas/webhook.json | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/api/schemas/webhook.json b/api/schemas/webhook.json index 1948aa59..467ff358 100644 --- a/api/schemas/webhook.json +++ b/api/schemas/webhook.json @@ -82,6 +82,10 @@ "description": "Whether to include storage metadata in the `get_urls` property in `flows/segments_added` events. This option is the same as the `verbose_storage` query parameter for the [/flows/{flowId}/segments](#/operations/GET_flows-flowId-segments) API endpoint.", "type": "boolean" }, + "include_object_timerange": { + "description": "If set to `true`, the underlying object's timerange should appear in `flows/segments_added` events (if it differs from the Flow Segment's `timerange`). Assume `false` if omitted. This option is the same as the `include_object_timerange` query parameter for the [/flows/{flowId}/segments](#/operations/GET_flows-flowId-segments) API endpoint.", + "type": "boolean" + }, "tags": { "$ref": "tags.json" } From 688fcba5473aeeb85feef1cfc0d483bb37c37a7a Mon Sep 17 00:00:00 2001 From: James Sandford Date: Mon, 15 Jun 2026 16:16:53 +0100 Subject: [PATCH 2/2] Always return `object_timerange` when `include_object_timerange` is set --- api/TimeAddressableMediaStore.yaml | 4 ++-- api/schemas/webhook.json | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/api/TimeAddressableMediaStore.yaml b/api/TimeAddressableMediaStore.yaml index 3b4400e1..246c0027 100644 --- a/api/TimeAddressableMediaStore.yaml +++ b/api/TimeAddressableMediaStore.yaml @@ -1792,7 +1792,7 @@ paths: - name: include_object_timerange in: query description: | - If set to `true`, the underlying object's timerange should appear in the response (if it differs from the segment timerange). + If set to `true`, the underlying object's timerange should appear in the response. Assume `false` if omitted. schema: type: boolean @@ -1919,7 +1919,7 @@ paths: - name: include_object_timerange in: query description: | - If set to `true`, the underlying object's timerange should appear in the response (if it differs from the Flow Segment's `timerange`). + If set to `true`, the underlying object's timerange should appear in the response. Assume `false` if omitted. schema: type: boolean diff --git a/api/schemas/webhook.json b/api/schemas/webhook.json index 467ff358..e57431fc 100644 --- a/api/schemas/webhook.json +++ b/api/schemas/webhook.json @@ -83,7 +83,7 @@ "type": "boolean" }, "include_object_timerange": { - "description": "If set to `true`, the underlying object's timerange should appear in `flows/segments_added` events (if it differs from the Flow Segment's `timerange`). Assume `false` if omitted. This option is the same as the `include_object_timerange` query parameter for the [/flows/{flowId}/segments](#/operations/GET_flows-flowId-segments) API endpoint.", + "description": "If set to `true`, the underlying object's timerange should appear in `flows/segments_added` events. Assume `false` if omitted. This option is the same as the `include_object_timerange` query parameter for the [/flows/{flowId}/segments](#/operations/GET_flows-flowId-segments) API endpoint.", "type": "boolean" }, "tags": {