---
title: "Ask what the installed cape's defaultSettings WOULD do under a jurisdiction"
method: GET
path: "/api/cape/defaults"
tags: ["cape"]
---

# Ask what the installed cape's defaultSettings WOULD do under a jurisdiction

`GET /api/cape/defaults`

Cape detection runs from fppinit at boot, before anyone has been asked where they are, so a cape's telemetry defaults are held rather than applied.  By the time the setup wizard has that answer, detection has already run.  This lets the wizard re-ask the question without re-running detection for real -- which would write to the settings file mid-wizard and break the property the page depends on, that nothing is persisted until Finalize. Nothing is written.  The evaluation calls the same predicate a real run calls, so the answer cannot drift from what would actually happen.  A key the user has already set is absent from both lists; a key already holding exactly the proposed value is absent too, since there is nothing to offer and nothing to explain.

## Response `200`

What the cape would set, and what it would be refused

- object

## Changes

- **2026-09-15** `a923e87eff94` — 1 info
  - endpoint added

[Change history](https://skmtc.dev/falconchristmas/apis/fpp-api/changes/api/cape/defaults/get.md)

---

[API](https://skmtc.dev/falconchristmas/apis/fpp-api.md) · [All operations](https://skmtc.dev/falconchristmas/apis/fpp-api/llms.txt) · [OpenAPI document](https://skmtc.dev/falconchristmas/apis/fpp-api/revisions/23d55a891c9a?raw)