Unable to register webhook. Getting 'Bad Authentication Data code: 215'

[TaylorKrusen]

I’m having some authentication issues with registering a webhook in node.js. My account is approved for using the Account Activity API.

I’ve setup my node scripts and am porting localhost through ngrok. Using Twitter’s Account Activity Dashboard, I can create, validate, and delete a webhook no problem. However, I want to create the webhook programmatically using curl.

I’m using the exact curl command from the ‘Create new webhook’ section of the docs, but with my Consumer API Key and Access Token. Every time it throws a ‘code: 215 Bad Authentication Data’.

I also setup a POST request on postman using the OAuth 1.0 settings with appropriate variables and URL. This still throws an authentication error:

{
    "errors": [
        {
            "code": 32,
            "message": "Could not authenticate you."
        }
    ]
}

This all points to an issue with the information I’m copying over from my Twitter App’s ‘Keys and Permissions’. However, those exact same strings work perfectly in the Account Activity Dashboard app.

I’m not sure where to go from here. Any suggestions on next steps?

[TaylorKrusen]

I forgot to mention that both of these methods of registering webhooks worked for me ~ 3 weeks ago.

[LeBraat]

Hey @TaylorKrusen,

Sorry to hear about the troubles. Can you please provide us your request to help us investigate?

Are you using your consumer and access tokens in your request?

We have some details related to Code 32 in our Error Troubleshooting Guide.

[TaylorKrusen]

Sure, here is the curl command I am trying to use (abstracted out the sensitive info).

$ curl --request POST 
--url 'https://api.twitter.com/1.1/account_activity/all/serverlessDemo100/webhooks.json?url=https://b57c6e2d.ngrok.io/webhook-demo/twitter' 
--header 'authorization: OAuth oauth_consumer_key=“<MY_CONSUMER_KEY>“, oauth_nonce="GENERATED", oauth_signature="GENERATED", oauth_signature_method="HMAC-SHA1", oauth_timestamp="GENERATED", oauth_token=“<MY_ACCESS_TOKEN>”, oauth_version="1.0"'

The consumer key and access token are the same ones I am able to use successfully in the Account Activity Dashboard.

Thanks for the link, but I’ve already double-checked all of those suggestions.

[LeBraat]

Have you tried to HTML encode your webhook URL in your request?

[TaylorKrusen]

Yes, I’ve tried it with and without HTML encoding the webhook URL. It throws the ‘bad authentication data’ error in both cases.

[LeBraat]

The next check would be your generated tokens. Are you sure they are generating properly?

It sounds like you were getting there with Postman, so maybe Postman was handling your generated tokens properly. Have you, by chance, tried this in Insomnia? One of my colleagues had issues with Postman but was able to get through Insomnia.

[TaylorKrusen]

I’m confident the tokens are generating properly because they work to register the webhook through the Account Activity Dashboard app. I’ve regenerated them and have the same behavior with new ones.

I’ve been sending the request above with curl commands from terminal. I’d really like to get my requests working from there because it’s easiest to demonstrate.

I did successfully use Postman to register webhooks ~3 weeks ago and saved the methods that I used. However, now when I use them they throw that authentication error. Even with new consumer key / access tokens.

[LeBraat]

I think there might be a miscommunication about the generated tokens.

I was curious to see how you are handling the oauth_nonce, oauth_signature, and oauth_timestamp, all of which you shouldn’t have to worry about with the Account Activity Dashboard.

I did successfully use Postman to register webhooks ~3 weeks ago and saved the methods that I used. However, now when I use them they throw that authentication error. Even with new consumer key / access tokens.

Quick question on this statement:

What do you mean by ‘when I use them’? Did they become invalidated and are you trying to reestablish the connection and receive events through that connection?

Are these webhooks still registered? (you can check with the GET :env_name/all/webhooks endpoint.

If they are still registered, are you using the CRC endpoint to revalidate these webhooks?

[mcukkemane]

I too have same problem as mentioned in the beginning of this thread. Basically, i am just using the Activity API dashboard example from github. It used work OK until yesterday noon (India time) and then it stopped and throwing out the Bad Authentication Error (Error code: 215). Any way to fix this?

[LeBraat]

@mcukkemane - Were you making a request to the POST :env_name/webhooks endpoint when you received this error?

[system]

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.