Apps Script API

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

✓ Official Vendor SpecDeveloper ToolsCi Cdoauth216 EndpointsREST

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.

Quickstart

Get started with Apps Script API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"create apps script deployment"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Apps Script API 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

Create, list, get, update, and delete deployments that publish a version as add-on or web app

GET STARTED

Start building with Apps Script API API

Explore with Jentic

View OpenAPI Document

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.

The Google Apps Script API manages and executes Google Apps Script projects programmatically, including project creation, content updates, deployments, versions, and execution metrics. It exposes endpoints for retrieving and updating script content, listing and creating versions and deployments, and enumerating script processes and metrics so operators can build CI/CD pipelines around Apps Script. The API enables external systems to deploy and monitor Apps Script automations that extend Google Workspace and Google Sheets.

Use Cases

Patterns agents use Apps Script API 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 the Jentic vault.

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 though Jentic?

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

Credential isolation

Apps Script OAuth 2.0 credentials are stored encrypted in the Jentic vault. Agents receive a scoped, short-lived access token at execution time so raw refresh tokens never enter the agent context.

Intent-based discovery

Agents search Jentic with intents like 'create apps script deployment' or 'list apps script processes', and Jentic returns the matching operation with its full schema, so the agent calls the correct endpoint without browsing the v1 docs.

Time to first call

Direct integration takes 2-3 days to wire OAuth, content updates, and deployment lifecycle. Through Jentic the same flow is under 1 hour: search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Google Drive API

Hosts Apps Script project files and bound documents.

Use Drive to manage the parent file; use Apps Script API to manage the bound script.

Complementary

Google Sheets API

Targets the spreadsheets that Apps Script projects automate.

Use Sheets for cell-level operations; use Apps Script when the automation must run inside the spreadsheet's UI.

Alternative

Google Workspace Events API

Subscribe to Workspace events without hosting Apps Script.

Choose Workspace Events for event-driven backends; choose Apps Script when the automation must extend the Workspace UI.

Alternative

Cloud Functions API

Run general-purpose serverless code outside the Apps Script runtime.

Choose Cloud Functions when the automation needs custom dependencies; choose Apps Script for native Workspace UI extensions.

FAQs

Specific to using Apps Script API 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.