I am trying to prototype Twitter webhooks using account activity APIs. I am using postman’s Twitter collection, and all API calls using OAuth are failing with 404 and the “Nothing to see here” message.

However, the call to list the webhooks - it uses a bearer token - is always successful.

I wonder if it’s a recurrence of the issue reported here: twitter api oauth/authenticate shows nothing to see here

Just to clarify, I am using the following values for parameters:

  • consumer_key/oauth_consumer_key = Twitter App’s API key
  • Consumer Secret = Twitter App’s API secret
  • Access Token/oauth_token = TwitterApp’s access token
  • Token Secret = Twitter App’s access secret

In case of adding subscriptions, I am using the Twitter user account’s access token and the token secret that I received after linking the accounts to my app.

Somehow, the call to create a webhook was successful once a few days back, and I am still receiving the CRC check on my app. However, now I can’t add subscriptions to it or even delete it.

Any pointers to debug would greatly help!

Does it work if you use this? GitHub - twitterdev/account-activity-dashboard: Sample web app and helper scripts to get started with the premium Account Activity API or GitHub - twitterdev/autohook: Automatically setup and serve webhooks for the Twitter Account Activity API ?

1 Like

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