Skip to content

Update OpenAPI specs to v239.87.5 #2178

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
stream-ci-bot merged 1 commit into from
Oct 22, 2026
Merged

Update OpenAPI specs to v239.87.5 #2178

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion openapi/chat-openapi-clientside.json
View file
Open in desktop

Large diffs are not rendered by default.

52 changes: 43 additions & 9 deletions openapi/chat-openapi-clientside.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1114,6 +1114,15 @@ components:
replies:
type: boolean
x-stream-index: 001.002.008
scheduled_messages_max_lead_time_seconds:
description: How far ahead, in seconds, a message can be scheduled. Present
only when scheduled messages are enabled for the app. A later scheduled_at
returns error code 116 (scheduled_at_too_far), whose max_lead_time_seconds
carries the same value
format: int32
title: Scheduled messages max lead time seconds
type: integer
x-stream-index: "004"
scheduled_messages_max_per_channel:
description: Maximum number of scheduled messages (scheduled or sending)
a user can have in this channel. Present only when scheduled messages
Expand All @@ -1122,6 +1131,23 @@ components:
title: Scheduled messages max per channel
type: integer
x-stream-index: "003"
scheduled_messages_max_per_user:
description: Maximum number of scheduled messages (scheduled or sending)
a user can have across all channels. Present only when scheduled messages
are enabled for the app. Scheduling more returns error code 118 (scheduled_limit_user)
format: int32
title: Scheduled messages max per user
type: integer
x-stream-index: "006"
scheduled_messages_min_lead_time_seconds:
description: Minimum time ahead, in seconds, a message is scheduled for.
Present only when scheduled messages are enabled for the app. A future
scheduled_at closer than this is moved later, to the first whole minute
at least this far ahead; it is never rejected
format: int32
title: Scheduled messages min lead time seconds
type: integer
x-stream-index: "005"
search:
type: boolean
x-stream-index: 001.002.006
Expand Down Expand Up @@ -14247,10 +14273,14 @@ components:
$ref: '#/components/schemas/MessageRequest'
x-stream-index: "001"
scheduled_at:
description: 'When set, the message is not sent now: it is stored and sent
at this time (UTC). The response then carries scheduled_message. Must
be at least 1 minute and at most the app''s maximum lead time (120 days
by default) from now. Slash commands cannot be scheduled'
description: 'When set to a future time, the message is not sent now: it
is stored and sent at that time (UTC), rounded up to the first whole minute
that is at least 1 minute from now, never earlier than requested. The
response then carries scheduled_message with the rounded time. Must be
at most the app''s maximum lead time (120 days by default) from now. A
time that is now or in the past sends the message now as if scheduled_at
was not set, unless the request''s message ID belongs to a scheduled message
that was canceled or already sent. Slash commands cannot be scheduled'
format: date-time
title: Scheduled at
type: string
Expand Down Expand Up @@ -14300,8 +14330,10 @@ components:
x-stream-index: "001"
scheduled_message:
$ref: '#/components/schemas/ScheduledMessageResponse'
description: The scheduled message. Only set when the request had scheduled_at;
message then holds the content as it will be sent and is not in the channel
description: The scheduled message. Only set when the request scheduled
the message; message then holds the content as it will be sent and is
not in the channel. Not set when scheduled_at was now or in the past and
the message was sent now
title: Scheduled message
x-stream-index: "006"
required:
Expand Down Expand Up @@ -15934,8 +15966,10 @@ components:
title: Message
x-stream-index: "002"
scheduled_at:
description: New send time (UTC). Must be at least 1 minute and at most
the app's maximum lead time from now
description: New send time (UTC). Must be in the future and at most the
app's maximum lead time from now. Rounded up to the first whole minute
that is at least 1 minute from now, never earlier than requested. Resending
the stored time leaves it unchanged
format: date-time
title: Scheduled at
type: string
Expand Down Expand Up @@ -18069,7 +18103,7 @@ components:
type: apiKey
info:
title: Stream API
version: v239.87.4
version: v239.87.5
x-stream-breaking-changes:
go:
- CHA-3441 (2026-10-08)
Expand Down
2 changes: 1 addition & 1 deletion openapi/chat-openapi.json
View file
Open in desktop

Large diffs are not rendered by default.

52 changes: 43 additions & 9 deletions openapi/chat-openapi.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2617,6 +2617,15 @@ components:
replies:
type: boolean
x-stream-index: 001.002.008
scheduled_messages_max_lead_time_seconds:
description: How far ahead, in seconds, a message can be scheduled. Present
only when scheduled messages are enabled for the app. A later scheduled_at
returns error code 116 (scheduled_at_too_far), whose max_lead_time_seconds
carries the same value
format: int32
title: Scheduled messages max lead time seconds
type: integer
x-stream-index: "004"
scheduled_messages_max_per_channel:
description: Maximum number of scheduled messages (scheduled or sending)
a user can have in this channel. Present only when scheduled messages
Expand All @@ -2625,6 +2634,23 @@ components:
title: Scheduled messages max per channel
type: integer
x-stream-index: "003"
scheduled_messages_max_per_user:
description: Maximum number of scheduled messages (scheduled or sending)
a user can have across all channels. Present only when scheduled messages
are enabled for the app. Scheduling more returns error code 118 (scheduled_limit_user)
format: int32
title: Scheduled messages max per user
type: integer
x-stream-index: "006"
scheduled_messages_min_lead_time_seconds:
description: Minimum time ahead, in seconds, a message is scheduled for.
Present only when scheduled messages are enabled for the app. A future
scheduled_at closer than this is moved later, to the first whole minute
at least this far ahead; it is never rejected
format: int32
title: Scheduled messages min lead time seconds
type: integer
x-stream-index: "005"
search:
type: boolean
x-stream-index: 001.002.006
Expand Down Expand Up @@ -19913,10 +19939,14 @@ components:
type: object
x-stream-index: "005"
scheduled_at:
description: 'When set, the message is not sent now: it is stored and sent
at this time (UTC). The response then carries scheduled_message. Must
be at least 1 minute and at most the app''s maximum lead time (120 days
by default) from now. Slash commands cannot be scheduled'
description: 'When set to a future time, the message is not sent now: it
is stored and sent at that time (UTC), rounded up to the first whole minute
that is at least 1 minute from now, never earlier than requested. The
response then carries scheduled_message with the rounded time. Must be
at most the app''s maximum lead time (120 days by default) from now. A
time that is now or in the past sends the message now as if scheduled_at
was not set, unless the request''s message ID belongs to a scheduled message
that was canceled or already sent. Slash commands cannot be scheduled'
format: date-time
title: Scheduled at
type: string
Expand Down Expand Up @@ -19973,8 +20003,10 @@ components:
x-stream-index: "002"
scheduled_message:
$ref: '#/components/schemas/ScheduledMessageResponse'
description: The scheduled message. Only set when the request had scheduled_at;
message then holds the content as it will be sent and is not in the channel
description: The scheduled message. Only set when the request scheduled
the message; message then holds the content as it will be sent and is
not in the channel. Not set when scheduled_at was now or in the past and
the message was sent now
title: Scheduled message
x-stream-index: "006"
required:
Expand Down Expand Up @@ -23159,8 +23191,10 @@ components:
title: Message
x-stream-index: "002"
scheduled_at:
description: New send time (UTC). Must be at least 1 minute and at most
the app's maximum lead time from now
description: New send time (UTC). Must be in the future and at most the
app's maximum lead time from now. Rounded up to the first whole minute
that is at least 1 minute from now, never earlier than requested. Resending
the stored time leaves it unchanged
format: date-time
title: Scheduled at
type: string
Expand Down Expand Up @@ -25581,7 +25615,7 @@ components:
type: apiKey
info:
title: Stream API
version: v239.87.4
version: v239.87.5
x-stream-breaking-changes:
go:
- CHA-3441 (2026-10-08)
Expand Down
2 changes: 1 addition & 1 deletion openapi/clientside-api.json
View file
Open in desktop

Large diffs are not rendered by default.

52 changes: 43 additions & 9 deletions openapi/clientside-api.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8390,6 +8390,15 @@ components:
replies:
type: boolean
x-stream-index: 001.002.008
scheduled_messages_max_lead_time_seconds:
description: How far ahead, in seconds, a message can be scheduled. Present
only when scheduled messages are enabled for the app. A later scheduled_at
returns error code 116 (scheduled_at_too_far), whose max_lead_time_seconds
carries the same value
format: int32
title: Scheduled messages max lead time seconds
type: integer
x-stream-index: "004"
scheduled_messages_max_per_channel:
description: Maximum number of scheduled messages (scheduled or sending)
a user can have in this channel. Present only when scheduled messages
Expand All @@ -8398,6 +8407,23 @@ components:
title: Scheduled messages max per channel
type: integer
x-stream-index: "003"
scheduled_messages_max_per_user:
description: Maximum number of scheduled messages (scheduled or sending)
a user can have across all channels. Present only when scheduled messages
are enabled for the app. Scheduling more returns error code 118 (scheduled_limit_user)
format: int32
title: Scheduled messages max per user
type: integer
x-stream-index: "006"
scheduled_messages_min_lead_time_seconds:
description: Minimum time ahead, in seconds, a message is scheduled for.
Present only when scheduled messages are enabled for the app. A future
scheduled_at closer than this is moved later, to the first whole minute
at least this far ahead; it is never rejected
format: int32
title: Scheduled messages min lead time seconds
type: integer
x-stream-index: "005"
search:
type: boolean
x-stream-index: 001.002.006
Expand Down Expand Up @@ -36585,10 +36611,14 @@ components:
$ref: '#/components/schemas/MessageRequest'
x-stream-index: "001"
scheduled_at:
description: 'When set, the message is not sent now: it is stored and sent
at this time (UTC). The response then carries scheduled_message. Must
be at least 1 minute and at most the app''s maximum lead time (120 days
by default) from now. Slash commands cannot be scheduled'
description: 'When set to a future time, the message is not sent now: it
is stored and sent at that time (UTC), rounded up to the first whole minute
that is at least 1 minute from now, never earlier than requested. The
response then carries scheduled_message with the rounded time. Must be
at most the app''s maximum lead time (120 days by default) from now. A
time that is now or in the past sends the message now as if scheduled_at
was not set, unless the request''s message ID belongs to a scheduled message
that was canceled or already sent. Slash commands cannot be scheduled'
format: date-time
title: Scheduled at
type: string
Expand Down Expand Up @@ -36638,8 +36668,10 @@ components:
x-stream-index: "001"
scheduled_message:
$ref: '#/components/schemas/ScheduledMessageResponse'
description: The scheduled message. Only set when the request had scheduled_at;
message then holds the content as it will be sent and is not in the channel
description: The scheduled message. Only set when the request scheduled
the message; message then holds the content as it will be sent and is
not in the channel. Not set when scheduled_at was now or in the past and
the message was sent now
title: Scheduled message
x-stream-index: "006"
required:
Expand Down Expand Up @@ -40941,8 +40973,10 @@ components:
title: Message
x-stream-index: "002"
scheduled_at:
description: New send time (UTC). Must be at least 1 minute and at most
the app's maximum lead time from now
description: New send time (UTC). Must be in the future and at most the
app's maximum lead time from now. Rounded up to the first whole minute
that is at least 1 minute from now, never earlier than requested. Resending
the stored time leaves it unchanged
format: date-time
title: Scheduled at
type: string
Expand Down Expand Up @@ -44330,7 +44364,7 @@ components:
type: apiKey
info:
title: Stream API
version: v239.87.4
version: v239.87.5
x-stream-breaking-changes:
go:
- CHA-3441 (2026-10-08)
Expand Down
2 changes: 1 addition & 1 deletion openapi/moderation-clientside-api.json
View file
Open in desktop

Large diffs are not rendered by default.

28 changes: 27 additions & 1 deletion openapi/moderation-clientside-api.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1479,6 +1479,15 @@ components:
replies:
type: boolean
x-stream-index: 001.002.008
scheduled_messages_max_lead_time_seconds:
description: How far ahead, in seconds, a message can be scheduled. Present
only when scheduled messages are enabled for the app. A later scheduled_at
returns error code 116 (scheduled_at_too_far), whose max_lead_time_seconds
carries the same value
format: int32
title: Scheduled messages max lead time seconds
type: integer
x-stream-index: "004"
scheduled_messages_max_per_channel:
description: Maximum number of scheduled messages (scheduled or sending)
a user can have in this channel. Present only when scheduled messages
Expand All @@ -1487,6 +1496,23 @@ components:
title: Scheduled messages max per channel
type: integer
x-stream-index: "003"
scheduled_messages_max_per_user:
description: Maximum number of scheduled messages (scheduled or sending)
a user can have across all channels. Present only when scheduled messages
are enabled for the app. Scheduling more returns error code 118 (scheduled_limit_user)
format: int32
title: Scheduled messages max per user
type: integer
x-stream-index: "006"
scheduled_messages_min_lead_time_seconds:
description: Minimum time ahead, in seconds, a message is scheduled for.
Present only when scheduled messages are enabled for the app. A future
scheduled_at closer than this is moved later, to the first whole minute
at least this far ahead; it is never rejected
format: int32
title: Scheduled messages min lead time seconds
type: integer
x-stream-index: "005"
search:
type: boolean
x-stream-index: 001.002.006
Expand Down Expand Up @@ -9822,7 +9848,7 @@ components:
type: apiKey
info:
title: Stream API
version: v239.87.4
version: v239.87.5
x-stream-breaking-changes:
go:
- CHA-3441 (2026-10-08)
Expand Down
2 changes: 1 addition & 1 deletion openapi/moderation-openapi.json
View file
Open in desktop

Large diffs are not rendered by default.

28 changes: 27 additions & 1 deletion openapi/moderation-openapi.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1048,6 +1048,15 @@ components:
replies:
type: boolean
x-stream-index: 001.002.008
scheduled_messages_max_lead_time_seconds:
description: How far ahead, in seconds, a message can be scheduled. Present
only when scheduled messages are enabled for the app. A later scheduled_at
returns error code 116 (scheduled_at_too_far), whose max_lead_time_seconds
carries the same value
format: int32
title: Scheduled messages max lead time seconds
type: integer
x-stream-index: "004"
scheduled_messages_max_per_channel:
description: Maximum number of scheduled messages (scheduled or sending)
a user can have in this channel. Present only when scheduled messages
Expand All @@ -1056,6 +1065,23 @@ components:
title: Scheduled messages max per channel
type: integer
x-stream-index: "003"
scheduled_messages_max_per_user:
description: Maximum number of scheduled messages (scheduled or sending)
a user can have across all channels. Present only when scheduled messages
are enabled for the app. Scheduling more returns error code 118 (scheduled_limit_user)
format: int32
title: Scheduled messages max per user
type: integer
x-stream-index: "006"
scheduled_messages_min_lead_time_seconds:
description: Minimum time ahead, in seconds, a message is scheduled for.
Present only when scheduled messages are enabled for the app. A future
scheduled_at closer than this is moved later, to the first whole minute
at least this far ahead; it is never rejected
format: int32
title: Scheduled messages min lead time seconds
type: integer
x-stream-index: "005"
search:
type: boolean
x-stream-index: 001.002.006
Expand Down Expand Up @@ -7105,7 +7131,7 @@ components:
type: apiKey
info:
title: Stream API
version: v239.87.4
version: v239.87.5
x-stream-breaking-changes:
go:
- CHA-3441 (2026-10-08)
Expand Down
2 changes: 1 addition & 1 deletion openapi/moderation-serverside-api.json
View file
Open in desktop

Large diffs are not rendered by default.

Loading
Loading