Area120 Tables API: Node.js Client

release level npm version

Tables 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 Area120 Tables 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/area120-tables

Using the client library

// Imports the Google Cloud client library

const {TablesServiceClient} = require('@google/area120-tables');

// TODO(developer): replace with your prefered project ID.
// const projectId = 'my-project'

// Creates a client
const client = new TablesServiceClient();

async function listTables() {
  const res = await client.listTables();



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

SampleSource CodeTry it
Tables_service.batch_create_rowssource codeOpen in Cloud Shell
Tables_service.batch_delete_rowssource codeOpen in Cloud Shell
Tables_service.batch_update_rowssource codeOpen in Cloud Shell
Tables_service.create_rowsource codeOpen in Cloud Shell
Tables_service.delete_rowsource codeOpen in Cloud Shell
Tables_service.get_rowsource codeOpen in Cloud Shell
Tables_service.get_tablesource codeOpen in Cloud Shell
Tables_service.get_workspacesource codeOpen in Cloud Shell
Tables_service.list_rowssource codeOpen in Cloud Shell
Tables_service.list_tablessource codeOpen in Cloud Shell
Tables_service.list_workspacessource codeOpen in Cloud Shell
Tables_service.update_rowsource codeOpen in Cloud Shell
Quickstartsource codeOpen in Cloud Shell
Quickstart.testsource codeOpen in Cloud Shell

The Area120 Tables 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/area120-tables@legacy-8 installs client libraries for versions compatible with Node.js 8.


This library follows Semantic Versioning.

This library is considered to be in preview. This means it is still a work-in-progress and under active development. Any release is subject to backwards-incompatible changes at any time.

More Information: Google Cloud Platform Launch Stages


Contributions welcome! See the Contributing Guide.

Please note that this, the samples/, 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