Registering Webhook returns code 200 Forbidden

[notifyio]

Help,
I’m new to the apis and I’m unable to attach the webhook to my app, although I have no trouble querying for the webhooks and calling VerifyCredentials. I consistently see a response of

{"errors":[{"code":200,"message":"Forbidden."}]}

Am I misconfigured in some way? or is there a policy preventing this from working out of the box?
I’m POSting to something like:

https://api.twitter.com/1.1/account_activity/all/env-beta/webhooks.json?url=https%3A//hillcity-staging.notify.io/twitter/gap/hillcity/

For the environment name, I’ve tried many options (env-beta, NotifyDev, :env_name). I’m using the python-twitter module, raw requests, twurl, but with no luck.

A GET on https://api.twitter.com/1.1/account_activity/all/webhooks.json gives me the expected results:

{"environments":[{"environment_name":"NotifyDev","webhooks":[]}]}

App ID: 15812889
App Name: “Notify.io Test Bot”
Owner: @notifyio
Owner ID: 971468619925266432
Dev Environment Label: NotifyDev

Context: My goal is to port one of our chatbots to the platform and send and receive Direct Messages (DMs) and Quick Replies.

Thanks,
/charles thayer
(cc @KyleW)

[happycamper]

Hi @notifyio to troubleshoot, can you try the following:

Make sure you’ve secured your webhook URL, see here for ‘Securing Webhooks’

Go to https://developer.twitter.com/en/account/environments:

• Check the name of your dev environment (note that it is case sensitive).
• Check that the authorization you’re using to make this post call is for the app that you set up on the environment

Go to https://developer.twitter.com/en/apps

• Check that your callback URL is set, this is now required
• Check that your app has Read, Write & Direct Messages permissions (this is required for Account Activity API)

In the request itself:

• Check that your URL is encoded
• Check the name of your environment (this is case sensitive)
• Check that you have webhooks and not webhook

[notifyio]

Thanks!
Setting the callback appeared to resolve it, or at least move the process forward.

From reading some of the javascript code I found that POST-ing with url=https://… in the data works (/account_activity/all/NotifyDev/webhooks.json) although passing it as a query parameter did not (https://goo.gl/36UGqQ)

Super helpful, got unblocked Saturday,
/charles

[happycamper]