# (Developers: Please specify valid set of arguments)

**URL:** <https://discuss.dev.twitch.com/t/developers-please-specify-valid-set-of-arguments/27015>\
**Category:** API\
**Created:** [July 9, 2020, 10:06am UTC](https://discuss.dev.twitch.com/t/developers-please-specify-valid-set-of-arguments/27015 "2020-07-09T10:06:00Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![BarryCarlyon](https://d3ovvz0v2ajtpu.cloudfront.net/user_avatar/discuss.dev.twitch.com/barrycarlyon/32/253_2.png) [@BarryCarlyon](https://discuss.dev.twitch.com/u/BarryCarlyon)\
**Post date:** [July 9, 2020, 1:09pm UTC](https://discuss.dev.twitch.com/t/developers-please-specify-valid-set-of-arguments/27015/4 "2020-07-09T13:09:21Z")

</div>

It’s covered in the iframe attributes

```auto
|`src`|string|The iframe `src` URL string should be https://player.twitch.tv/ with one of these required query string parameters:

* `channel` – (string) Name of the channel, for a live stream.
* `video` – (string) Video ID (for past broadcasts, highlights, and video uploads). In this context (the video player), the video ID must have a “v” prefix.
* `collection` - (string) Collection ID, for a collection of videos.

If both `video` and `collection` are specified, the specified collection starts playing from the specified video. If the video is not in the collection, `collection` is ignored and the specified video is played.

If `channel` is specified along with `video` and/or `collection` , only `channel` is used.|
| --- | --- |

```

Could be clearer but the examples cover the three variations

> [@TAPgiles](#):
>
> So now it works for https, but still just gives me the gray embed saying it wouldn’t load, for http. Could you help me with how I would go about fixing that? (I tried just using // for the iframe instead of https://, but have the same problem.)

HTTPS is now required

> [@Twitch Embedded Player Updates in 2020](https://discuss.dev.twitch.com/t/twitch-embedded-player-updates-in-2020/23956/1):
>
> ### SSL certificate required
> 
> With this new configuration, _Twitch embeds can only be embedded on https sites_ . Non-https sites should plan accordingly if they intend on continued use of any Twitch embed experiences that are currently in operation on their site.

---

_[View the full topic](https://discuss.dev.twitch.com/t/developers-please-specify-valid-set-of-arguments/27015)._