Okapi Okapi

Google Forms API POST /v1/forms changes: new forms are created unpublished

Stopped workingSubscribe to Google Forms APIShare

On June 30, 2026, the behavior of POST /v1/forms changed so that newly created forms are unpublished by default. Because unpublished forms cannot receive responses, workflows expecting immediate submissions fail since that date.


Calls it hits

  • POST /v1/forms

What to use instead of these calls

After creating a form, publish it by calling POST /v1/forms/{formId}:setPublishSettings with publishSettings.publishState.isPublished set to true.

In Google Forms API's words

If no action is taken, then new forms created using APIs after June 30, 2026, will be in an unpublished state by default and won't receive responses.

Google Forms API, Announcement

Facts

API
Google Forms API forms.googleapis.com
Kind
Behaviour change
Announced
April 8, 2025
Takes effect
June 30, 2026
Calls after that day
Fail
Source
Announcement
Last updated
Verified
, against Google Forms API's own pages

Questions

When does this change take effect?

Calls to POST /v1/forms on Google Forms API stopped working on June 30, 2026.

What happens to calls after June 30, 2026?

They have failed since June 30, 2026.

How do I find the calls this hits in my code?

Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.


You fixed this one by hand.

Okapi opens the pull request with the fix before the next breaking change reaches your code.

Add to GitHub

Get notifications

Subscribe to Google Forms API

Hear about each breaking change Google Forms API announces, in your feed reader, calendar or Slack.

1What to follow

Provider
  • Google Forms API

2Where to get it

/breaking-changes/feed.xml

Paste it into Feedly, Inoreader, NetNewsWire or any reader. New changes show up as they're announced.