Account activity APIのwebhook登録でエラー["Could not authenticate you."]

[yuno_miyako]

問題

https://api.twitter.com/1.1/account_activity/all/prod/webhooks.json?url=[my webhook url]
に対してpostリクエストを送ると"Could not authenticate you."が返ってくる。
AuthorizationはOauth1を使っており、アクセストークンなどは正しい値が入っている(タイムラインの取得や、ダイレクトメッセージの送信を行うことができる)
prodという名前のaccount activity APIのdev environmenも作成済みである。

試したこと

1. bearer tokenでの認証
   こちらで行うと、"Application cannot perform write actions. Contact Twitter Platform Operations through https://help.twitter.com/forms/platform."というエラーが返ってきました。ただし、ダイレクトメッセージまで含めたパーミションはつけており、実際にダイレクトメッセージの送信を行うことができます。

2. この問題に関するトラブルシューティングを読みました。
   https://developer.twitter.com/en/docs/accounts-and-users/subscribe-account-activity/FAQ#troubleshooting
   いずれについても問題をクリアしていますが、いまだに問題が続いています。

[Aurelia]

Hi @yuno_miyako - make sure you’re using the right authentication. Each endpoint has the correct authentication listed in the API documentation. Registering a webhook, for example, requires OAuth 1.0 A.

Additionally, please note that our system noted that your application was being spammy, which is why we revoked your right actions. You need to address this and re-implement your right actions, before you re-register with the webhook again.

[yuno_miyako]

Thank you for your reply!
I’m using Oauth1.0 for registering a webhook so probably right authentification.
I can tweet or send direct messages with same authorization but can’t register a webhook. I couldn’t understand why this happens.

How do I check my application is being regarded as a spam?
I checked my application detail but no warning messages there.
What should I do next?

Thank you in advance.

[yuno_miyako]

I could register webhook url by using account-activity-dashboard(below link)

twitterdev/account-activity-dashboard

I couldn’t understand why I cannot register url by post man but I’m now unstuck so ok.
If there’s anyone being stuck on registering webhook url, try above dashboard.

[LeBraat]

I’d guess that you are not generating your oauth nonce , oauth_signature , and oauth_timestamp properly. POSTMAN has been known to have issues with this.

We suggest that you use an oAuth library, Insomnia, Twurl, or read through this document closely to resolve this issue.

[system]

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