Can I read a form's submissions with the Fillout REST API?

Yes. Call GET /forms to list your forms, then GET /forms/{formId}/submissions to page through a form's responses, and GET /forms/{formId}/submissions/{submissionId} to fetch one submission in full. You can also delete a submission by id with the matching DELETE endpoint.

Can the Fillout REST API push new submissions to my system?

Yes. Create a webhook with POST /webhook/create that delivers submission events to your endpoint, and remove it with POST /webhook/delete when the automation is retired. That lets a workflow react the moment a form is submitted instead of polling for new responses.

Does the Fillout REST API support EU data residency?

Yes. The API is served from a US host at https://api.fillout.com/v1/api and an EU host at https://eu-api.fillout.com/v1/api, so you can keep form data in the region you choose by calling the matching base URL with the same bearer key. Point your agent at the host that fits your data-residency needs.

What are the rate limits for the Fillout REST API?

The OpenAPI spec does not specify rate limits for the Fillout REST API. Check the Fillout documentation for current limits, prefer webhooks over polling for new submissions, and have your agent back off when the API signals that it is being throttled.

How do I read form submissions through Jentic?

Search Jentic for 'get the latest submissions for a form' to load the Fillout operation with its input schema, list forms with GET /forms, then read GET /forms/{formId}/submissions. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Can I limit what my agent is allowed to do with the Fillout REST API?

Yes. Fillout puts the form id in the URL path, such as /forms/{formId}/submissions, so a rule can pin your agent to one form and the submission operations you pick, for example reading submissions while leaving out DELETE /forms/{formId}/submissions/{submissionId}. You choose the operations it may call, and every call it makes is logged.