Fillout API Documentation
This is the complete API documentation for connecting to the Fillout API using MindCloud's Universal API. If you are new to MindCloud, start with the Introduction to see how one API can sit in front of many different apps.
MindCloud is an integration company that offers one normalized API to access 3,100+ apps from a single place. It cleans up provider-specific quirks, keeps requests and responses consistent, and centralizes authentication so you do not need to manage separate flows for every app. Browse other apps.
Meet Fillout: Connect Fillout forms and Zite databases to list forms, manage submissions, and work with databases, tables, fields, and records through the Fillout REST APIs. Keep reading to get started.
Quickstart
Before you run your first Fillout request, you need three things:
- A MindCloud account — sign in or create an account at MindCloud.
- A MindCloud API Key — create one in API Keys. Keep it on your server.
- At least one Fillout connection — create or choose one in Connections. Note its
connectionId.
Every Fillout action uses the same URL pattern:
https://connect.mindcloud.co/v1/universal/fillout/latest/actions/{actionSlug}You need a MindCloud API Key and a Fillout connection. Then call an action such as Get Database By Id:
curl --request GET \
--url "https://connect.mindcloud.co/v1/universal/fillout/latest/actions/get-database-by-id" \
--header "Authorization: Bearer $MINDCLOUD_API_KEY" \
--get \
--data-urlencode "connectionId=$CONNECTION_ID"Every response comes back in the same envelope, with your rows in a data array:
{
"success": true,
"data": [
{ "id": "1042", "name": "Ava" }
],
"meta": {}
}After your first request works, use Shape your requests to control arguments, pagination, filtering, fields, and errors.
Authentication
Authentication has two layers. Your MindCloud API Key authenticates the request to MindCloud, sent as a Bearer token in the Authorization header. The connectionId selects the connected Fillout account that should run the action. MindCloud stores and refreshes the Fillout credentials behind that connection, so you never send provider tokens with your requests.
Pass connectionId in the query string for GET and DELETE actions, and in the JSON body for POST, PUT, and PATCH actions. Keep your MindCloud API Key on your server; do not ship it in browser code, mobile apps, public repositories, or logs.
Fillout actions
All 26 published actions for this Fillout version. Each page documents the endpoint, arguments, and response controls.
- POSTCreate Database
- POSTCreate Database Webhook
- POSTCreate Field
- POSTCreate Form Submission
- POSTCreate Form Webhook
- POSTCreate Record
- POSTCreate Table
- DELETEDelete Database
- DELETEDelete Database Webhook
- DELETEDelete Field
- DELETEDelete Form Submission
- DELETEDelete Form Webhook
- DELETEDelete Record
- DELETEDelete Table
- GETGet Database By Id
- GETGet Databases
- GETGet Form Metadata
- GETGet Form Submission
- GETGet Record By Id
- GETList Database Webhooks
- GETList Form Submissions
- GETList Forms
- GETList Records
- PUTUpdate Field
- PUTUpdate Record
- PUTUpdate Table
Related apps
More apps on the Universal API, behind the same REST shape. Or browse all apps.