Google Apps Script API

Name: Apps Script API
Brand: Apps Script API
Availability: InStock

✓ Official Vendor SpecDeveloper ToolsCi Cdoauth216 EndpointsREST

Install Jentic One Beta

Connect the Apps Script API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Apps Script 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.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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 Apps Script API.

Create a new Apps Script project bound to a parent Drive file or standalone

Get and update the source files inside a script project as a single content payload

Create a new immutable version of a script and list previous versions

GET STARTED

Start building with Apps Script API

Explore with Jentic

View OpenAPI Document

For Agents

Manage Google Apps Script projects - create projects, update script content, manage versions and deployments, and inspect script processes and metrics from external systems.

Use for: Create a new Apps Script project for a custom Sheets sidebar, Update the source files of a script project from a CI pipeline, Create a new version of a script ahead of a deployment, Deploy an Apps Script web app at a specific version

Not supported: Does not execute arbitrary script functions on demand, edit Drive files outside script projects, or run code outside the Apps Script runtime - use for managing Apps Script project content, versions, and deployments only.

Use Cases

Patterns agents use Apps Script API for, with concrete tasks.

★ CI/CD for Apps Script projects

Engineering teams that maintain Apps Script automations push source updates to GitHub. A CI agent uses the Apps Script API to update the project content, create a new version, and create a new deployment of that version, replacing manual editing in the in-browser script editor. The API lets the team apply code review and rollback discipline to Apps Script.

PUT /v1/projects/{scriptId}/content with the updated files, POST /v1/projects/{scriptId}/versions to create a new version, then POST /v1/projects/{scriptId}/deployments referencing that version.

Apps Script execution monitoring

An operations agent polls /v1/processes:listScriptProcesses for failed Apps Script executions across the team's automations and routes failures to an incident tracker. Pairing this with the metrics endpoint produces a dashboard of failure rates over time without each team standing up its own monitoring.

GET /v1/processes:listScriptProcesses with statuses=FAILED and post each failure to a ticketing webhook.

Backup and restore of script content

A backup agent reads the content of every Apps Script project in the team's Drive corpus on a schedule and stores the JSON payload in a versioned bucket. If a project is corrupted, the agent restores it by issuing a content update with the most recent backup, returning the project to a known good state.

GET /v1/projects/{scriptId}/content for each script, store the response, and PUT /v1/projects/{scriptId}/content with the latest backup on demand.

Agent-driven Apps Script ops through Jentic

An AI agent built on Jentic exposes Apps Script administration as tools for Workspace operators: create a script, deploy a version, list failures. It searches Jentic for the right operation by intent and runs it, with OAuth tokens kept in your Jentic One instance.

Search Jentic for 'create apps script deployment', load the deployment schema, execute against the target scriptId and version.

Key Endpoints

16 endpoints — the google apps script api manages and executes google apps script projects programmatically, including project creation, content updates, deployments, versions, and execution metrics.

METHOD

PATH

DESCRIPTION

POST

/v1/projects

Create an Apps Script project

GET

/v1/projects/{scriptId}

Get project metadata

GET

/v1/projects/{scriptId}/content

Get project source content

PUT

/v1/projects/{scriptId}/content

Update project source content

POST

/v1/projects/{scriptId}/versions

Create a new immutable version

POST

/v1/projects/{scriptId}/deployments

Create a deployment for a version

GET

/v1/processes:listScriptProcesses

List script processes for the project

GET

/v1/projects/{scriptId}/metrics

Retrieve project execution metrics

POST

/v1/projects

Create an Apps Script project

GET

/v1/projects/{scriptId}

Get project metadata

GET

/v1/projects/{scriptId}/content

Get project source content

PUT

/v1/projects/{scriptId}/content

Update project source content

POST

/v1/projects/{scriptId}/versions

Create a new immutable version

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Your Google OAuth credential is stored once, encrypted, by your own Jentic One instance and a scoped access token is injected at execution time. The credential never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'create an Apps Script deployment' or 'list Apps Script processes', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without browsing the v1 docs.

Time to first call

FAQs

Specific to using Apps Script API through Jentic.

What authentication does the Apps Script API use?

It uses Google OAuth 2.0 with scopes such as scripts.projects, scripts.deployments, and scripts.processes, declared as Oauth2 and Oauth2c. Through Jentic, OAuth tokens are stored encrypted in the vault and exchanged for short-lived access tokens at execution time.

Can I create deployments through the Apps Script API?

Yes. POST /v1/projects/{scriptId}/deployments creates a deployment of a specific version with a deploymentConfig that specifies whether it is a web app, add-on, or executable. The endpoint returns the new deployment ID, which can then be referenced in update or delete calls.

What are the rate limits for the Apps Script API?

Google applies per-project quotas to Apps Script API calls; the default is 90 queries per minute per user for read endpoints, with mutating create and update endpoints sharing a separate per-day quota that scales with usage. Quotas can be raised through the Cloud Console for sustained CI/CD usage.

How do I deploy an Apps Script version through Jentic?

Search Jentic for 'create apps script deployment', load the schema for POST /v1/projects/{scriptId}/deployments, and execute with the version number and deploymentConfig payload. Jentic returns the new deployment ID for downstream verification.

Is the Apps Script API free?

The API is free to call within Google Cloud quotas; underlying Apps Script execution is metered by the standard Apps Script execution-time quotas tied to the calling user's account, not by the API itself. There is no per-API-call charge.

How do I monitor failed Apps Script executions?

Call GET /v1/processes:listScriptProcesses with statuses=FAILED to enumerate recent failed executions for the calling user's projects, and pair it with GET /v1/projects/{scriptId}/metrics to retrieve aggregate failure counts. The metrics endpoint accepts a metricsGranularity parameter for daily or hourly bucketing.

Can I limit what my agent is allowed to do with the Apps Script API?

Yes. Because your Jentic One instance is self-hosted, your own rules decide which operations and credentials the agent may use. The Apps Script API puts the script project id in the URL path (/v1/projects/{scriptId}), so a rule can pin the agent to a single project and let it only read content, versions, and metrics for that project. State-changing operations like updating content with PUT /v1/projects/{scriptId}/content or creating a deployment with POST /v1/projects/{scriptId}/deployments are excluded unless you explicitly add them.

Google Apps Script API

Connect the Apps Script API to your agent

Capabilities

Start building with Apps Script API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs