Activity API beta access not working


#1

A few months ago, I applied for activity API beta access for one of my apps, and developed an app, and that’s all working fine. I tried to apply for a second app, and I got back an email saying it was approved, but it doesn’t seem to work at all.

We have a production environment and a “demo” environment for demoing products to our customers, so I created a second “demo” twitter app, and went to apply for API beta access again. The process is a bit different now than it used to be, but I went through it, I mentioned I already had access on my one app, but I was looking for it for this other app.

Twitter replied and told me “We have provisioned access to the Account Activity API beta for the single client application you noted in your application for access.”

But… they don’t seem to have. With my “old” app, if I send a request to account_activity/webhooks, I get back a list of provisioned webhooks. With my “new” app, I get back:

[ { code: 32, message: 'Could not authenticate you.' } ]

I tried replying to the email from Twitter, but I didn’t even get back an automated reply. I tried to go through the “sign up for beta access” wizard again, except when I click on the link it now redirects to https://developer.twitter.com/en/dashboard. How do I get in contact with Twitter to get them to fix this?


#2

Hi there,

Sorry to hear you’re having issues. In order for us to help troubleshoot, can you please provide the following?

  1. The Twitter account (@handle) that was approved for access
  2. The endpoints that you are making requests to (e.g., DM endpoints)

Once we have the requested info, we can better assist.

-JD


#3

The account is this one @BenbriaDev.

I just tried this again. With my first app (Benbria-Loop) if I send a GET to https://api.twitter.com/1.1/account_activity/webhooks.json, I get back:

[ { id: 'XXX',
    url: 'YYY',
    valid: true,
    created_timestamp: '2018-01-30 04:12:00 +0000' } ]

With my second app (Benbria-Loop-Demo) if I try the same, I get back a “401”, and the message body is:

{"errors":[{"code":32,"message":"Could not authenticate you."}]}

#5

Ah got it. Sorry for the confusion here, but the beta period is limited to one app per account – so it will not support the desired setup of two environments. Additionally, it is limited to a max of 35 subscriptions.

If you do need more access, you can always apply for the enterprise access level here.


#6