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
Upon examining the cheermotes retrieved via the Get Cheermote endpoint and filtering for channel custom cheermotes, it's noticed that the last_updated field consistently displays 0001-01-01T00:00:00Z. This observation has been confirmed across three different broadcasters, all of whom possess custom cheermotes.
How to Reproduce
Initiate a GET request to the cheeremotes endpoint, including the broadcaster_id query parameter to retrieve broadcaster-specific cheermotes.
Examine the last_updated field in the response.
Expected Behavior
The anticipated behavior is for the endpoint to furnish the most recent update timestamp or creation date for the cheermote. For instance, global cheermotes typically showcase a creation date akin to 2018-05-22T00:06:05Z.
Screenshots
Additional Context or Questions
N/A
The text was updated successfully, but these errors were encountered:
Brief Description
Upon examining the cheermotes retrieved via the Get Cheermote endpoint and filtering for
channel custom
cheermotes, it's noticed that thelast_updated
field consistently displays0001-01-01T00:00:00Z
. This observation has been confirmed across three different broadcasters, all of whom possess custom cheermotes.How to Reproduce
GET
request to the cheeremotes endpoint, including thebroadcaster_id
query parameter to retrieve broadcaster-specific cheermotes.last_updated
field in the response.Expected Behavior
The anticipated behavior is for the endpoint to furnish the most recent update timestamp or creation date for the cheermote. For instance, global cheermotes typically showcase a creation date akin to
2018-05-22T00:06:05Z
.Screenshots
Additional Context or Questions
N/A
The text was updated successfully, but these errors were encountered: