botman / driver-twitter

BotMan Twitter Driver
MIT License
7 stars 6 forks source link

Callback #3

Closed freescout-helpdesk closed 3 years ago

freescout-helpdesk commented 3 years ago

Thanks for the driver. Where can the callback listening for incoming direct messages be configured?

freescout-helpdesk commented 3 years ago

https://github.com/botman/driver-twitter/blob/master/src/Console/Commands/TwitterRegisterCommand.php

freescout-helpdesk commented 3 years ago

account_activity/webhooks request returns [{"code":32,"message":"Could not authenticate you."}]

Does access to webhooks require a Twitter Enterprise level access? https://developer.twitter.com/en/docs/twitter-api/enterprise/account-activity-api/guides/getting-started-with-webhooks

freescout-helpdesk commented 3 years ago

All the keys are correct as "statuses/show/:id" request works fine.

freescout-helpdesk commented 3 years ago

A per instruction https://developer.twitter.com/en/docs/twitter-api/premium/account-activity-api/guides/getting-started-with-webhooks created a Dev Environment labeled "prod".

$webhooks = $connection->get('account_activity/all/prod/webhooks')
freescout-helpdesk commented 3 years ago

Here https://developer.twitter.com/en/docs/twitter-api/premium/account-activity-api/guides/getting-started-with-webhooks there is a note:

When registering your webhook URL, your web app must authenticate with its consumer token and secret and the app owner's user access token and secret.

Where "app owner's user access token and secret" can be found?

freescout-helpdesk commented 3 years ago

Adding all/prod to all requests did the trick.