Fetching all your form submissions is useful. Fetching only the ones you care about right now is faster.
The GET /api/forms/:formId/data endpoint supports column-level filtering through query parameters—no configuration required.
How filtering works
Any query parameter that isn't reserved maps directly to a column in your sheet.
If your sheet has a status column, this request returns only rows where that column equals new:
GET /api/forms/your-form-id/data?status=new
Multiple filters are applied together. This returns only new submissions from paid traffic:
GET /api/forms/your-form-id/data?status=new&source=paid
Both conditions must match. No SQL, no config file.
Reserved parameters
A few query params are reserved for future pagination and sorting:
limitpagecursorsort
Everything else is treated as a column filter.
Practical examples
Sales follow-up queue: Add a hidden status field to your demo request form. Your CRM team queries ?status=pending each morning.
Region-specific views: Include a region field in your signup form. Route different teams to ?region=emea or ?region=americas.
Source attribution: Pass ?source=homepage to separate organic leads from paid campaign entries.
What you don't need
No extra backend logic. No view tables. No scheduled syncs.
Your form keeps writing to the sheet. The filters let any internal tool slice that data on demand.
Keep your form fields consistent
Column matching is case-insensitive and normalizes spaces to underscores. A column named Request Type matches the query parameter request_type.
If you rename a column in the sheet, update the query parameter in your scripts to match.
Want to start filtering your submission data today? Connect your form to Info2Sheets.