Since March, Twitter is starting to disable API 1.0.
I want to share and remind the masters, those who use the Twitter API in their products. Both versions of the API are currently available, but API 1.0 in the documentation is already marked as “deprecated” and will be disabled from March 2013.
Now you can not perform a search without authentication; all requests must be made by account / token.
All speed limits apply in the context of a 15 minute window. Each requested method has its limitations. Restrictions are imposed on the number of connections per minute, the usual values are 15 and 180. For example, the “search” method is limited to 180 connections per 15 minutes.
Only JSON will be available as a transport protocol, and XML is no longer supported.
')
Twitter informs you about your current speed and limitations through HTTP X-Rate-Limit headers.
Restrictions on the speed of reconnection. Too stubborn clients will be banned by IP - for REST API and Streaming API their limitations.
For continuous collection, it is recommended to use the Streaming API, which allows you to receive tweets on a specific topic in streaming mode in one connection.
Check your client for API 1.1 compatibility, since the interaction protocol is different from API 1.0.
If you lack the speed of collecting tweets, you can use the services of intermediaries - paid series recommended by Twitter.
Useful links:
dev.twitter.com/docs/api/1.1
dev.twitter.com/docs/faq
dev.twitter.com/docs/rate-limiting-faq
API 1.1 Features
Now you can not perform a search without authentication; all requests must be made by account / token.
All speed limits apply in the context of a 15 minute window. Each requested method has its limitations. Restrictions are imposed on the number of connections per minute, the usual values are 15 and 180. For example, the “search” method is limited to 180 connections per 15 minutes.
Only JSON will be available as a transport protocol, and XML is no longer supported.
')
Twitter informs you about your current speed and limitations through HTTP X-Rate-Limit headers.
Restrictions on the speed of reconnection. Too stubborn clients will be banned by IP - for REST API and Streaming API their limitations.
For continuous collection, it is recommended to use the Streaming API, which allows you to receive tweets on a specific topic in streaming mode in one connection.
Check your client for API 1.1 compatibility, since the interaction protocol is different from API 1.0.
If you lack the speed of collecting tweets, you can use the services of intermediaries - paid series recommended by Twitter.
Useful links:
dev.twitter.com/docs/api/1.1
dev.twitter.com/docs/faq
dev.twitter.com/docs/rate-limiting-faq
Source: https://habr.com/ru/post/170253/
All Articles