-
Notifications
You must be signed in to change notification settings - Fork 234
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Webhook Register Issue #244
Comments
Hi Mynetx, Could you please update on this? Regards, |
3 similar comments
Hi Mynetx, Could you please update on this? Regards, |
Hi Mynetx, Could you please update on this? Regards, |
Hi Mynetx, Could you please update on this? Regards, |
Hi Mynetx, Could you please update on this? Is this under development so we can check for some different solution? Regards, |
@iceblitz0077 I will have a solution for calling these methods over the weekend. Please stay tuned! :) |
@iceblitz0077 Please re-test with the revision f2265fc. |
Hey, We have followed your instructions with the new revision & updated the package, we are still facing the same issues, can you help us? |
Hi,
How to implement Twitter Account Activity API calls in Codebird PHP?
https://developer.twitter.com/en/docs/accounts-and-users/subscribe-account-activity/api-reference/aaa-premium
We are trying to Register a Webhook.
For above call we got response as below:
{#784 ▼
+"errors": array:1 [▼
0 => {#778 ▼
+"code": 200
+"message": "Forbidden."
}
]
+"httpstatus": 403
+"rate": null
}
Also we tried to call using codebird function syntax below:
Changed call to $response = $this->api->accountActivity_all_ENV_NAME_webhooks($params); something like this but the response was "To call the templated method "account_activity/all/:env/_n_a_m_e/webhooks", specify the parameter value for "env"." This seems something wrong in the retrieving the original URL function.
For all other API calls codebird works fine.
Kindly specify something about using Twitter Account Activity API in your docs. It will be much appreciated.
Regards,
Nick
The text was updated successfully, but these errors were encountered: