# Otp Confirm

**Endpoint**

 `POST/v2/auth/otp/confirm`

**Link**

{% embed url="<https://stagep.tst-apidmndelss.com/openapi/v2.html#/operations/Auth_OtpConfirm>" %}

### **Request**

#### **Headers**

| Key             | Value              | Required |
| --------------- | ------------------ | -------- |
| `Authorization` | `Bearer <JWT>`     | Yes      |
| `Content-Type`  | `application/json` | Yes      |
| `Accept`        | `application/json` | Yes      |

#### **Request Body (JSON)**

| Field      | Type     | Description                                      | Required | Example    |
| ---------- | -------- | ------------------------------------------------ | -------- | ---------- |
| **`code`** | `string` | **OTP code** (e.g., from SMS/authenticator app). | Yes      | `"123456"` |

**Example Request Body:**

json

```
{
  "code": "123456"
}
```

***

### **Response (200 OK)**

Returns a success flag indicating OTP verification status.

#### **Response Fields**

| Field         | Type      | Description                                | Example |
| ------------- | --------- | ------------------------------------------ | ------- |
| **`success`** | `boolean` | `true` if OTP is valid, `false` otherwise. | `true`  |

**Example Response:**

json

```
{
  "success": true
}
```

### **Error Responses**

1. **Invalid OTP**:

   json

   ```
   {
     "success": false,
     "error": "Invalid OTP code"
   }
   ```
2. **Expired OTP**:

   json

   ```
   {
     "success": false,
     "error": "OTP code expired"
   }
   ```
3. **Missing Authorization**:

   json

   ```
   {
     "error": "Unauthorized"
   }
   ```

***

### **Notes**

* **Token Requirement**: Requires a valid JWT from the initial login attempt (provided in `Authorization` header).
* **OTP Lifetime**: Typically valid for 2-5 minutes (depends on system configuration).
* **Success Behavior**:
  * If `success: true`, the user is fully authenticated.
  * The `accessToken` from the initial login becomes active.

### Examples

**Real request**&#x20;

`{`
\
`"code": "951212"`
\
`}`

**Real response**&#x20;

200 OK

```
{  "success": true}
```


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.delos.financial/authentication/otp-confirm.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.