#1

curl --compressed -v -uvaibhavmishra@ninja.com
“https://gnip-stream.twitter.com/stream/powertrack/accounts/ninja/publishers/twitter/king-tgx.json”

when i am trying to get the response with proper credentials getting

{
“title”: “Unauthorized”,
“type”: “about:blank”,
“status”: 401,
“detail”: “Unauthorized”

checked with postman also facing the same issue

1 Like
#2

Hi there,
I am not sure what you mean by v2? your URL appears to be against the Powertrack enterprise API

The correct URL for v2 is this:

Could this be the issue?

1 Like
#3

Hi
Meaning of V2 is version 2 and we are using version 2 Enterprises Edition provided by Gnip
https://console.gnip.com/ and you mentioned rules URL i am talking about stream , please help .

#4

Oh I see, sorry! I was confused PowerTrack 2 is different from API V2

I highly recommend you contact your account manager, they will connect you with someone from the managed support team, that’s probably the fastest route to resolve issues for Enterprise customers.
Otherwise I don’t know how soon someone from the twitter staff will see this. Perhaps @suhemparack can help.

If I had to guess, the product has been removed from your Gnip subscription. When you login to your Gnip console, do you see PowerTrack 2.0 (PowerTrack) in your list of products?

1 Like
#5

yes we are getting power track api in our list of product

#6

OK then, sorry I am out of ideas

Drop an email to your account manager and hopefully they will connect you with managed support soon

#7

Sorry to semi-hijack thread, but we’re a GNIP customer experiencing similar issue with 401’s on the GNIP compliance stream, with credentials that work everywhere else…

We have had a longtime account manager, but their email is now returning a rejection that they no longer exist… could you please advise of the support channel for GNIP customers? at a loss

#8

I am really sorry, I am a developer like you so I don’t really know how to contact them once you lose contact with your account manager.
Hopefully one of the twitter staff will see this and help out.

I would also try this form:

And write a note that you already have access but you no longer know who your account manager is
Hopefully this helps

1 Like
#9

I had the same issue.

Screenshot 2565-12-28 at 14.50.14
Screenshot 2565-12-28 at 14.50.141074×240 156 KB

#11

do you know how to solve this

#12

thanks mate

#13

looking for that

#14

Contact Email: dev-support@twitter.com

1 Like
#15

I contacted Twitter dev-support team. He mentioned that it might happen due to DNS cache. Twitter has shut down one of its DC and the API traffic from APAC region was still rerouted to the old DC.

In my case, I flushed my DNS cache on my server and it works, I don’t have any authentication issue anymore. But I still failed to connect from my laptop though.

2 Likes
#16

restart your laptop and try once , in my case i am not facing this issue

1 Like
#17

hi all
please check issue is solved or not for your side

#18

hi
if we will use replay api as we missed the data in this case we have to pay something or not

#19

hi
if we will use replay api to get data from 25 to till now as we missed the data in this case we have to pay something or not as in historical search api we have to pay

#20

hi @suhemparack if we will use replay api to get data from 25 to till now as we missed the data in this case we have to pay something or not as in historical search api we have to pay

#21

You can use 30-Day Search API or Full Archive Search API from 25th to 29th December and then use RealTime PowerTrack API.

These are included in your package.

2 Likes