160 results found
-
anonsubgift, anonsubmysterygift, anongiftpaidupgrade are documented but never occur https://dev.twitch.tv/docs/irc/tags#usernotice-twitch-tags documents anonsubgift and anongiftpaidupgrade. I found this announcement post https://discuss.dev.twitch.tv/t/anonymous-sub-gifting-to-launch-11-15-launch-details/18683 saying that apparently it was temporarily disabled as a workaround. As far as I can tell to this day the workaround is used. The documentation should be updated to remove the originally planned but never put into service types, and instead document that anonymous gifts come from AnAnonymousGifter.
4 votesAll USERNOTICE tags that have been removed are no longer listed:
https://dev.twitch.tv/docs/chat/irc#usernotice-twitch-tags
-
Remove jQuery from the GA Example The examples for Google Analytics suggest using jQuery. Which is extra bloat if an extension hasn't use jQuery to start with and can lead to confusion
4 votes -
New IRC tag "msg-params-gift-months" in docs is actually "msg-param-gift-months" The recent announcement "Updates to PubSub Messages and IRC for Multi-Month Subscription Gifting" (https://discuss.dev.twitch.tv/t/updates-to-pubsub-messages-and-irc-for-multi-month-subscription-gifting/26873) and IRC Tags docs (https://dev.twitch.tv/docs/irc/tags#usernotice-twitch-tags) lists the new "msg-params-gift-months" tag, but like all other so far it's actually singular "param" not "params" ("msg-param-gift-months") in reality.
4 votes -
Helix Users docs showing optional scope as required The Helix Users endpoint docs state the "user:read:email" scope as required, although it is an optional scope if you also need the users email returned.
4 votes -
Documentation not updated for oAuth changes on Helix As per
https://discuss.dev.twitch.tv/t/requiring-oauth-for-helix-twitch-api-endpoints/23916
None of the documentation is updated to reflect this change.
Yes it's not required yet. But it's good practice for new developers to be using the new oAuth procedure now
4 votes -
4 votes
-
The Validate requests endpoint omits the expiry from the example response URL
https://dev.twitch.tv/docs/authentication#validating-requests
{
"clientid": "<your client ID>",
"login": "<authorized user login>",
"scopes": [
"<requested scopes>"
],
"userid": "<authorized user ID>"
}should be
{
"clientid": "<your client ID>",
"login": "<authorized user login>",
"scopes": [
"<requested scopes>"
],
"userid": "<authorized user ID>",
"expires_in": timeInSeconds
}4 votes -
HTTP Response codes unclear From: https://github.com/twitchdev/issues/issues/69
Brief descriptionSome endpoints return a 204 code no content.
But this is only highlighted in the example responses and not in the "main documentation"For example
https://dev.twitch.tv/docs/extensions/reference#send-extension-pubsub-message
https://dev.twitch.tv/docs/extensions/reference#send-extension-chat-messageEach endpoint documented could be extended to include usual HTTP response codes.
Expected documentation
The expected response code for success when theres no body response
Common non 2xx codes for the endpoints4 votes -
Webhooks limits: ambiguous From: https://github.com/twitchdev/issues/issues/65
Brief description
https://dev.twitch.tv/docs/api/webhooks-guide
Limits: By default, each client ID can have at most 10,000 subscriptions. Also, you can subscribe to the same topic at most 3 times.
Seems to be ambiguous to a lot of developers, they seem to think the that "3 times" means they can renew it 3 times then they are SOOL
Expected documentation
Limits: Each client ID can have at most 10,000 subscriptions. Where you can have 3 active subscriptions to a topic at the same time. Where an active subscription is defined as a topic/callback pair.
4 votes -
Get All Chat Emoticons From: https://github.com/twitchdev/issues/issues/10
Brief description
Docs state the "images" is an array
{
"links": {
"self": "http://api.twitch.tv/kraken/chat/emoticons"
},
"emoticons": [
{
"id": 115390,
"regex": "TwitchLit",
"images": [
{
"width": 28,
"height": 28,
"url": "https://static-cdn.jtvnw.net/jtvuserpictures/emoticon-115390-src-b577ded8522fc1a1-28x28.png",
"emoticonset": 19151
}
]
},
{
"id": 80393,
"regex": "Kappa",
"images": [
{
"width": 28,
"height": 28,
"url": "https://static-cdn.jtvnw.net/jtv_user_pictures/emoticon-80393-src-cf7c8d03a4c5cb75-28x28.png",
"emoticon_set": 15940
}
]
}
]
}Expected documentation
…{ "_links": { "self": "http://api.twitch.tv/kraken/chat/emoticons" }, "emoticons": [ { "id": 115390, "regex": "TwitchLit", "images": { "width": 28, "height": 28, "url": "https://static-cdn.jtvnw.net/jtv_user_pictures/emoticon-115390-src-b577ded8522fc1a1-28x28.png", "emoticon_set": 19151 } }, { "id": 80393, "regex": "Kappa",4 votes -
Missing `channel:moderate` scope There are missing "channel:moderate" scope required in Channel Ban (channel.ban) and Channel Unban (channel.unban) EventSubs
https://dev.twitch.tv/docs/eventsub/eventsub-subscription-types/#channelban
https://dev.twitch.tv/docs/eventsub/eventsub-subscription-types/#channelunban
3 votes -
correct Content-Type to Content-Length This page has this line
"Your response must return a 200 status code, the response body must contain the raw challenge value, and you must set the Content-Type response header to the length of the challenge value. If successful, your subscription is enabled."
I have assumed that this is meant to say "Content-Length" rather than "Content-Type", because using the challenge length as a Content-Type is not a valid content type.
3 votes -
Wrong documentation about python webserver port In the section "HTTPS on localhost: the easy way" it says to launch python webserver with command: "python3 -m http.server", but this will launch it on port 8000, not 8080 like it says in the next sentence:
Then, change your base URI in the Asset Hosting page of your control panel from https://localhost:8080 to http://localhost:8080.
3 votes -
API status page is gated by Atlassian login? Hey Twitch team -- the Twitch API "status page" link at the bottom of the page at https://dev.twitch.tv/docs/api/guide/#twitch-api-health currently links to a login-gated Atlassian page.
I tried using my work's Atlassian account, but even with that, I can't view the Twitch API health page.
Any way to make it publicly accessible?
3 votesThat page is no longer active, so we have removed it from the footer of the website
-
Missing JSON field for refresh token If successful, the refresh token response includes a expires_in value. that is not shown in the example and is a very useful field.
3 votes -
No info about "expires_in" field in response of refresh request Hello, thanks for this great page! But there is no info about "expiresin" field when using refresh token. Refresh request returns "expiresin" field too. Am I doing something wrong?
3 votes -
Wrong description in Create Prediction Description of 'outcomes' in 'Create Prediction' says that array size must be 2. Isn't the current limit between 2 and 10?
3 votes -
Host example code in an official Twitch organization on GitHub This tutorial looks very unprofessional.
The example GitHub repository is not available from an official Twitch source, but lives in someone's personal
account at:
https://github.com/sonia145These GitHub organizations would be better alternatives:
https://github.com/twitchtv
https://github.com/twitchdev3 voteshttps://github.com/twitchdev/
-
IRC Landing page/guide -> twitchapps.com https://dev.twitch.tv/docs/irc
As a getting started/IRC docs landing page is confusing new developers
As it references
The token to authenticate your chatbot with Twitch's servers. Generate this with https://twitchapps.com/tmi/ (a Twitch community-driven wrapper around the Twitch API), while logged in to your chatbot account. The token will be an alphanumeric string.
And doesn't reference anything about the "right way" to auth/scopes needed
Until the end of the guide.
Authentication using not a third party site should be more prevalent in the guide.
3 votes -
Get Custom Reward Redemptions "missing redemption status" Declares that only broadcasterid and rewardid are required.
A call to
results in
{
"error": "Bad Request",
"status": 400,
"message": "missing redemption status"
}The documentation lists status as not required
3 votes
- Don't see your idea?