Google Safe Browsing API
/v4/* version retirement
Deprecated, no dateSubscribe to Google Safe Browsing APIShare
Google Safe Browsing API v4 endpoints matching /v4/* have been deprecated without a shutdown date. Google Safe Browsing API states that the Safe Browsing APIs (v4) are deprecated. Requests sent to these endpoints will eventually fail.
Calls it hits
/v4/*
What to use instead of these calls
Migrate to the Safe Browsing API v5 by using GET /v5/hashes:search for lookups and GET /v5/hashLists:batchGet instead of threatListUpdates.fetch.
In Google Safe Browsing API's words
The Safe Browsing APIs (v4) are deprecated.
Facts
- API
- Google Safe Browsing API
safebrowsing.googleapis.com - Kind
- Version retirement
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Google Safe Browsing API's own pages
Questions
When does this change take effect?
Google Safe Browsing API deprecated /v4/* without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Google Safe Browsing 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.