> For the complete documentation index, see [llms.txt](https://developers-apps-in-toss.toss.im/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers-apps-in-toss.toss.im/documentation/api-and-sdk-en/sdk/domains-api/navigationbar/navigationbar.setoptions.md).

# NavigationBar.setOptions

### Function description

Change the Navigation Bar's back button, home button, and title display, transparency, background color, and icon/text theme. Only the fields you pass are applied, and omitted fields keep the value applied previously. Before the first call, the value is in the mini app config's `navigationBar`is.

`transparentBackground`is `true`then the Navigation Bar overlaps the content and does not take up layout height. In this case `backgroundColor`is not applied. `backgroundColor`to `null`if you pass it, it returns to the theme's default background color. `theme`only changes the icon/text color.

### Type

**Params**

```ts
type NavigationBarTheme = "light" | "dark";

interface SetNavigationBarOptions {
  withBackButton?: boolean;
  withHomeButton?: boolean;
  withTitle?: boolean;
  transparentBackground?: boolean;
  backgroundColor?: string | null; // `#RRGGBB` or `#RRGGBBAA`
  theme?: NavigationBarTheme;
}
```

**Response**

```ts
Promise<void>;
```

### Example code

```ts
import { NavigationBar } from "@apps-in-toss/web-framework";

await NavigationBar.setOptions({ theme: "dark" });

await NavigationBar.setOptions({
  withBackButton: false,
  withHomeButton: true,
  withTitle: true,
  transparentBackground: false,
  backgroundColor: "#3182F6",
});
```


---

# 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://developers-apps-in-toss.toss.im/documentation/api-and-sdk-en/sdk/domains-api/navigationbar/navigationbar.setoptions.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.