Google Area120 Tables API
Browse all Google APIs40
AI ReadinessNon-Ready (F)40/100
Official vendor OpenAPI document · agent-readyProductivityCollaborationoauth210 EndpointsREST
For Agents
Read and write structured rows in Google Area 120 Tables, including listing tables and workspaces and batch-importing records.
Use for: I need to import a CSV of leads into a Google Area 120 Tables table, List all tables in my Area 120 workspace, Retrieve the row that matches a specific record ID, Update the status column for a row in a project tracker table
Not supported: Does not handle formulas, charts, or general spreadsheet computation, and does not manage file permissions - use for structured row read/write in Google Area 120 Tables only.
The Area120 Tables API provides programmatic access to Google's Area 120 Tables product, a structured spreadsheet-database hybrid for tracking projects, tasks, and team data. It exposes operations to read tables and workspaces, retrieve and update individual rows, and batch create rows for bulk imports. Tables are organised into workspaces shared across team members, and each row is a structured record with typed columns. The API is scoped to working with structured row data, not free-form documents or general spreadsheet computation.
Install Jentic One Beta
Connect the Area120 Tables API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Area120 Tables API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgoogleapis.com%2Farea120tables" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgoogleapis.com%2Farea120tables" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Area120 Tables API.
List all tables and workspaces a user has access to with filtering by view
Retrieve a single row by resource name with selectable view detail levels
Batch create up to hundreds of rows in one call against /v1alpha1/{+parent}/rows:batchCreate
Update individual row values with field-mask-based partial updates
Delete rows from a table by resource name to clean up stale records
Page through large row sets using pageToken and pageSize on the rows endpoint
Use Cases
Patterns agents use Area120 Tables API for, with concrete tasks.
★ Bulk Import Records into a Tracker
Migrate data from an existing spreadsheet, CSV, or external system into a Google Area 120 Tables table by batch-creating rows in a single API call. The batchCreate endpoint accepts an array of row objects mapped to the table's column schema, returning the created resource names. Suitable for one-time migrations or scheduled syncs of up to a few hundred rows per request.
Read 200 rows from a source CSV, map columns to the target table schema, and POST to /v1alpha1/{parent}/rows:batchCreate to create them all in one call.
Sync External Tickets into a Workspace Table
Keep an Area 120 Tables tracker in sync with an external ticketing or CRM system by polling for new records and appending them as rows. The API supports listing existing rows with paging, creating new rows individually, and patching status fields when source records change. Ideal for lightweight integrations where Tables is the team-facing surface.
Poll an external ticket source, diff against existing rows in the target table, and POST new tickets to /v1alpha1/{parent}/rows.
Programmatic Cleanup of Stale Rows
Maintain hygiene in shared Area 120 Tables trackers by listing rows, applying age or status filters in code, and deleting expired entries. Useful for automated retention policies on team task lists, intake forms, and event logs without manually pruning the table.
List rows from a table, filter rows older than 90 days by a date column, and DELETE each one by resource name.
Agent-Driven Table Updates via Jentic
Let an AI agent read structured records from a Google Area 120 Tables tracker and write back updates as a result of a workflow run. The agent uses Jentic to discover the row update operation, loads its schema, and patches specific row fields without needing direct OAuth setup. Suitable for status updates, enrichment workflows, and assignment changes driven by agent reasoning.
Use Jentic search for 'update a row in Google Tables', load the patch operation schema, and call it with the row name and updated field values.
Key Endpoints
10 endpoints — the area120 tables api provides programmatic access to google's area 120 tables product, a structured spreadsheet-database hybrid for tracking projects, tasks, and team data.
METHOD
PATH
DESCRIPTION
GET
/v1alpha1/tables
List tables the caller has access to
GET
/v1alpha1/workspaces
List workspaces
GET
/v1alpha1/{+parent}/rows
List rows in a table with paging
POST
/v1alpha1/{+parent}/rows
Create a single row
POST
/v1alpha1/{+parent}/rows:batchCreate
Batch create multiple rows
PATCH
/v1alpha1/{+name}
Update a row with a field mask
DELETE
/v1alpha1/{+name}
Delete a row by resource name
GET
/v1alpha1/tables
List tables the caller has access to
GET
/v1alpha1/workspaces
List workspaces
GET
/v1alpha1/{+parent}/rows
List rows in a table with paging
POST
/v1alpha1/{+parent}/rows
Create a single row
POST
/v1alpha1/{+parent}/rows:batchCreate
Batch create multiple rows
PATCH
/v1alpha1/{+name}
Update a row with a field mask
DELETE
/v1alpha1/{+name}
Delete a row by resource name
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
A
Area120 Tables API
- Non-Ready (F)40/100
71
Foundational Compliance56
Developer Experience & Jentic Compatibility17
AI-Readiness & Agent Experience94
Agent Usability63
Security59
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
71
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A-Signals: 4
83%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
0%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
100%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
56
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: CSignals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
25%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
17
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
69%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
0%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
0%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
63
Security
Trust, risk posture, and security compliance.
Grade: B-Signals: 1
62%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
59
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: C+Signals: 1
59%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Area120 Tables API by hand means configuring Google OAuth2, granting the right Tables scopes, and refreshing access and refresh tokens for each row operation yourself. Through Jentic you install once, import the Area120 Tables API from the API Directory, store the OAuth credential once, and your agent calls it.
Permission scoping
This API puts the table name in the URL path (/v1alpha1/{parent}/rows, /v1alpha1/{name}), so a rule can pin your agent to one table: it can list and create rows there and nothing else. You choose the operations it may call, so actions like deleting a row are not included unless you add them.
Credential isolation
Your Google OAuth credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'create a row in a Google Tables tracker', and Jentic returns the matching Area120 Tables operation with its input schema so the agent calls the right endpoint without browsing Google's discovery docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Area120 Tables API through Jentic.
What authentication does the Area120 Tables API use?
The API uses Google OAuth 2.0 with the Oauth2 and Oauth2c security schemes declared in the spec. Callers must obtain an access token with a Tables scope and send it in the Authorization header. Through Jentic, OAuth tokens are stored in the encrypted vault so an agent never touches the raw refresh token.
Can I batch insert rows with the Area120 Tables API?
Yes. POST to /v1alpha1/{parent}/rows:batchCreate with an array of row objects to create multiple rows in one call. This is the recommended path for migrations and scheduled syncs rather than calling the single-row create endpoint in a loop.
What are the rate limits for the Area120 Tables API?
The spec does not declare numeric rate limits. As with other googleapis.com endpoints, requests are subject to per-project quotas configured in the Google Cloud console; check the project's quota dashboard before running large batch jobs.
How do I update a single row with the Area120 Tables API through Jentic?
Search Jentic for 'update a row in Google Tables', load the schema for the PATCH /v1alpha1/{+name} operation, and execute it with the row resource name and the field mask describing which columns to change. The token is supplied from your Jentic One instance at execute time.
Is the Area120 Tables API generally available?
The API is exposed under v1alpha1, indicating an alpha release. Field shapes and operations may change without strict backward-compatibility guarantees, so production integrations should pin to the alpha version and watch for upgrade notices.
Can I delete rows from a table programmatically?
Yes. Send DELETE to /v1alpha1/{+name} where the name is the row's full resource path. Deletes are immediate and remove the row from the table's view.
Can I limit what my agent is allowed to do with the Area120 Tables API?
Yes. Because you self-host Jentic One, your own rules decide which Area120 Tables operations and credentials your agent may use. Since this API carries the table name in the URL path, such as /v1alpha1/{parent}/rows and /v1alpha1/{name}, you can pin the agent to a single table and allow only listing and creating rows there. Destructive operations like deleting a row are excluded unless you explicitly add them, and the stored Google OAuth credential is injected at execution time rather than exposed to the agent.
GET STARTED