Error while registering webhook

X API Premium APIs v1.1
1

Hello!

I am trying to register a webhook for my application, but I get the message:
[{“code”:214,“message”:“Webhook URL does not meet the requirements. Invalid CRC token or json response format.”}]}’ } }

However, this endpoint was used in another Twitter App successfully. So, I don´t think the url does not meet the requirements; the message does not match the problem that is occurring probably.
I am actually trying to migrate an app from one account to other. In the account that has errors, I already have the developer account approved and I created an environment for the account activity and the correct app.

The account that has errors is: @tcuoficial, app id 15734170

Please help me.

Thank you in advance.

4

@alessandra.requena - Can you please provide the request that you are using to help us investigate?

Have you tried using this repository, this repository, or Twurl to make your request?

5

I am using GitHub - twitterdev/account-activity-dashboard: Sample web app and helper scripts to get started with the premium Account Activity API.

I am calling:
node example_scripts/webhook_management/create-webhook-config.js
(‘https://api.twitter.com/1.1/account_activity/all/envprod/webhooks.json’)

And the message that I get is: ‘{“errors”:[{“code”:214,“message”:“Webhook URL does not meet the requirements. Invalid CRC token or json response format.”}]}’ } })

Just remembering that I already use this webhook in another twitter account.

Please help!

7

First off, you cannot use the same webhook URL with two different accounts. I believe we have a different error message for that though.

This error message triggers when you are either not using the proper tokens or when your web app is not providing a proper response.

From our documentation:

Response requirements:

  • A base64 encoded HMAC SHA-256 hash created from the crc_token and your app Consumer Secret
  • Valid response_token and JSON format.
  • Latency less than 3 seconds.
  • 200 HTTP response code.
8

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.