intelowlproject
Deprecation of endpoint `POST /search/hash` in Hybrid Analysis API
As of API v2.35.0 Hybrid Analysis started deprecating the POST version of the endpoint /search/hash in favor of it's GET version.
We should update our code before the full deprecation of the endpoint in order to avoid having a broken analyzer for hash-type observables.
Hi! I'd love to take this issue as my first contribution. It looks like a great starting point. Please let me know if I can go ahead!
This issue has been marked as stale because it has had no activity for 30 days. If you are still working on this, please provide some updates.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
Hey can I work on this , I am intrested to contribute to this . Let me work on this if @ali90h is not.
Hi @vengamanaidu1 , sure! You can take a look at the linked PRs to this issue for further details. If you're in trouble feel free to open a draft PR and reach out for help! :)
Hey! thanks for assigning it to me . If i had to say I seriously know nothing how intelowl works .I read some articles about , but i have no idea where start to solve this issue . Could you help me out where to start and what to learn , i would be really keen and interested to learn something new .
thankyou !
On Fri, Sep 5, 2025 at 2:26 PM Federico Gibertoni @.***> wrote:
fgibertoni left a comment (intelowlproject/IntelOwl#2934) https://github.com/intelowlproject/IntelOwl/issues/2934#issuecomment-3257599067
Hi @vengamanaidu1 https://github.com/vengamanaidu1 , sure! You can take a look at the linked PRs to this issue for further details. If you're in trouble feel free to open a draft PR and reach out for help! :)
— Reply to this email directly, view it on GitHub https://github.com/intelowlproject/IntelOwl/issues/2934#issuecomment-3257599067, or unsubscribe https://github.com/notifications/unsubscribe-auth/BMVBUUPKGNYZYUQQPDCLFUT3RFF3LAVCNFSM6AAAAACCS3T7YOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTENJXGU4TSMBWG4 . You are receiving this because you were mentioned.Message ID: @.***>
Hey @vengamanaidu1, I think you can start by having a look at the documentation on how to contribute creating an analyzer and then try to run the project locally to understand how it works. Then you can start working at the issue with the deprecated endpoint.
Thanks for the interest @sankalp-b1401, I'll let @vengamanaidu1 have a look at the project and raise a PR first. You'll be assigned, if still interested, as soon as possible. In the meantime you can have a look at other open issues in the repository.
This issue has been marked as stale because it has had no activity for 30 days. If you are still working on this, please provide some updates.
This issue has been marked as stale because it has had no activity for 30 days. If you are still working on this, please provide some updates.
Hi @fgibertoni , I’d like to work on this issue. Could you please assign it to me?
hey @fgibertoni, before I start, could you point me to all the places where this endpoint is implemented or referenced? just want to make sure I cover everything in one go.
Hey, the main implementation is in ha_get.py file.
You can also take a look at my comment here to see what I think this fix should bring to the analyzer.
Let me know if everything sounds good to you.
Hi @fgibertoni, I’m interested in taking this issue. Could I get some guidance on how to begin?
Hey @Nivikiwi. At the moment this issue is taken by @PranavShukla7. You can have a look around other issues in the project 😃
@fgibertoni I've commited some changes on the mentioned pr could you please review it?