Google Forms API

Name: Google Forms API API
Brand: Google Forms API
Availability: InStock

✓ Official Vendor SpecProductivityForms Surveysoauth210 EndpointsREST

For Agents

Create Google Forms, modify their structure with batch updates, read submitted responses, and subscribe to response notifications. Suited for agents that automate intake, surveys, or feedback collection.

Quickstart

Get started with Google Forms 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 a google form"

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

Capabilities

What an agent can do with Google Forms API API.

Create a new Google Form with a title and items

Mutate form structure and items atomically with forms:batchUpdate

Retrieve a form's full definition and metadata

List all responses to a form with pagination

Get a single response by id for processing

GET STARTED

Start building with Google Forms API API

Explore with Jentic

View OpenAPI Document

Use for: Create a new Google Form with a set of questions, Add a multiple-choice question to an existing form, Retrieve all responses for a feedback form, Get a single form response by id

Not supported: Does not handle response editing, payment collection, or signature workflows — use Forms for survey and intake creation only.

The Google Forms API lets developers create, retrieve, and modify Google Forms and read their responses programmatically. It supports batch updates that change form structure, items, and settings in a single transaction, plus a watch system that notifies an external endpoint when responses arrive. This API turns Forms into a building block for survey workflows, intake systems, and data collection automations.

Use Cases

Patterns agents use Google Forms API API for, with concrete tasks.

★ Programmatic Form Creation for Intake Workflows

Operations and HR teams often need to spin up a structured intake form per project, candidate, or vendor. The Forms API supports creating a form and then using batchUpdate to add sections, questions, and validation in a single atomic call. This lets a backend service generate consistent, branded forms on demand instead of asking staff to copy templates by hand.

Call POST /v1/forms with the title 'Vendor Onboarding', then POST /v1/forms/{formId}:batchUpdate with createItem requests for vendor name, contact email, and tax id questions.

Real-Time Response Processing

Survey processing pipelines need to react to each new submission. The watches resource lets an application register a Cloud Pub/Sub topic to receive a push notification when responses arrive or the form schema changes. Combined with responses.get on the response id, this enables real-time enrichment, ticket creation, or downstream notification.

Call POST /v1/forms/{formId}/watches with eventType RESPONSES and a Pub/Sub topic, then on each notification call GET /v1/forms/{formId}/responses/{responseId}.

Bulk Response Export for Analysis

Research and analytics teams want to export all responses from a form into a data warehouse. The list responses endpoint paginates through every submission and returns answers keyed by question id, which can be joined with the form definition from forms.get to produce a flat table for analysis.

Call GET /v1/forms/{formId}/responses, paginate with pageToken, and write each response to a data warehouse keyed by responseId.

Agent-Built Surveys

An AI assistant can generate a survey for a user's described intent, then provision the matching Google Form via Jentic. The agent searches for the create form and batch update operations, loads their schemas, and executes them so the user receives a shareable form URL within seconds. The agent never sees the user's underlying OAuth credentials.

Use Jentic to search 'create a google form', load the create and batchUpdate schemas, and execute them to provision a survey from an agent-generated question list.

Key Endpoints

10 endpoints — the google forms api lets developers create, retrieve, and modify google forms and read their responses programmatically.

METHOD

PATH

DESCRIPTION

POST

/v1/forms

Create a new Google Form

GET

/v1/forms/{formId}

Get a form's definition

POST

/v1/forms/{formId}:batchUpdate

Apply a batch of structural updates

GET

/v1/forms/{formId}/responses

List responses for a form

POST

/v1/forms/{formId}/watches

Subscribe to response notifications

POST

/v1/forms/{formId}:setPublishSettings

Update publish settings for a form

POST

/v1/forms

Create a new Google Form

GET

/v1/forms/{formId}

Get a form's definition

POST

/v1/forms/{formId}:batchUpdate

Apply a batch of structural updates

GET

/v1/forms/{formId}/responses

List responses for a form

POST

/v1/forms/{formId}/watches

Subscribe to response notifications

Why though Jentic?

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

Credential isolation

OAuth refresh tokens are stored encrypted in the Jentic vault. Agents receive scoped, short-lived access tokens for the requested forms scopes only.

Intent-based discovery

Agents search by intent (e.g., 'create a google form' or 'list form responses') and Jentic returns the matching operation with its batchUpdate or response request schema.

Time to first call

Direct integration: 1-2 days for OAuth, batchUpdate request shape, and Pub/Sub watch wiring. Through Jentic: under 30 minutes — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Google Sheets API

Spreadsheet API often used as a destination for Forms responses.

Use Sheets when responses must be analysed, charted, or reformatted; Forms API for the form definition itself.

Complementary

Google Drive API

Manages the Drive container that holds the form file.

Use Drive to share, move, or set permissions on the form file; Forms API for content edits.

Complementary

Google Calendar API

Schedule events triggered from form responses, such as interview slots.

Pair with Forms when a submission should generate a calendar event.

FAQs

Specific to using Google Forms API API through Jentic.

What authentication does the Google Forms API use?

It uses Google OAuth 2.0 with forms.body and forms.responses.readonly scopes. Through Jentic, refresh tokens are stored encrypted in the vault and agents only see scoped, short-lived bearer tokens.

Can I add multiple-choice questions to a form with this API?

Yes. Use POST /v1/forms/{formId}:batchUpdate with a createItem request whose questionItem.question.choiceQuestion.type is RADIO or CHECKBOX and supply the option list.

What are the rate limits for the Google Forms API?

Google enforces standard per-user and per-project quotas, typically around 60 read requests per minute per user with similar write limits. Quota errors return HTTP 429 and should be retried with backoff.

How do I get notified when a new response arrives through Jentic?

Search Jentic for 'subscribe to google forms responses', load the schema for POST /v1/forms/{formId}/watches, and execute it with eventType RESPONSES and your Cloud Pub/Sub topic to receive push notifications on each submission.

Is the Google Forms API free?

Yes, the Forms API itself has no cost. Standard Google OAuth verification rules apply for apps requesting restricted scopes.

Can I edit responses through this API?

No. Responses are read-only via the API. You can list and get responses, but updating answers must be done by the respondent through the form itself.