Authenticate with Formstack's OAuth2 flow and read/write form submissions via the API
domain: developers.formstack.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Create an application on the Formstack API page to obtain a Client ID and Client Secret, and configure an OAuth2 redirect URI
Direct the user through the OAuth2 authorization flow to obtain an access token for their account
Decide whether to target the established V2 API or the newer OpenAPI-compliant V2025 API depending on which endpoints/features you need
Call GET /form/{id}/submission with the Authorization: Bearer {access_token} header to list submissions for a form
Call POST /form/{id}/submission with field-keyed data to create a new submission programmatically
Use PUT to update or DELETE to remove a specific submission by ID when managing existing records
Known gotchas
Formstack currently maintains two parallel API versions (V2 and the newer V2025) with different conventions -- confirm which version a given endpoint/example applies to before mixing calls across them
Access tokens are obtained per-user via OAuth2, not via a single static account-wide API key, so multi-tenant integrations need a token per connected Formstack user
Submission field keys correspond to internal field IDs rather than display labels -- you generally need to fetch the form definition first to map labels to the correct field keys
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?