> ## Documentation Index
> Fetch the complete documentation index at: https://developer.z-api.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Confirm device transfer

> Finalizes the WhatsApp transfer from the phone to the instance after confirmation on the device

## Overview

Method used to finalize the WhatsApp transfer from the phone to the instance. It should be used after the [Confirm code](/mobile/confirm-code) endpoint returns `deviceConfirm: true` in the response.

<Warning>
  **Confirm the transfer on the device before making the request.**

  When receiving `deviceConfirm: true`, WhatsApp will display a notification on the phone where it is registered asking to confirm the transfer. **Only after accepting this confirmation on the device** should you call this endpoint. Otherwise, the connection will not be transferred to the instance.
</Warning>

***

## Expected flow

1. The **Confirm code** endpoint returns `"deviceConfirm": true`
2. The user **confirms the transfer on the phone** where WhatsApp is registered
3. After confirming on the device, call this endpoint
4. The WhatsApp connection is transferred from the phone to the instance

***

## Attributes

### Header

<ParamField path="instanceId" type="string" required>
  Your instance ID. Available in the Z-API panel under **Instances**.
</ParamField>

<ParamField path="token" type="string" required>
  Your Z-API instance token.
</ParamField>

***

## Response

### 200

<ResponseField name="success" type="boolean">
  Returns true if the transfer has been successfully confirmed and the instance is connected.
</ResponseField>

```json theme={"theme":{"light":"github-light","dark":"poimandres"}}
{
  "success": true
}
```

### 400

Invalid request. Check that the confirmation on the device was completed before calling this endpoint.

### 405

In this case, make sure you are correctly sending the method specification, i.e. verify that you sent POST or GET as specified at the beginning of this topic.

### 415

If you receive a 415 error, make sure to add the "Content-Type" of the object you are sending in the request headers, in most cases "application/json".