> For the complete documentation index, see [llms.txt](https://docs.zama.org/protocol/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zama.org/protocol/sdk/api-references/react/useunwrap.md).

# useUnwrap

Low-level mutation hook that requests an unwrap for a specific amount.

Low-level mutation hook that requests an unwrap for a specific amount. You must finalize manually with [`useFinalizeUnwrap`](/protocol/sdk/api-references/react/usefinalizeunwrap.md).

{% hint style="info" %}
Most apps should use [`useUnshield`](/protocol/sdk/api-references/react/useunshield.md) instead, which orchestrates both steps (unwrap + finalize) in a single call.
{% endhint %}

## Import

```ts
import { useUnwrap } from "@zama-fhe/react-sdk";
```

## Usage

{% tabs %}
{% tab title="UnwrapButton.tsx" %}

```tsx
import { useUnwrap, useFinalizeUnwrap } from "@zama-fhe/react-sdk";

function UnwrapButton() {
  const { mutateAsync: unwrap, isPending } = useUnwrap("0xWrapper");
  const { mutateAsync: finalize } = useFinalizeUnwrap("0xWrapper");

  const handleUnwrap = async () => {
    // `unwrap` returns the `unwrapRequestId` directly -- no manual event decoding.
    const result = await unwrap({ amount: 500n });
    console.log("Unwrap requested:", result.txHash);
    await finalize(result);
  };

  return (
    <button onClick={handleUnwrap} disabled={isPending}>
      {isPending ? "Unwrapping..." : "Unwrap 500"}
    </button>
  );
}
```

{% endtab %}
{% endtabs %}

## Parameters

### address

`Address`

Address of the confidential wrapper contract. Passed positionally as the first argument.

```tsx
const { mutateAsync: unwrap } = useUnwrap("0xWrapper");
```

## Mutation variables

### amount

`bigint`

The amount of tokens to unwrap.

```tsx
await unwrap({ amount: 1000n });
```

## Return Type

The mutation resolves with an `UnwrapResult` -- `{ txHash: Hex, receipt: TransactionReceipt, unwrapRequestId: EncryptedValue }`. Pass the result straight to [`useFinalizeUnwrap`](/protocol/sdk/api-references/react/usefinalizeunwrap.md); its `unwrapRequestId` is decoded for you, so there's no need to parse the `UnwrapRequested` event yourself.

## Related

* [`useFinalizeUnwrap`](/protocol/sdk/api-references/react/usefinalizeunwrap.md) -- finalize the unwrap with a decryption proof
* [`useUnwrapAll`](/protocol/sdk/api-references/react/useunwrapall.md) -- unwrap the full balance
* [`useUnshield`](/protocol/sdk/api-references/react/useunshield.md) -- high-level hook that handles both steps


---

# 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.zama.org/protocol/sdk/api-references/react/useunwrap.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.