Account Activity API - All Activities (beta) whitelist failure

[Vinodreddi999]

@sao_ademola i’m not receiving CRC request call to my application on registering the webhook url with POSTMAN.

i have tested my method with https://tools.pingdom.com, it returning response code as 200 OK and sha256=jaWVpObgHMpqrEcbcGhDHm0zTlDGWPh9VWhpA5+0/hw=

https://XXXXXXX:10352/api/social/socialfeed/twitter/onmessage?user=dummyUser&organization=dummyOrg&crc_token=123

[Vinodreddi999]

Any help would be really appreciated…i’m waiting on this and not sure if i need to provide any more information to get it cleared.

appid: 12571850

[KyleW]

There are too many things in what you posted for me to diagnose well.

Have you tried registering the webhook without the url parameters to start? (I should know this, but recall off the top of my head right now) I am not sure if we support URL parameters in the URL like you are using them.

[Vinodreddi999]

@KyleW Thanks for the reply.

i have tried registering the url without parameters[https://XXXX.com:10352/api/social/socialfeed/twitter/onmessage] still i don’t see the call coming to my CRC verification method.
other issue i notice is even if my application is not running also, same exception is thrown

{
“errors”: [
{
“code”: 214,
“message”: “Non-200 response code during CRC GET request (i.e. 404, 500, etc).”
}
]
}
is it anything to do with port 10352? facebook webhook integration is working fine in my application.

using POSTMAN:
post activity url : https://api.twitter.com/1.1/account_activity/all/env-beta/webhooks.json
Content-Type: application/x-www-form-urlencoded
Filled in all Authorization information with type OAuth 1.0

[happycamper]

I’m getting this error, can you check your URL?

High latency on CRC GET request. Your webhook should respond in less than 1 second.

[Vinodreddi999]

@happycamper my application was not runnning, i don’t know that i should keep my application up and running for you to looking into it. i have just brought it up. please look into it and let me know if you need anymore information from myside.

[werowe]

Hi,

Hi Twitter,

This thread discussions subscriptsion.json but not webhooks.json.

Would you look at my thread?

regards.

Walker Rowe

[Vinodreddi999]

@happycamper @KyleW can you please look into this? i waiting on it. my application is not receiving the call at all. but on POST MAN i see following errors when i try multiple times

{
“errors”: [
{
“code”: 214,
“message”: “High latency on CRC GET request. Your webhook should respond in less than 1 second.”
}
]
}

{
“errors”: [
{
“code”: 214,
“message”: “Non-200 response code during CRC GET request (i.e. 404, 500, etc).”
}
]
}

[Osus]

@KyleW could you help take a look at this account for the All Activities (beta):

App ID: 14785362
Owner ZedBots
Owner ID 888397152

I am having similar issues but my error is

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

The same code works on another whitelisted application/user.

I was supposed to been approved two weeks ago but I can not use account activity APIs, I always get that error but I have access to developer portal.

Any help would be appreciated.

[KyleW]

Hi @Osus - We were able to provide access to the App ID you mentioned. It looks like this was not done at creation. You environment name is: env-beta

Be sure to check out the docs if you have any questions

[KyleW]

Hi @Vinodreddi999 - The CRC errors happen when we do not receive a response to our call (you likely know this). This often occurs when your server needs to warm/wake up before it responds.

The second error (non-200) means we received a message back, but it was not what we expected. This means we are sending a request and soemthing is responding. Is it possible these requests are being filtered somewhere on your end?

[Osus]

Hi @KyleW, it works now but you have provided access to ALL API, but we need only the direct messages one.

Could you please provide access to the Standard Account Activity API DM only?

Thank you very much for your support!

[Osus]

@KyleW, @Vinodreddi999

Now that I got access I reach with
High latency on CRC GET request. Your webhook should respond in less than 1 second.
at first and then with
Non-200 response code during CRC GET request (i.e. 404, 500, etc)

I guess the problem is with non-standard ports in the url. I’ve made some tests.

I have a webhook in another account working fine with standard https port 443 and if I try that url in the new account, everything seems to be right.
But when I try to use a different port, I’ve tried two: 7085 and 13266, @Vinodreddi999 tried 10352 it does not work.
But in one of my tests I used a url with one of those ports but that url has also a running service on standard https port and my surprise was that the CRC request was been received in HTTPS 443 instead of the one I had set in the url.

To be clear. I try to use as webhook:
https://mydomain.com:7085/twitter
If something exists on:
https://mydomain.com/
I get reply:
Non-200 response code during CRC GET request (i.e. 404, 500, etc)
in fact it’s a 404 as /twitter does not exists on that hosts. That’s on my apache logs.

If there is no public
https://mydomain.com/
I get the famous
High latency on CRC GET request. Your webhook should respond in less than 1 second.

And that’s, in fact, because there is no response from that host.

So my guess is the CRC system ignores the ports on URLs and no other port than 443 can be used.

Could you take a look into this?

[brnnrn]

@KyleW
I have the same problem wiith my twitter app - got an 403 and {“errors”:[{“code”:200,“message”:“Forbidden.”}]} when i trying to subscribe webhook “account_activity/all/:env-beta/webhooks” in my APP ID: 14724134 (Baron Neyron kernel, OWNER ID 955452424805896192).
If i try to subscribe only DM-activity on “account_activity/webhooks”, so i got 401 and {“errors”:[{“code”:32,“message”:“Could not authenticate you.”}]}

pls help.

[KyleW]

@brnnrn - We were able to provide access to the App ID you mentioned. Your environment name is: env-beta

Please be sure to check the docs with any questions.

[KyleW]

@Osus - You are correct, at this time, we are only responding on port 443, the standard https port.

We can revisit this once we have a GA product.

I am going to close this topic as the initial problem has been resolved. Please create a new thread for any new items.

[KyleW]