Add a transport filter to the status endpoint
It would be nice if you could filter the response of the subscription status endpoint with a transport filter (e.g. "?transport=websocket").
Its not a big deal at the moment because there only is one transport (webhooks) available but with more transports added down the line this would be a huge QoL improvement.
Syzuna
shared this idea
-
AzazaelLoki
commented
Tagging along with this, additional query parameters on the Get Eventsub endpoint would be a great addition. Right now I don't have a problem going through the list manually but down the line it would be nice to just EventSubs by a channel ID or by a type.
-
Syzuna
commented
Yes this is about the Get Eventsub Subscriptions endpoint.
I would use this to be able to monitor my subscriptions based on their transport type.
E.g. if you have multiple systems/services in your application that use different transport types this would help the service only monitoring the subscriptions that use their transport type.
I dont see the point of a webhook server having to paginate 40-50 pages just to accumulate the subscriptions that even don't call into it and that is where this filter would really help.The same kinda goes for my other uservoice regarding more filters.
It also would really help debugging not working subscriptions or weird behavior of subscriptions
-
Adminecressey
(Admin, Twitch)
commented
Hi Syzuna, thanks for the feature request. We will consider this as we think about adding more transports. You're asking for additional query parameters for the Get Webhook Subscriptions Twitch API endpoint, right?
Can you tell me a little more about how you would use this or specifically how this would help you?