The new endpoint for retrieving wallet history is highly beneficial for developers, and I appreciate the quality of the data provided. However, it would be helpful to distinguish whether a token was received through an airdrop or purchased. In my case, I need to consult additional log files to determine whether a token was airdropped. Furthermore, enhancing the clarity of the spam parameter, which often remains ambiguous, would improve the situation. To address this, I am conducting my simulations. If these two areas—identifying airdropped tokens and refining the spam parameter—could be improved, it would significantly enhance our ability to analyze our portfolios. Specifically, we could better understand which tokens are sellable and which have been airdropped.
1 Like
Thanks for the feedback, we will check with api team about this
1 Like