You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As per discussion at https://discord.com/channels/325552783787032576/785942102386540614/1328016079670480946 , the data provided to callbacks handling incoming EventSub notifications via WebSocket does not provide any way to access much of the data from the metadata key of the incoming json message. In particular, the metadata.message_timestamp and metadata.message_id fields are both useful, and not available.
As noted in the discord thread, the similarly named fields under the subscription key are not the same thing -- in particular, the id under that key is the id for the subscription, and the created_at under that key is when the subscription was created.
Most of the other metadata fields (message_type, subscription_type, and subscription_version) are already covered, either because they never change (message_type), or because they're available in the subscription field (subscription_type and subscription_version).
Thanks!
The text was updated successfully, but these errors were encountered:
As per discussion at https://discord.com/channels/325552783787032576/785942102386540614/1328016079670480946 , the data provided to callbacks handling incoming EventSub notifications via WebSocket does not provide any way to access much of the data from the
metadata
key of the incoming json message. In particular, themetadata.message_timestamp
andmetadata.message_id
fields are both useful, and not available.Reference for incoming notification messages: https://dev.twitch.tv/docs/eventsub/websocket-reference/#notification-message
As noted in the discord thread, the similarly named fields under the
subscription
key are not the same thing -- in particular, theid
under that key is the id for the subscription, and thecreated_at
under that key is when the subscription was created.Most of the other metadata fields (
message_type
,subscription_type
, andsubscription_version
) are already covered, either because they never change (message_type
), or because they're available in thesubscription
field (subscription_type
andsubscription_version
).Thanks!
The text was updated successfully, but these errors were encountered: