So i tried to make a request using API to create a marker. It used to work on January 30 but now i always getting error 500 Internal server error. I just creating a simple tool for myself(at least for now) to create markers using obs extensions. But every request i specify throws a internal server error. I specify bearer token with user:edit:broadcast and all required json in body, but nothing works neither in my code, neither in any REST application i tested. Internal error everytime on posting this request.
Is the stream you are attempted to create a marker for actually live?
Yes and no. I tested both scenarios.
When it was online i tried in a dashboard and it told that unknown error, markers also says unknown error as well as my attempt to use api and nightbotâs.
Previously i tested it also when stream is offline, but then it gave me an error 404 with message that broadcast must be online, as well as other methods told me that broadcast must be online.
But now it sends me error 500 with no message instead.
When you are creating a marker:
Are you using a description, no description, or a description that is too long (itâs capped to 140 characters)
And/or whats your actual request?
I usually use empty description. I using app tool to check request before implementing it in code but it shows same error. My request is:
Post method
Url: https://api.twitch.tv/helix/streams/markers
Headers:
Content-Type: Application/json
Authorization: Bearer *******************
Body:
{âuser_idâ:â147603574â,âdescriptionâ:""}
Not sure exact method to show you request properly so i just sticked info i using in app to make post request. But the thing is that i donât think i doing something wrong since i canât create markers using even native methods, like through dashboard or chat command as wellâŚ
I will correct my reply. In chat command â/markerâ tells me when Iâm trying to create marker that I need to be online, but when I am it says unexpected error. API tells returns me error code 500 in any scenario
Successfully added a stream marker at 0:38:22: âtestâ
Seems to be working today!
YAY
1 Like
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.