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
If there are no contributors for a Tweet, then there will be an
empty or "contributors" : {}. This field will only be populated if
the user has contributors enabled on his or her account — this is
a beta feature that is not yet generally available to all.
This object contains an array of user IDs for users who have
contributed to this status (an example of a status that has been
contributed to is this one). In practice, there is usually only
one ID in this array. The JSON renders as such
"contributors":[8285392].
I tried to get the raw JSON output for the request I'm making, but it's for the retweets_of_me timeline so calling the API "manually" using the API tool that Twitter provides isn't possible.
This feature doesn't seem completely finished yet on Twitter's end, to the point that there are two different API specifications for how the field should look or what it does, and different endpoints seem to behave differently. Does it make sense to remove parsing for this attribute for now, until it's generally available?
The text was updated successfully, but these errors were encountered:
I just got a failure to parse, and after making a change as described in #21, I was able to produce the error message:
Trying to find information about this field, I came upon the document Overview: Tweets, which provides the following example:
I also found GET status/show/:id, which says:
I tried to get the raw JSON output for the request I'm making, but it's for the retweets_of_me timeline so calling the API "manually" using the API tool that Twitter provides isn't possible.
This feature doesn't seem completely finished yet on Twitter's end, to the point that there are two different API specifications for how the field should look or what it does, and different endpoints seem to behave differently. Does it make sense to remove parsing for this attribute for now, until it's generally available?
The text was updated successfully, but these errors were encountered: