-
Notifications
You must be signed in to change notification settings - Fork 6
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.
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
Check AutoMod Status various issues #527
Comments
|
Revison a body of as per the docs 500's as user 23422 doesn't eixst. additionally omits the required add If you specify the wrong broadcaster_id fix the 403 to be more descriptive If the body is invalid fix the error to include a validation error |
|
Additionally using a username instead of a numeric ID in the This endpoint needs some validation work Results in isntead of |
|
Summary of issues
Should be
should be
Missing User User is a word Expected User ID deosn't exist, or is TOS'ed from the service. (I don't have handy TOS'ed ID to test this) Result: You specify one good payload and one bad payload Result: Expected something like You specify something weird: Result: 200 OK with Should be an error as no Documentation Error https://dev.twitch.tv/docs/api/reference#check-automod-status The Example does not include a |
|
Superseeded by #530 for clarity |
Brief description
Currently
Check AutoMod Statusis broken.It either returns
My token, correct scope, wrong broadcaster_id
https://api.twitch.tv/helix/moderation/enforcements/status?broadcaster_id=26610234My token, correct scope, correct broadcaster_id
https://api.twitch.tv/helix/moderation/enforcements/status?broadcaster_id=15185913How to reproduce
Post to
https://api.twitch.tv/helix/moderation/enforcements/statuswith body as follows, or the example from the docs.
Expected behavior
Correct error message when the user_id in the token is not the user_id in the query string
Correct response when using the right data reporting enforcement values, not an error
Additional context or questions
Original report
https://discuss.dev.twitch.tv/t/keep-getting-forbidden-status-trying-to-call-the-api/34972/
The text was updated successfully, but these errors were encountered: