Safe Browsing API API

by googleapis.com

Overview

Enables client applications to check web resources (most commonly URLs) against Google-generated lists of unsafe web resources. The Safe Browsing APIs are for non-commercial use only. If you need to use APIs to detect malicious URLs for commercial purposes – meaning “for sale or revenue-generating purposes” – please refer to the Web Risk API.

Safe Browsing API is an analytics API from googleapis.com. It needs no API key. It is served over HTTPS. Its OpenAPI description documents 7 endpoints.

At a glance

Authentication: No auth
HTTPS: Yes
CORS: Unknown
Category: Analytics
Base URL: https://safebrowsing.googleapis.com/
Version: v4
Endpoints: 7
OpenAPI: Specification ↗
Spec updated: 2023-04-21

Make a first request

Replace the placeholders; the documentation says exactly where credentials go.

cURL

curl -X GET "https://safebrowsing.googleapis.com/v4/threatLists" \
  -H "Accept: application/json"

JavaScript

const response = await fetch("https://safebrowsing.googleapis.com/v4/threatLists", {
  method: "GET",
  headers: {
    "Accept": "application/json",
  },
});
const data = await response.json();
console.log(data);

Python

import requests

response = requests.request(
    "GET",
    "https://safebrowsing.googleapis.com/v4/threatLists",
    headers={
    "Accept": "application/json",
    },
    timeout=30,
)
print(response.json())

Endpoints

Method	Path	What it does
GET	`/v4/encodedFullHashes/{encodedRequest}`	safebrowsing.encodedFullHashes.get
GET	`/v4/encodedUpdates/{encodedRequest}`	safebrowsing.encodedUpdates.get
POST	`/v4/fullHashes:find`	Finds the full hashes that match the requested hash prefixes.
POST	`/v4/threatHits`	Reports a Safe Browsing threat list hit to Google. Only projects with TRUSTED_REPORTER visibility can use this method.
POST	`/v4/threatListUpdates:fetch`	Fetches the most recent threat list updates. A client can request updates for multiple lists at once.
GET	`/v4/threatLists`	Lists the Safe Browsing threat lists available for download.
POST	`/v4/threatMatches:find`	Finds the threat entries that match the Safe Browsing lists.

Questions

Does the Safe Browsing API API need an API key?

No. The Safe Browsing API API can be called without an API key or sign-up, which makes it handy for prototypes and front-end demos.

Does the Safe Browsing API API support HTTPS?

Yes, the Safe Browsing API API is served over HTTPS.

How many endpoints does the Safe Browsing API API have?

Its OpenAPI description lists 7 endpoints in version v4. All of them are shown on this page.

What are alternatives to the Safe Browsing API API?

Other Analytics APIs include Google Play Integrity API, versionhistory.googleapis.com API, Doc Converter, Perspective Comment Analyzer API, Web Fonts Developer API.

Compare alternatives →

Google Play Integrity API

Analytics

The Play Integrity API helps you check that you're interacting with your genuine app on a genuine Android device powered by Google Play services. The Play Integrity API has replaced SafetyNet Attestation and Android Device Verification.

OAuth1 endpoints

versionhistory.googleapis.com API

Analytics

Version History API - Prod

No auth4 endpoints

Doc Converter

Analytics

This api converts file formats of OpenXml and OpenOffice documents formats to vector files (e.g., svg)

No auth1 endpoints

Perspective Comment Analyzer API

Analytics

The Perspective Comment Analyzer API provides information about the potential impact of a comment on a conversation (e.g. it can provide a score for the "toxicity" of a comment). Users can leverage the "SuggestCommentScore" method to submit corrections to improve Perspective over time. Users can set the "doNotStore" flag to ensure that all submitted comments are automatically deleted after scores are returned.

OAuth2 endpoints