Web Risk API: Node.js Client

release level npm version

Web Risk API client for Node.js

A comprehensive list of changes in each version may be found in the CHANGELOG.

Read more about the client libraries for Cloud APIs, including the older Google APIs Client Libraries, in Client Libraries Explained.

Table of contents:


Before you begin

  1. Select or create a Cloud Platform project.
  2. Enable billing for your project.
  3. Enable the Web Risk API API.
  4. Set up authentication with a service account so you can access the API from your local workstation.

Installing the client library

npm install @google-cloud/web-risk

Using the client library

 * Check a URI against the WebRisk API.
 * @param {string} uri A URI to pass to the Web Risk API.
async function quickstart(uri) {
  // Create the WebRisk client library.
  const {WebRiskServiceClient, protos} = require('@google-cloud/web-risk');
  const client = new WebRiskServiceClient();

  // Create an API request to check for malware, social engineering,
  // and unwanted software.
  const request = {
    uri: uri,
    threatTypes: [

  // call the WebRisk searchUris API.
  const {threat} = (await client.searchUris(request))[0];
  if (threat) {
  } else {
    console.info('no threats found');


Samples are in the samples/ directory. Each sample's README.md has instructions for running its sample.

SampleSource CodeTry it
Web_risk_service.compute_threat_list_diffsource codeOpen in Cloud Shell
Web_risk_service.create_submissionsource codeOpen in Cloud Shell
Web_risk_service.search_hashessource codeOpen in Cloud Shell
Web_risk_service.search_urissource codeOpen in Cloud Shell
Web_risk_service.submit_urisource codeOpen in Cloud Shell
Web_risk_service_v1_beta1.compute_threat_list_diffsource codeOpen in Cloud Shell
Web_risk_service_v1_beta1.search_hashessource codeOpen in Cloud Shell
Web_risk_service_v1_beta1.search_urissource codeOpen in Cloud Shell
Quickstartsource codeOpen in Cloud Shell

The Web Risk API Node.js Client API Reference documentation also contains samples.

Supported Node.js Versions

Our client libraries follow the Node.js release schedule. Libraries are compatible with all current active and maintenance versions of Node.js. If you are using an end-of-life version of Node.js, we recommend that you update as soon as possible to an actively supported LTS version.

Google's client libraries support legacy versions of Node.js runtimes on a best-efforts basis with the following warnings:

  • Legacy versions are not tested in continuous integration.
  • Some security patches and features cannot be backported.
  • Dependencies cannot be kept up-to-date.

Client libraries targeting some end-of-life versions of Node.js are available, and can be installed through npm dist-tags. The dist-tags follow the naming convention legacy-(version). For example, npm install @google-cloud/web-risk@legacy-8 installs client libraries for versions compatible with Node.js 8.


This library follows Semantic Versioning.

This library is considered to be stable. The code surface will not change in backwards-incompatible ways unless absolutely necessary (e.g. because of critical security issues) or with an extensive deprecation period. Issues and requests against stable libraries are addressed with the highest priority.

More Information: Google Cloud Platform Launch Stages


Contributions welcome! See the Contributing Guide.

Please note that this README.md, the samples/README.md, and a variety of configuration files in this repository (including .nycrc and tsconfig.json) are generated from a central template. To edit one of these files, make an edit to its templates in directory.


Apache Version 2.0