node-red / node-red/node-red-nodes
Twitter v2.0 API not supported (returns 403)
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.1k
- Forks
- 612
- Avg merge
- 13h 57m
- Merged PRs (30d)
- 3
Description
Which node are you reporting an issue on?
What are the steps to reproduce?
- Create a new instance of Node-RED
- Add the Twitter node
- Add an App/Project through the Twitter Developer Portal
What happens?
- Receive a
"stream error: http (403)"error from the Twitter API
This is because Twitter have restricted access for "Essential" developer accounts (the default account provided when signing up for a Twitter developer account) to using the v2 API only. In order to use the v1.1 API, developers must have an "Elevated" account.
What do you expect to happen?
- Should be able to utilise the Twitter nodes, without the requirement to upgrade to an "Elevated" Twitter dev account.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting the Twitter node and its API integration, then reproduce the 403 using an Essential developer account as described. Compare the node's current API usage with Twitter's v2 access requirements. Done means the Twitter nodes work for Essential accounts without the reported 403.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100