---
title: "Verify OTP V2"
method: POST
path: "/v2/otp/verify"
tags: ["SMS OTP"]
---

# Verify OTP V2

`POST /v2/otp/verify`

SMS OTP version change is by introducing a new API version release.<br>

Version changes usually need to be applied immediately to the latest version, in order to get a better API usage experience than the previous version.<br>

The benefits you get if you use a newer version are as follows.
- Decreasing processing time in API Request and Response
- Improve feature in SMS: Blocking Request, Spam Check, Sequential Phone Number, and Blocked Numbers
- Increase RPS in SMS (before 30rps to 50rps)
- Better developer environment to support future developments
- Improve logging and monitoring on our side
- Improved dependencies and improved service stability<br>

This method helps you to verify one-time password to destination number<br>

## Headers

- `App-ID` string, required
- `API-Key` string, required

## Request body

- VerifyOtp
  - `msisdn` string, required — This value is destination number. You need to include international prefix number.
  - `otp` string, required — Code received by destination number.
  - `challenge` string — This value is a category. You can verify OTP based on the same challenge.

## Response `200`

Successful Response

- ResponseVerifyOTP
  - `message` string, required — Message

## Other responses

- `400` — Bad Request
- `401` — Unauthorized
- `404` — Not Found
- `422` — Unprocessable Entity
- `500` — Internal Server Error

---

[API](https://skmtc.dev/verihubs/apis/sms-api-documentation.md) · [All operations](https://skmtc.dev/verihubs/apis/sms-api-documentation/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/verihubs/sms-api-documentation/revisions/5fa885d38adc/schema)