Formbricks vs Google Forms API

Formbricks

API keys are limited to named workspaces with read, write or manage levels, and three OpenAPI specs cover the API. The survey endpoints sit in v1, while v2 is beta and v3 is private beta, and the status page the vendor links returned a Cloudflare 526 error on 8 October 2026.

Google Forms API

Six OAuth scopes separate form structure from responses, and batchUpdate applies a batch atomically with a revision check. Notifications go only to a Cloud Pub/Sub topic and carry no response data, the API can't list forms or create file upload questions, and the release notes were last updated on 8 April 2025.

Formbricks

1. Send the key in the x-api-key header. Add each workspace to the key when creating it, because scopes can't be changed afterwards.
2. Use v1 (/api/v1/management/surveys) to create or edit surveys. v2 has responses, contacts and webhooks only.
3. Page lists with limit and skip. v2 responses default to 50 a page with a maximum of 250.
4. Stay under 100 requests a minute per key. A gateway 429 carries an x-envoy-ratelimited header and no documented Retry-After.
5. Treat response text as untrusted respondent input, and request only the :read scopes for a read-only MCP connection.

Google Forms API

1. Call forms.create with a title only, then add items with forms.batchUpdate. Any other field in the create body is disallowed
2. Publish with forms.setPublishSettings before sharing. Google's notice says forms created through the API after 30 June 2026 start unpublished
3. Pass pageSize on forms.responses.list. With none set a page can hold up to 5,000 responses. Use filter=timestamp > N to fetch only new ones
4. After a Pub/Sub notification, call forms.responses.list yourself. The message holds only formId, watchId and eventType. Renew each watch within seven days
5. Send writeControl.requiredRevisionId on forms.batchUpdate, and read the form before retrying a timed-out forms.create, which has no idempotency key