---
title: "Get feature settings for a property."
method: GET
path: "/settings/v1/features/{propertyId}"
tags: ["FeatureSettings"]
---

# Get feature settings for a property.

`GET /settings/v1/features/{propertyId}`

Get feature settings for a property.<br>You must have at least one of these scopes: 'settings.read, setup.read, setup.manage'.

## Path parameters

- `propertyId` string, required

## Response `200`

Returns feature settings.

- FeatureSettingsModel
  - `areCustomRevenueSubAccountsEnabled` boolean, required — Are custom sub-accounts for revenue enabled.
  - `performAccountingForOpenInvoiceActions` boolean, required — Whether marking an AR invoice as written off/paid leads to accounting or not.
  - `showRecipientForEachLineItemOnTheInvoice` boolean, required — Whether to display the main guest's name for each charge on the invoice if the invoice contains charges from several reservations.
  - `maxAmountForMinimalInvoices` number, double, nullable — If the amount for the invoice is lower than this value, allow creating invoices with the name only.
  - `invoiceNumberPattern` string, required — Pattern to generate the invoice number. Consists of three parts: custom prefix (optional), date template (optional), and number template (required). use '0' for numbers; 'd' or 'dd' for days; 'M' or 'MM' for months; 'yy' or 'yyyy' for years. To set a custom prefix, enclose it in quotation marks ("). Allowed symbols in the prefix: digits, uppercase letters, .,_,-. Example: pattern "MUC-"yyyy0000 will produce invoice numbers like MUC-20190001.
  - `advanceInvoiceNumberPattern` string, required — Pattern to generate the advance invoice number. Consists of three parts: custom prefix (optional), date template (optional), and number template (required). use '0' for numbers; 'd' or 'dd' for days; 'M' or 'MM' for months; 'yy' or 'yyyy' for years. To set a custom prefix, enclose it in quotation marks ("). Allowed symbols in the prefix: digits, uppercase letters, .,_,-. Example: pattern "MUC-"yyyy0000 will produce invoice numbers like MUC-20190001.

## Other responses

- `400` — Bad request.
- `401` — You are unauthorized.
- `403` — Forbidden.
- `404` — The Request-URI could not be found.
- `422` — Validation errors in the request body or query params.
- `499` — Client closed request.
- `500` — An unexpected error occurred.
- `503` — The server is currently unavailable. Please try later.

---

[API](https://skmtc.dev/apaleo/apis/apaleo-settings-api.md) · [All operations](https://skmtc.dev/apaleo/apis/apaleo-settings-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/apaleo/apaleo-settings-api/revisions/da1c3b71ee9a/schema)