Additional notes

https://gist.github.com/BarryCarlyon/a72f2d2f76c738148383873b8853658d

Descirbes what I would like to send and what I'd like as a reply

So the first message is tested at level 3 and the second at "channel set"

Categories on which thing's it was blocked for would be useful, but not immediately so for my described use case, but would be useful for other use cases.

A lot of the use cases here center on third party things such as extensions or overlays, where a message from $source would be tested, and the category/reason why would be useful, in order for a moderator to decide to allow it or not, since it's not a chat message the third party dashboard would need the unblock check.

Please include tenure data in the payload (current streak, total months)

This is a bug rather than a feature request. And I believe it affected all raids and might be fixed. See https://github.com/twitchdev/issues/issues/246

Usage scenarios

If I try to (re)create a subscription for say streams.online as it doesn't seem to be working.
And I get a 409
I then have to paginate "Get EventSub Subscriptions" to find the conflicting subscription, to check it's status.
And assuming that all 10k of my subscriptions are all streams.online I can't use the type filter.

Sure I could make 5 calls to different status filters.

But it's still more than one simple call to "just delete the subscription by the confliciting ID"

This Idea would be great, as then you don't have to make 10 rewards that are the same price, or deal with "free text" input when automating via the API