---
title: "Get a form's settings"
method: GET
path: "/api/v1/manage/forms/{form}/settings"
tags: ["Settings"]
---

# Get a form's settings

`GET /api/v1/manage/forms/{form}/settings`

## Request

- Base URL: `https://fillo.so`
- URL: `https://fillo.so/api/v1/manage/forms/{form}/settings`
- Auth: HTTP bearer

The form's current operational settings (notifications, receipts, save-and-resume, response limits, and the like). Scope: settings:manage.

## Path parameters

- `form` string, required

## Response `200`

The form's settings.

- FormSettingsEnvelope
  - `settings` FormSettings, required: A partial FormSettings patch (see @usefillo/core FormSettings): booleans such as notifyEmailIncludeAnswers, sendReceipt, saveProgress, draftAnswersVisible, resumeEmails, and draftDigest; strings such as notifyEmail, notifyEmailReplyToField, and resumeUrl; an array notifyEmailAnswerFields; and objects such as responseLimit and trust. Any key set to null is cleared. Six of the keys are not operational settings but part of the form's definition — submitMode, submitLabel, successTitle, successMessage, redirectUrl, and showProgress live inside the form schema: patching any of them additionally requires forms:write, and code-managed forms reject them outright.

## Other responses

- `401`: Missing, malformed, unknown, revoked, or expired key.
- `403`: The key is valid but lacks the required scope.
- `404`: No such resource in this project (returned instead of 403 for ids in other projects).
- `429`: Per-key (120/min), per-workspace (240/min), or per-IP (300/min) rate limit exceeded. Retry after the Retry-After header.

---

[API](https://skmtc.dev/fillo/apis/fillo-management-api.md) · [All operations](https://skmtc.dev/fillo/apis/fillo-management-api/llms.txt) · [OpenAPI document](https://skmtc.dev/fillo/apis/fillo-management-api/revisions/867f943f04f5?raw)