1)I did the DM creation with my API_KEY but I could do it. https://developer.twitter.com/en/docs/direct-messages/sending-and-receiving/api-reference/new-event Probably my API_KEY is not frozen.
I created a webhook to use account activity. I registered the URL and received an OK request. https://developer.twitter.com/en/docs/accounts-and-users/subscribe-account-activity/api-reference/aaa-premium#post-account-activity-all-env-name-webhooks (I was able to confirm that the token has reached my server by looking at the log)
But event does not come to the registered URL. I was able to confirm by looking at the log that the event had come before. But now the event has not arrived at my server. (I checked the log and confirmed that it did not arrive)
I guess from the reasons (1) to (3) that probably “account activity” is frozen. My server uses “heroku”. But there is no trace of access restricted.
Have you subscribed any users to your app?
If so, have you received any events from those users that are subscribed to that app?
LeBraat, Thanks for the advice. I was able to register webhook, but I did not register subscriptions.
My problem was resolved by running [POST account_activity / all /: env_name / subscriptions] written in [https://developer.twitter.com/en/docs/accounts-and-users/subscribe-account-activity/api-reference/aaa-premium]
Thanks for the update. Glad to hear that the product is working for you! @KoukokuProject
