> For the complete documentation index, see [llms.txt](https://docs.xyb.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xyb.co/xyb-ledger/api-reference-guides/access-permissions-and-settings-management-apis/settings-management-apis.md).

# Settings Management APIs

1. **Update System Settings**
   * **Endpoint:** `PUT /api/v1/setting`
   * **Use Case:** An admin modifies global or service-specific settings, such as enabling two-factor authentication or adjusting API rate limits. This ensures real-time configuration updates without requiring system downtime.
2. **Retrieve Specific Setting**
   * **Endpoint:** `GET /api/v1/setting/{*path}`
   * **Use Case:** A developer fetches the current value of a specific setting to verify configurations before deploying a new feature. This helps maintain consistency across different environments.
3. **Delete a Setting**
   * **Endpoint:** `DELETE /api/v1/setting/{*path}`
   * **Use Case:** An admin removes outdated or deprecated settings to maintain a clean and efficient system configuration. This prevents conflicts with new updates and ensures system security.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.xyb.co/xyb-ledger/api-reference-guides/access-permissions-and-settings-management-apis/settings-management-apis.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.