Google Forms
The Google Forms API is a RESTful interface that lets you create and modify Google Forms programmatically, read form responses, set up watches for notifications on form changes and new responses, and integrate forms with external applications.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles Google Forms the way a machine reads it — 52 machine-readable artifacts across 3 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Google Forms scores 69.8/100 (strong), with a separate agent-readiness read of 71/100 (agent native). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Google Forms
Each block below is one kind of artifact we hold for Google Forms. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 3
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Google Forms Forms API
Operations for creating, reading, and updating forms
Google Forms Responses API
Operations for reading form responses
Google Forms Watches API
Operations for managing form change notifications
Arazzo Workflows 8
Real integrations are rarely a single call. Arazzo describes the multi-step sequences — auth, then create, then confirm — so both a human and an agent can follow the choreography, not just the endpoints.
Multi-step API workflows described with the Arazzo specification.
Google Forms Build and Grade a Quiz
Create a form, switch it into quiz mode with a graded question, publish it, and read scored submissions.
ARAZZOGoogle Forms Close a Form and Export Final Responses
Stop a form accepting responses, then take the final response export and record the closing state.
ARAZZOGoogle Forms Create and Publish a Form
Create a form, add its questions in a batch update, publish it, and read back the responder link.
ARAZZOGoogle Forms Harvest Form Responses
Read a form's question structure, page through its responses since a timestamp, and pull one response in full.
ARAZZOGoogle Forms Renew an Expiring Watch
List a form's watches and renew the existing one, or create a replacement when none survives.
ARAZZOGoogle Forms Safe Form Edit with Write Control
Read a form's current revision, apply a batch update guarded by that revision, and confirm the new revision.
ARAZZOGoogle Forms Subscribe to Response Notifications
Verify a form, register a Cloud Pub/Sub watch for new responses, and confirm the watch is active.
ARAZZOGoogle Forms Unsubscribe Form Watches
List the watches registered on a form and delete one to stop its notification delivery.
ARAZZOScroll within the panel for all 8 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
google-forms-mcp.yml
MCP SERVERPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Google Forms Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Google Forms Finops
FINOPSFeatures 8
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Form Creation
Programmatically create Google Forms with custom titles and descriptions.
Batch Updates
Apply multiple changes to a form in a single API call.
Response Collection
Read and analyze form responses programmatically.
Watch Notifications
Receive real-time notifications via Cloud Pub/Sub when forms change or responses are submitted.
Quiz Support
Create and grade quiz forms with correct answers and scoring.
Publish Settings
Control whether forms are published and accepting responses.
File Upload Questions
Support for file upload question types.
Rating Questions
Support for rating-style questions with customizable icons.
Scroll within the panel for all 8 ·
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Google Forms Api Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Google Forms API Rules
SPECTRALGoogle Forms API Rules
SPECTRALJSON Schema 4
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
JSON Structure 4
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Google Forms Api Form Response Structure
JSON STRUCTUREGoogle Forms Api Form Structure
JSON STRUCTUREGoogle Forms Api Question Structure
JSON STRUCTUREGoogle Forms Api Watch Structure
JSON STRUCTUREExamples 4
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Security Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Use Cases 5
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Automated Survey Distribution
Create and distribute surveys programmatically as part of CRM or marketing workflows.
Response Analytics
Automatically collect and analyze form responses for reporting dashboards.
Event-Driven Processing
Trigger downstream workflows when new responses are submitted using watches.
Quiz and Assessment Automation
Build automated grading systems for educational quizzes.
Data Collection Pipelines
Integrate forms into data collection pipelines for research or operations.
Integrations 4
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
Google Sheets
Automatically link form responses to Google Sheets for analysis.
Google Cloud Pub/Sub
Receive real-time notifications about form events via Pub/Sub topics.
Google Drive
Store file upload responses in Google Drive.
Google Workspace
Integrate with other Google Workspace apps for collaboration.
Resources
Every other property we hold for Google Forms — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 2
Portal, sign-up, and the first successful call
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 16
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 16 ·
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 5
Authentication, authorization, and security posture
Operate 4
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
← All providers · Data indexed from github.com/api-evangelist/google-forms · machine-readable index on apis.io