This has worked for years.
I am receiving tweets through a hosebird-client however it has stopped working I get the following error,
NFO com.twitter.hbc.httpclient.BasicClient - New connection executed: hosebird-client-0, endpoint: /1.1/statuses/sample.json?delimited=length&stall_warnings=true
[hosebird-client-io-thread-0] INFO com.twitter.hbc.httpclient.ClientBase - hosebird-client-0 Establishing a connection
[hosebird-client-io-thread-0] WARN com.twitter.hbc.httpclient.ClientBase - hosebird-client-0 Error connecting w/ status code - 410, reason - Gone
[hosebird-client-io-thread-0] INFO com.twitter.hbc.httpclient.ClientBase - hosebird-client-0 Done processing, preparing to close connection
[hosebird-client-io-thread-0] INFO com.twitter.hbc.httpclient.ClientBase - hosebird-client-0 Establishing a connection
[hosebird-client-io-thread-0] WARN com.twitter.hbc.httpclient.ClientBase - hosebird-client-0 Error connecting w/ status code - 410, reason - Gone
This endpoint was deprecated:
This is a grandfathered account would I have to apply for v2 access?
Not sure what you mean by grandfathered account, but usually any account that has v1.1 Elevated access, also has v2 API access - but you may need to create a “project” and add an app to it to make it work.
system
Closed
#5
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.