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
{
"type": "response",
"code": 400,
"error": {
"errors": [
{
"parameters": {
"until_id": [
"1479477826428358657"
],
"start_time": [
"2022-01-06T20:27Z"
]
},
"message": "Invalid use of 'since_id' or 'until_id' in conjunction with 'start_time' or 'end_time'."
}
],
"title": "Invalid Request",
"detail": "One or more parameters to your request was invalid.",
"type": "https://api.twitter.com/2/problems/invalid-request"
},
...
}
The text was updated successfully, but these errors were encountered:
This is quite a strange choice from Twitter to deny use of until_id and start_time together, as they're not exclusive filters 😅.
I'll look how to paginate without use of since_id/until_id, but the docs seems to not mention clearly pagination tokens for this endpoint. next_token is mentionned in response field list, but is marked as optional.
As a mitigation, you can approximate a start_time using Twitter snowflake IDs (as they are encoded with a timestamp inside):
Get Recent Tweets iterator throws an error when the request contains a date filter.
Error thrown:
The text was updated successfully, but these errors were encountered: