List Destinations
List destinations on the specified project. To learn more about destinations, read Destinations.
Listing, Sorting and Filtering Destinations
This endpoint returns the list of destinations in the specified project.
Sorting
The results from this endpoint can be ordered using the $orderby query parameter. Specify a list of field names, separated by commas
where each one can optionally specify asc or desc.
Sorting is valid on the following fields: created, createdBy, displayName, id, labels, name, status/state, updated, updatedBy
Filtering
There are two ways to filter the set of returned destinations from this endpoint - the first is to use the $filter query parameter, the second is to use the
$label_key and $label query parameters.
The $filter query parameter allows for destinations to be filtered on the basis of fields in the schema using OData query syntax.
See this document for more details on the syntax used.
Filters are valid on the following fields: created, createdBy, createdByEmail, createdByName, displayName, id, labels, name, status/state, updated, updatedBy, updatedByEmail, updatedByName
$label_key and $label are specific to querying destinations based on their labels. Labels are a set of key-value pairs that can be used to identify destinations with
any arbitrary metadata you want, specifically for the purpose of retrieving relevant subsets of destinations.
Examples:
?$top=10 - Returns only the first 10 destinations from the list.
?$orderby=name desc - Sorts destinations by name in descending order.
?$filter=name eq 'descriptive name' - Returns destinations that match the provided name.
?$orderby=created desc - Sorts destinations by creation date in descending order.
?$filter=created ge 2021-01-01T00:00:00Z - Returns destinations created after January 1, 2021.
?$label=studio=paravalley - Returns destinations with the label studio set to paravalley.
?$label=release-date~2023 - Returns destinations with the label release-date set to a value that contains 2023.
?$label_key=studio&label_key=release-date - Returns destinations with any value set for the studio label and the release-date label.
RBAC Capability Required: flow.destination.get
Authentication
Bearer authentication of the form Bearer <token>, where token is your
auth token.
Path parameters
Query parameters
n that limits the number of items returned from a collection.
The service returns the number of available items up to but not greater than the specified value n.@odata.nextLink in the result object to enumerate the collection -
it will be present only if there's more than one page of entities.Response
200 List of destinations
Show 5 propertiesHide 5 properties
Show 4 propertiesHide 4 properties
Show 2 propertiesHide 2 properties
Show 4 propertiesHide 4 properties
Show 10 propertiesHide 10 properties
Show value schemaHide value schema
Show 3 propertiesHide 3 properties
Show 16 propertiesHide 16 properties
List of IP addresses that are allowed to connect, if the transport type supports it.
The following transport types can use the allowList field: SRTListener.
Encryption standard for the transport, if the transport type supports it.
The following transport types can use the encryptionStandard field: SRTCaller, SRTListener.
This field cannot be modified, only set during creation.
Add an IP resource reservation for the transport. This is necessary for <glossary:source>s and <glossary:destination>s that need to access a <<glossary:SaaS site>> through a public IP address or public URL.
The following transport types can use the ipResource field: SRTListener.
This field cannot be modified, only set during creation.
Show 1 propertyHide 1 property
Type of IP resource reservation:
Externalmeans reserve a public IP address,Internalmeans reserve an internal IP address (please contact MediaKind personnel for usage), andNonemeans don't try to reserve an IP resource.
Transports between on-prem devices don't need to explicitly reserve an IP address.
Minimum Latency, in seconds, for the transport, if the transport type supports it.
The following transport types can use the latency field: SRTCaller, SRTListener.
This field cannot be modified, only set during creation.
Maximum bitrate, in bits per second, expected through each individual connection to the Listener.
The following transport types can use the maxBitrate field: SRTCaller, SRTListener.
This field cannot be modified, only set during creation.
Maximum number of connections for a Listener destination. Overrides the flow output maxConnections setting if present.
The following transport types can use the maxConnections field: SRTCaller, SRTListener.
This field cannot be modified, only set during creation.
Maximum Overhead Bandwidth, as an integer (e.g., 100), for the transport, if the transport type supports it.
The following transport types can use the maxOverheadBandwidth field: SRTCaller, SRTListener.
This field cannot be modified, only set during creation.
Password phrase for the transport, if the transport type supports it.
The following transport types can use the passPhrase field: SRTCaller, SRTListener.
Password for HLS pull authentication.
For sources, this field can be updated via PATCH when the transport type is HLSPullInput. For all other transport types, it can only be set during creation.
Port for the transport, if the transport type supports it.
The following transport types need the port field: SRTListener.
This field cannot be modified, only set during creation.
The SRT stream ID sent by the caller during the SRT handshake. Used by the listener to identify or route the stream. Optional.
The following transport types can use the streamId field: SRTCaller.
This field cannot be modified, only set during creation.
The RTMP stream key (appended to the URL when connecting).
The following transport types need the streamKey field: RTMPPushOutput.
This field cannot be modified, only set during creation.
The URL for the transport, if the transport type supports it.
The following transport types need the url field: SRTCaller, UDP, SDI, HLSPullInput, RTMPPushOutput.
For sources, this field can be updated via PATCH when the transport type is SRTCaller or HLSPullInput. For all other transport types, and for destinations, it can only be set during creation.
url instead. This is provided for backwards compatibility and will be removed in a future release. If urls is used, only the first URL will be considered. If both url and urls are provided, url takes precedence.Username for HLS pull authentication.
For sources, this field can be updated via PATCH when the transport type is HLSPullInput. For all other transport types, it can only be set during creation.
Show 3 propertiesHide 3 properties
Show 1 propertyHide 1 property
The URLs configured or allocated/discovered for the transport.
Where the spec.transport.url field is supported by the transport type (e.g. an SRTCaller), the urls field will contain that data. Where the system automatically allocates/discovers one or more URLs (e.g. an SRTListener), the urls field will contain that data.