Posted by Alex Wozniak, Software Engineer, Safe Browsing Team
In May 2016, we
introduced the latest version of the
Google Safe Browsing API (v4). Since this launch, thousands of developers around the world have adopted the API to protect over
3 billion devices from unsafe web resources.
Coupled with that announcement was the deprecation of legacy Safe Browsing APIs, v2 and v3. Today we are announcing an official turn-down date of October 1st, 2018, for these APIs. All v2 and v3 clients must transition to the v4 API prior to this date.
To make the switch easier, an open source implementation of the Update API (v4) is available on
GitHub. Android developers always get the latest version of Safe Browsing’s data and protocols via the
SafetyNet Safe Browsing API.
Getting started is simple; all you need is a Google Account, Google Developer Console project, and an API key.
For questions or feedback, join the discussion with other developers on the
Safe Browsing Google Group. Visit
our website for the latest information on Safe Browsing.
No comments:
Post a Comment
You are welcome to contribute comments, but they should be relevant to the conversation. We reserve the right to remove off-topic remarks in the interest of keeping the conversation focused and engaging. Shameless self-promotion is well, shameless, and will get canned.
Note: Only a member of this blog may post a comment.