> 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/sdk/domains-api/navigationbar/navigationbar.setoptions.md).

# NavigationBar.setOptions

### 기능 설명

네비게이션 바의 뒤로가기·홈 버튼과 타이틀 표시 여부, 배경의 투명 여부와 색상, 아이콘·글자 테마를 바꿔요. 전달한 필드만 반영하고, 생략한 필드는 직전에 적용된 값을 유지해요. 처음 호출하기 전에는 미니앱 config의 `navigationBar` 설정을 사용해요.

`transparentBackground`가 `true`면 네비게이션 바가 콘텐츠 위에 겹치고 레이아웃 높이를 차지하지 않아요. 이때 `backgroundColor`는 적용되지 않아요. `backgroundColor`에 `null`을 넘기면 테마 기본 배경색으로 돌아가요. `theme`은 아이콘·글자 색만 바꿔요.

### 타입

**Params**

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

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

**Response**

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

### 예시 코드

```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/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.