Skip to content

APIVoid updated to v2 Closes #3006#3208

Merged
mlodic merged 3 commits intointelowlproject:developfrom
AnshSinghal:develop
Jan 18, 2026
Merged

APIVoid updated to v2 Closes #3006#3208
mlodic merged 3 commits intointelowlproject:developfrom
AnshSinghal:develop

Conversation

@AnshSinghal
Copy link
Contributor

@AnshSinghal AnshSinghal commented Jan 17, 2026

Closes #3006

Description

Updated v1 API to v2

Type of change

Please delete options that are not relevant.

  • Bug fix (non-breaking change which fixes an issue).

Checklist

  • I have read and understood the rules about how to Contribute to this project
  • The pull request is for the branch develop
  • A new plugin (analyzer, connector, visualizer, playbook, pivot or ingestor) was added or changed, in which case:
    • I strictly followed the documentation "How to create a Plugin"
    • Usage file was updated. A link to the PR to the docs repo has been added as a comment here.
    • Advanced-Usage was updated (in case the plugin provides additional optional configuration). A link to the PR to the docs repo has been added as a comment here.
    • I have dumped the configuration from Django Admin using the dumpplugin command and added it in the project as a data migration. ("How to share a plugin with the community")
    • If a File analyzer was added and it supports a mimetype which is not already supported, you added a sample of that type inside the archive test_files.zip and you added the default tests for that mimetype in test_classes.py.
    • If you created a new analyzer and it is free (does not require any API key), please add it in the FREE_TO_USE_ANALYZERS playbook by following this guide.
    • Check if it could make sense to add that analyzer/connector to other freely available playbooks.
    • I have provided the resulting raw JSON of a finished analysis and a screenshot of the results.
    • If the plugin interacts with an external service, I have created an attribute called precisely url that contains this information. This is required for Health Checks (HEAD HTTP requests).
    • If a new analyzer has beed added, I have created a unittest for it in the appropriate dir. I have also mocked all the external calls, so that no real calls are being made while testing.
    • I have added that raw JSON sample to the get_mocker_response() method of the unittest class. This serves us to provide a valid sample for testing.
    • I have created the corresponding DataModel for the new analyzer following the documentation
  • I have inserted the copyright banner at the start of the file: # This file is a part of IntelOwl https://github.com/intelowlproject/IntelOwl # See the file 'LICENSE' for copying permission.
  • Please avoid adding new libraries as requirements whenever it is possible. Use new libraries only if strictly needed to solve the issue you are working for. In case of doubt, ask a maintainer permission to use a specific library.
  • If external libraries/packages with restrictive licenses were added, they were added in the Legal Notice section.
  • Linters (Black, Flake, Isort) gave 0 errors. If you have correctly installed pre-commit, it does these checks and adjustments on your behalf.
  • I have added tests for the feature/bug I solved (see tests folder). All the tests (new and old ones) gave 0 errors.
  • If the GUI has been modified:
    • I have a provided a screenshot of the result in the PR.
    • I have created new frontend tests for the new component or updated existing ones.
  • After you had submitted the PR, if DeepSource, Django Doctors or other third-party linters have triggered any alerts during the CI checks, I have solved those alerts.

Important Rules

  • If you miss to compile the Checklist properly, your PR won't be reviewed by the maintainers.
  • Everytime you make changes to the PR and you think the work is done, you should explicitly ask for a review by using GitHub's reviewing system detailed here.

Copilot AI review requested due to automatic review settings January 17, 2026 08:59
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates the APIVoid analyzer integration from API v1 to v2, addressing issue #3006.

Changes:

  • Updated API base URL from https://endpoint.apivoid.com to https://api.apivoid.com/v2
  • Modernized endpoint paths (e.g., domainbldomain-reputation, iprepip-reputation, urlrepurl-reputation)
  • Changed authentication method from query parameter to HTTP header using X-API-Key

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copilot AI review requested due to automatic review settings January 17, 2026 09:34
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated no new comments.


💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@AnshSinghal
Copy link
Contributor Author

@mlodic can we merge?

@mlodic
Copy link
Member

mlodic commented Jan 17, 2026

compile the PR template appropriately, there's missing stuff

@AnshSinghal
Copy link
Contributor Author

Hi @mlodic I have updated the requested changes and compiled the same.

@fgibertoni
Copy link
Contributor

fgibertoni commented Jan 18, 2026

Hey, thanks for raising this.
Can you please provide a screenshot of the result after your fix?

@AnshSinghal
Copy link
Contributor Author

Hi @fgibertoni The api is now paid so I am unable to test the same. But I have checked the changelog docs thoroughly and also tested the analyzer that returns a 403 forbidden error because of api key.

@mlodic
Copy link
Member

mlodic commented Jan 18, 2026

considering I confirm this is a paid analyzer, it's not necessary to test it with a live analysis. Also, these analyzers are not currently supported anymore by the project, as an open source free project we assist for integrations with free analyzers.

So I think it is fair to just merge this anyway.

@mlodic mlodic merged commit ed98710 into intelowlproject:develop Jan 18, 2026
15 of 16 checks passed
@webaddicto
Copy link

Just FYI, the v2 I see uses POST with JSON payload, so I think this:

r = requests.get(complete_url, headers=headers, params=payload)

Should be changed to:

r = requests.post(complete_url, headers=headers, json=payload)

@AnshSinghal
Copy link
Contributor Author

Just FYI, the v2 I see uses POST with JSON payload, so I think this:

r = requests.get(complete_url, headers=headers, params=payload)

Should be changed to:

r = requests.post(complete_url, headers=headers, json=payload)

Please check the latest commit.

@webaddicto
Copy link

Yes sorry, didn't notice it was already done.

IshaanXCoder pushed a commit to IshaanXCoder/IntelOwl that referenced this pull request Jan 19, 2026
* udated to v2

* updated get request to post

* updated test file
@mlodic mlodic linked an issue Jan 30, 2026 that may be closed by this pull request
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Analyzer ApiVoid uses incorrect url

5 participants