We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The documentation is clear on how to add parameters with Twitter's API v1.1
const parameters = { track: "#bitcoin,#litecoin,#monero", follow: "422297024,873788249839370240", // @OrchardAI, @tylerbuchea locations: "-122.75,36.8,-121.75,37.8", // Bounding box - San Francisco };
const parameters = {
track: "#bitcoin,#litecoin,#monero",
follow: "422297024,873788249839370240", // @OrchardAI, @tylerbuchea
locations: "-122.75,36.8,-121.75,37.8", // Bounding box - San Francisco
};
However, there's no section on how to use the changes made for v2, such as the follow operators (@, from, to, etc) found here:
https://developer.twitter.com/en/docs/twitter-api/tweets/filtered-stream/migrate/standard-to-twitter-api-v2
Could a section be added on the changes made for Twitter's API v2?
More specifically, how would I add the follow operators described above?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
The documentation is clear on how to add parameters with Twitter's API v1.1
const parameters = {
track: "#bitcoin,#litecoin,#monero",
follow: "422297024,873788249839370240", // @OrchardAI, @tylerbuchea
locations: "-122.75,36.8,-121.75,37.8", // Bounding box - San Francisco
};
However, there's no section on how to use the changes made for v2, such as the follow operators (@, from, to, etc) found here:
https://developer.twitter.com/en/docs/twitter-api/tweets/filtered-stream/migrate/standard-to-twitter-api-v2
Could a section be added on the changes made for Twitter's API v2?
More specifically, how would I add the follow operators described above?
The text was updated successfully, but these errors were encountered: