List form submissions with the Netlify API
Lists the submissions of one form, newest first, with name, email, the data of each field and created_at. Paginate with page and per_page: a page with fewer items than per_page is the last one.
- Identifier
- netlify_list_form_submissions
The request
POST https://connect.reportei.com/api/tools/netlify_list_form_submissions/execute
Authorization: Bearer <merchant token>
x-customer-token: <customer token>
Content-Type: application/json
Accept: application/json
{
"customer_toolkit": "<connection UUID>",
"arguments": {
"form_id": "<form_id>"
}
}Your system sends your customer's connection id and the tool arguments. The headers are the same as the rest of the Connect API: your product's token and your customer's token.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
| form_id | string | Yes | The id of the form, from List site forms. |
| state | string | No | Send spam for the submissions marked as spam. Without it, the verified ones.Values: spam |
| per_page | integer | No | Results per page, up to 100. |
| page | integer | No | Page number, starting at 1. |
Supported connections
Your customer connects their Netlify account once, with one of the modes below. The same connection serves every tool of the toolkit.
API key
Your customer pastes the app's key on a Connect screen, or your system sends the key with POST /api/customer-toolkits, with no screen.
The response
On success, Connect preserves the app's response status and body. HTTP errors returned by the app use the {error, api_error} envelope; authentication or validation can fail before execution. The X-Toolkit-Execution-Id header identifies the recorded execution, available at GET /api/tools/executions/{uuid}.
Ready for AI agents
This tool's input is a JSON Schema, available at GET /api/tools/netlify_list_form_submissions. It becomes your agent's tool definition with no conversion.
Other Netlify tools
- List sitesGETLists the sites (projects, in the Netlify UI) the account can reach, with id, name, url, custom_domain, the published deploy and build settings. The id or the domain of a site is the site_id that the other tools take. Paginate with page and per_page: a page with fewer items than per_page is the last one.
- Update sitePATCHChanges the name or the domains of a site and returns it. Only the fields sent change. The DNS of a new custom domain still has to point to Netlify.
- List site deploysGETLists the deploys of a site, newest first, with id, state, branch, context, error_message and the deploy URL. Paginate with page and per_page: a page with fewer items than per_page is the last one.
- Get deployGETReturns a deploy, with state (ready when it is live or ready to publish, error when the build failed), error_message, branch, commit_ref, published_at and the deploy URL.
- Create site buildPOSTStarts a build of a site from its connected repository and returns the build, with deploy_id to follow in Get deploy. Without branch it builds production; another branch makes a branch deploy. It waits in line when the team has no free build capacity.
- Cancel deployPOSTStops a deploy that is still queued or building, and returns it.
- Restore site deployPOSTPublishes an earlier deploy again and makes it the live version of the site, which is how a rollback works. Returns the deploy.
- List site formsGETLists the forms Netlify detected in a site, with id, name, fields and submission_count. The submissions themselves come from List form submissions.
Toolkits in the same category
See all 100 toolkitsSee Connect applied to your product.
Try it for 15 days with no card, or walk our team through your use case.
