#1

When I use date params, I always have this error. Without it everything is working well.

image
image1402×334 79.5 KB

Start_time with Timelines endpoint (node.js)
#2

This happens a lot with Postman. I wouldn’t use it for testing the API because it’s buggy with oauth (i remember vaguely it fails to properly url encode pameter values when building the signature base string or something like that). I’d use twurl instead GitHub - twitter/twurl: OAuth-enabled curl for the Twitter API

#3

I also had the same result in my integration tests in code. Do you manage to use it on your side ?

#4

Oh, now that you mention it, yes - it doesn’t seem to work. I also get 503 error.

i tried

twurl "/2/users/495430242/tweets?max_results=10&start_time=2020-12-16T20:21:21.000Z&end_time=2020-12-26T20:21:21.000Z"

for reference.

It seems to work if i use a different parameter like since_id & until_id. So it’s definitely something weird on twitter’s side with that parameter.

1 Like
#5

Yes, I tried to contact @suhemparack last week on DM but didn’t have any answer until now…

1 Like
#6

Thanks for reaching out and reporting this issue. This is a known issue with this endpoint that we are aware of and we may be deploying a fix shortly (likely after the new year). I’ll keep you updated if I hear anything further.

Thanks again!

1 Like
#7

It looks now working fine :slight_smile: Thanks !

1 Like
#8

The latest Postman release has resolved the encoding bug and should now generate the correct authorization signatures.

3 Likes