You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Sep 15, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Sep 15, 2026. It is now read-only.
async function createNewTwitterClient (subdomain, extension, response, twitterAppConfig, version) {
const twitter = require("twitter-lite");
return new twitter({
subdomain,
consumer_key: twitterAppConfig.consumerKey, // from Twitter.
consumer_secret: twitterAppConfig.consumerSecret,
extension, // true is the default (this must be set to false for v2 endpoints),
access_token_key: twitterAppConfig.accessTokenKey, // from your User (oauth_token)
access_token_secret: twitterAppConfig.accessTokenSecret, // from your User (oauth_token_secret)
bearer_token: response ? response?.access_token : null,
version
});
}
const twitterApiClient = await createNewTwitterClient('api', false, null, twitterAppConfig,'2');
twitterApiClient.post('tweets', { text: 'hello world' }).then(tweet => {
// do something
}).catch();
So, I removed the bearer token from the twitterAppConfig
Maybe, you should be allowed to send the bearer token, along with the access token, without losing the ability to POST. Currently, your code chooses which type of authentication to use, based on whether the bearer token is present. It might be better to choose which type of authentication to use, based on whether the bearer token is present and whether the access token is not present?
Chiming in here to say that I'm also receiving the same content-type error for the /tweets endpoint.
try{constclient=newTwitter({subdomain: "api",// With or without this parameter, the error persistsversion: "2",extension: false,
consumer_key,
consumer_secret,
access_token_key,
access_token_secret,});consttweet=awaitclient.post("tweets",{text: "Hello, World!",});res.send({ tweet });}catch(error){res.send({ error });}
Reponds with:
{
"error": {
"_headers": {},
"errors": [
{
"message": "Requests with bodies must have content-type of application/json."
}
],
"title": "Invalid Request",
"detail": "One or more parameters to your request was invalid.",
"type": "https://api.twitter.com/2/problems/invalid-request"
}
}
Activity
charlesr1971 commentedon Dec 8, 2021
I have found the fix:
Oh. And I had to update my code as well:
Here is the code
So, I removed the bearer token from the twitterAppConfig
Maybe, you should be allowed to send the bearer token, along with the access token, without losing the ability to POST. Currently, your code chooses which type of authentication to use, based on whether the bearer token is present. It might be better to choose which type of authentication to use, based on whether the bearer token is present and whether the access token is not present?
[-]OAuth 2 error for POST /2/tweets[/-][+]OAuth 2 error for POST /2/tweets FIXED[/+]ZainUrRehmanKhan commentedon Feb 28, 2022
Response:
any fix? @charlesr1971
charlesr1971 commentedon Feb 28, 2022
Try adding:
subdomain: 'api'
To the arguments of:
new Twitter({
subdomain: 'api'
...
})
Argument object...
ZainUrRehmanKhan commentedon Feb 28, 2022
Still same response.
charlesr1971 commentedon Feb 28, 2022
Please try using this exact code:
`async function createNewTwitterClient (subdomain, extension, response, twitterAppConfig, version) {
const twitter = require("twitter-lite");
return new twitter({
subdomain,
consumer_key: twitterAppConfig.consumerKey,
consumer_secret: twitterAppConfig.consumerSecret,
extension,
access_token_key: twitterAppConfig.accessTokenKey,
access_token_secret: twitterAppConfig.accessTokenSecret,
bearer_token: response ? response?.access_token : null,
version
});
}
const apiClient = await createNewTwitterClient('api', false, null, twitterAppConfig,'2');
const apiResponse = await apiClient.getBearerToken();
const twitterApiClient = await createNewTwitterClient('api', false, apiResponse, twitterAppConfig,'2');
twitterApiClient.post('tweets', { text: 'hello world' }).then(tweet => {
}).catch();`
This works for me!
My twitterAppConfig is:
const twitterAppConfig = { consumerKey: APP_CONFIG.CONSUMER_KEY1, consumerSecret: APP_CONFIG.CONSUMER_SECRET1, accessTokenKey: APP_CONFIG.ACCESS_TOKEN1, accessTokenSecret: APP_CONFIG.ACCESS_TOKEN_SECRET1 };charlesr1971 commentedon Feb 28, 2022
Also:
#187
**This PR has not been merged yet. **
I had to change the code inside the Twitter-Lite for
/tweetsv2 to work!charlesr1971 commentedon Feb 28, 2022
God, this MarkDown Editor is terrible.
You would think GitHub could sort this out? 😩
charlesr1971 commentedon Feb 28, 2022
charlesr1971@d5e9ef1
ZainUrRehmanKhan commentedon Feb 28, 2022
I'm still facing the same issue, I tried the exact same code you mentioned above.
Is there any workaround or other package which I can use for now?
ZainUrRehmanKhan commentedon Feb 28, 2022
why there is no content-type application/json?
charlesr1971 commentedon Feb 28, 2022
Yes. You need to use the twitter-lite version in my PR request above:
#187
Unfortunately, the owners of the twitter-lite repo, are not merging PR requests at the moment.
But, you can clone my repository and use that:
https://github.com/charlesr1971/twitter-lite/tree/%40charlesr1971
charlesr1971 commentedon Feb 28, 2022
Here is the commit:
charlesr1971@d5e9ef1
ZainUrRehmanKhan commentedon Feb 28, 2022
I tried using your repo for the package but It's also not working.
charlesr1971 commentedon Feb 28, 2022
All I know is that the current Twitter-lite V2
/tweetsendpoint does NOT work.My PR code updates, work with me.
I must say your content type error message, is a little strange.
McCambley commentedon Sep 19, 2022
Chiming in here to say that I'm also receiving the same content-type error for the
/tweetsendpoint.Reponds with:
{ "error": { "_headers": {}, "errors": [ { "message": "Requests with bodies must have content-type of application/json." } ], "title": "Invalid Request", "detail": "One or more parameters to your request was invalid.", "type": "https://api.twitter.com/2/problems/invalid-request" } }@charlesr1971 I will take a look at your PR!
ericdjavid commentedon Dec 1, 2024
I'm having the same issue, it has not been fixed yet?