GET /api/v1/pro/phishfeed → endpoint removal
urlscan.io API
Deprecated, no date
The provider deprecated the GET /api/v1/pro/phishfeed endpoint without a shutdown date. Calls made to this endpoint fail. The endpoint served as a convenience method over the Search API for retrieving detected pages.
Calls it hits
GET /api/v1/pro/phishfeed
What to use instead of these calls
Query the Search API via GET /api/v1/search/ for the detected pages instead.
In urlscan.io API's words
Phishfeed deprecated urlscan Pro - The Phishing URL endpoint is a convenience method over the Search API for retrieving detected pages.
Facts
- API
- urlscan.io API
urlscan.io - Kind
- Endpoint removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against urlscan.io API's own pages
Questions
When does this change take effect?
urlscan.io API deprecated GET /api/v1/pro/phishfeed without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: urlscan.io API has not given a shutdown date yet.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.