The bouquets a customer may choose from. How they are shaped depends on the service: one running a playlist editor groups them by live/vod/series, one talking straight to a panel returns a flat list. A store can run both at once, so every service reports its own mode under plugins.
Add &plugin_id= to ask about one service. With exactly one service connected the top-level mode and bouquets are also filled in, so existing integrations keep working unchanged; with several, mode is per_plugin and you should read plugins. Every bouquet carries its plugin_id, so a store with several services can divide one flat list per service and send each line only its own service's share (update_bouquets refuses bouquets from another service).
Request Parameters
Field
Type
Required
Description
plugin_id
integer
Optional
Only this service's bouquets
Response Fields
Field
Type
Description
plugins
array
One entry per service: plugin_id, plugin_name, mode, bouquets. Read this when the store has more than one service.
mode
string
editor, panel, none, or per_plugin when several services are connected and each has its own
bouquets
object|array
Grouped by category in editor mode, flat array in panel mode, empty when mode is none or per_plugin
Bouquet Object
Field
Type
Description
id
integer
Bouquet ID
name
string
Internal bouquet name
display_name
string
Customer-facing display name — falls back to name if not set
category
string|null
live, vod, or series — editor mode only
sort_order
integer
Display sort order
plugin_id
integer|null
The service this bouquet belongs to. Only send a bouquet to a line on the same service — the ids mean nothing to another panel.