> For the complete documentation index, see [llms.txt](https://helpdocs.ycloud.com/help-center/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdocs.ycloud.com/help-center/integrations/channels/verify/verification-features/custom-otp.md).

# Custom OTP

If you already have a system for generating and verifying verification codes and wish to continue using them, you can send us your code and use our pre-approved message templates along with text and voice localization options.

**How to use custom codes?**\
To use your own generated verification codes, include them in the API call to the send verification request.

```javascript
{
"to": "+44868534958",
"channel": "SMS",
"code": "1234",
}
```

To ensure accurate and reliable user authentication, it is recommended to submit the user-provided verification code using the Verification Code API. This method not only allows you to monitor the success rate of verifications but also provides us with valuable information about the stability of global SMS routes. By leveraging this API, you can provide your users with a seamless and secure authentication process.


---

# 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 dynamically by asking a question.

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

```
GET https://helpdocs.ycloud.com/help-center/integrations/channels/verify/verification-features/custom-otp.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.