Twitter account activity API sending me my own requests from the API?

[AbdelrahmanMDM]

So it seems that the account activity api will send you a webhook no matter who made the request whether if it’s you , yes you or someone else interacting with you.

Example : You send a person a DM using Account Activity API, Account Activity API sends you the request that you just sent to the other person ? Why ? What should i do in that case ? I want to only receive requests that didn’t originate from the API rather from other users interacting with my app ? what should i do in that case ? make a check at every event type to see if it’s originating from me-myself (the authenticating user) or from another user trying to interact with my app ?
or are there better solutions ?

[snowman]

Yes, the Account Activity is designed to send all events related to the accounts you are subscribed to. It is common to ‘drop’ events that are not important to your app. For example, chatbots are typically only interested in DM events, and may decide to ignore events like Favorites happening around their account. Note that you need to respond with a ‘200’/success response code for all received events (even the ones you drop) so the Twitter side knows you received the webhook event.

And note that DMs are not sent with the Account Activity API, but with the DM API, and the Account Activity API sends webhook events around those DM messages.