Twitter webhook registration

[vinodsaini]

@momentring Thanks for the reply.

I tried above url as well but issue is same, please check screenshot of what I am doing

Let me know if there is anything wrong in my code

[momentring]

@vinodsaini
“Authorization: Bearer …” is for application-only authentication.
Since “Authorization: OAuth …” header is generated by the library, you don’t need to set it explicitly.

[vinodsaini]

Still getting Forbidden error after change code

[momentring]

$ curl --request GET --url 'https://api.twitter.com/1.1/account_activity/all/env-beta/webhooks.json' --header 'Authorization: Bearer YOUR_BEARER_TOKEN'

Expected response is “[]” (empty json array).
If you get some error, your app probably isn’t permitted.
If receive no error, parameters of registration request will be invalid.

[vinodsaini]

Its showing same error

{"errors":[{"code":200,"message":"Forbidden."}]

Even when I am accessing url https://api.twitter.com/1.1/account_activity/all/env-beta/webhooks.json its showing page not found error

[momentring]

I made some trial.

$ curl --request GET --url 'https://api.twitter.com/1.1/account_activity/all/env-beta/webhooks.json' --header 'Authorization: Bearer VALID_TOKEN'
[]

$ curl --request GET --url 'https://api.twitter.com/1.1/account_activity/all/env-beta/webhooks.json' --header 'Authorization: Bearer INVALID_TOKEN'
{"errors":[{"code":89,"message":"Invalid or expired token."}]}

$ curl --request GET --url 'https://api.twitter.com/1.1/account_activity/all/env-beta/webhooks.json' --header 'Authorization: Basic VALID_TOKEN'
{"errors":[{"code":215,"message":"Bad Authentication data."}]}

$ curl --request GET --url 'https://api.twitter.com/1.1/account_activity/env-beta/webhooks.json' --header 'Authorization: Bearer VALID_TOKEN'
{"errors":[{"message":"Sorry, that page does not exist","code":34}]}

$ curl --request GET --url 'https://api.twitter.com/1.1/account_activity/all/:env-beta/webhooks.json' --header 'Authorization: Bearer VALID_TOKEN'
{"errors":[{"code":200,"message":"Forbidden."}]}

My only situation that forbidden error occurs is the last one.

By the way, how is any other endpoint?

$ curl --request GET --url "https://api.twitter.com/1.1/statuses/user_timeline.json?screen_name=TwitterDev&count=1" --header 'Authorization: Bearer VALID_TOKEN'
[{"created_at":"Tue Apr 17 20:22:20 +0000 2018","id":986339096762241026, ...

If this request is accepted, the issue may be AAAPI specific.

[vinodsaini]

I tried all these;

$ curl --request GET --url ‘https://api.twitter.com/1.1/account_activity/all/env-beta/webhooks.json’ --header ‘Authorization: Bearer VALID_TOKEN’

But its showing Forbidden error

I am very tired with these apis, didn’t find any solution yet, almost wasting 1 month

Can somebody help over this.

Again describing my problem—

I am registering webhook url to access account activity in real time
For example- if someone tweets on a particular hashtag then I need that tweet on my server in real time.

Thanks in advanced.

[andypiper]

Hi there @vinodsaini - first of all, I can certainly see how frustrating this is for you, and appreciate your persistence in trying to use the Account Actvity API. You’ve tried seemingly everything and are still hitting an error, and that sucks for sure. We are sorry you’ve had this experience. As a reminder, this API is brand new and in a beta access period and some issues do still remain.

I’ve done some checking and I believe that, due to a technical limitation of the beta phase of the API, we are currently unable to help you. It appears that you may have made some changes to your application identity in between beta access being granted and your current attempts to get this working (did you delete and recreate it?), and at the present time we cannot resolve this for you.

When the API becomes generally available this will be something that we will have tools that can help to resolve, but I wanted to let you know that we narrowed down what is happening here, to apologise directly for the frustration, and to set your expectation that we cannot fix this until later. Please do not spend more effort on it for now.

[vinodsaini]

@andypiper Thanks for the reply,

It appears that you may have made some changes to your application identity in between beta access being granted and your current attempts to get this working (did you delete and recreate it?), and at the present time we cannot resolve this for you.

What did you mean about this?
This should not be a problem, these things are not mentions anywhere in the document.

In the last, let me know what should I do to register webhook?
Do I need to apply for Enterprise Access if there is something which help me to register webhook?

Also correct me if I am wrong and what I am trying to do is

If someone tweets on a particular hashtag then I need that tweet on my server in real time. I can get these through normal apis but these are 30 seconds delay, I need tweets in real time. Thats why I am using Account Activity API and trying to register webhook. Let me know if there is any other way to get tweet in real time.

[andypiper]

Until the beta period is completed, we will be unable to help you with the Account Activity API. It appears that you deleted and recreated an application where we had already granted Account Activity API access, and unfortunately that prevents us from re-adding the access due to a limitation in the beta. When the API is generally available we should be able to assist you.

As an alternative to using the Account Activity API you may try looking into the standard streaming statuses/filter endpoint and filtering on the hashtag you’re looking for.

[vinodsaini]

standard streaming statuses/filter endpoint are for streaming, I need to show tweets on a web page of a hashtag. How can streaming apis would help over this.

Also cab I create a new account to access Account Activity API and apply for beta access if my current app keys creating problem.

[andypiper]

Please do not apply for access from another account as we are only able to provision access for one account and application during the beta. We are very sorry about this limitation.

I’m not sure that the Account Activity API will be an ideal solution to what you’re trying to build, as it will only provide Tweets posted by the authenticated user (as well as all other supported event types for that user account). I guess you would then have to look at each Tweet object and check if it contained the hashtag you want to track before choosing to display it. The streaming API would let you filter and only receive Tweets containing the hashtag, from all users. Anyway, I’m not exactly sure of the architecture of your app, so I’ll leave you to decide which is the most effective way of working!

[vinodsaini]

Ok…

Are these streaming API free to use and how many tweets I can get from these.

Also, Do I need to hit twitter api in every second to get tweet or is there any other way to get tweet in real time?
And do I need to apply for any access to run these apis.

[vinodsaini]

@andypiper

When I search for getting real-time tweet apis, I also found below:

The major drawback of the Streaming API is that Twitter’s Steaming API provides only a sample of tweets that are occurring. The actual percentage of total tweets users receive with Twitter’s Streaming API varies heavily based on the criteria users request and the current traffic.

Studies have estimated that using Twitter’s Streaming API users can expect to receive anywhere from 1% of the tweets to over 40% of tweets in near real-time.

The reason that you do not receive all of the tweets from the Twitter Streaming API is simply because Twitter doesn’t have the current infrastructure to support it, nor do they don’t want to support it; hence, the Twitter Firehose.

Let me know if its correct and What are the pricing of Firehose apis.

Is Firehose apis different from Decahose stream?

[andypiper]

Unless you are looking for a very high volume hashtag, I find it incredibly unlikely that this will be an issue for you. You’re capped at 1% of the firehose, but if all of the Tweets being sent in a single instant containing your hashtag will take you beyond that volume (usually somewhere around 50-60 Tweets PER SECOND) then you’ll see all of the Tweets you want.

The statuses/filter endpoint is free to use and does not require polling, but does require your application to hold an open socket to receive the Tweet data. There are lots of examples of how to do this using PHP (here’s just one project that demonstrates the technique, you can easily search for others).

[vinodsaini]

@andypiper Thanks!!
I hope you are understanding that what I want and how would I use it. Again explaining my requirements;

1. I am creating a webpage on which tweet of a perticuler hastags will show.
2. If someone tweet on hashtag like ‘ipl20’, I will grab that in real-time and show on that web page.
3. I need all those tweets in real-time. normal search apis send data after 30 seconds.

Is statuses/filter api send all tweets in real-time, and how i would send and on which url?
And how I create open socket to receive Tweet Data?

[andypiper]

I think the example project that I linked to above is probably a good starting point. The API documentation has information on the parameters required.

[bobber205]

@vinodsaini What changes did you make to your application that caused the issue Andy is talking about? Curious what happened so I can avoid.

[andypiper]

Firstly once the API is generally available / out of beta this should not be a problem; secondly it is not clear (to me), but it could have been an app deletion and recreation such that the whitelisting could not be sustained due to current technical limitations. Simply changing description or permissions on apps.twitter.com should not have had any effect.

[bobber205]

Does changing the name of the handle that owns the app have any effect?