---
title: "Perform a verification"
method: POST
path: "/2step"
---

# Perform a verification

`POST /2step`

You can send a Two Factor Authentication very easily just by specifying the recipient, the type of the message and the method that the verification will be…

## Headers

- `Content-Type` string, required
- `Authorization` string, required

## Request body

- object
  - `method` string, required — The method which will be used to send the 2step verification. Values: "sms", "voice".
  - `type` string, required — The type of the message. Value: "code".
  - `recipient` string, required — The recipient that will receive the 2step verification. For sms method format with a '+' and country code e.g., +306948530920 (E.164 format).
  - `template` string, required — The template of the message. It must contain a @@pin that will be replaced by the generated code.
  - `arguments` string — If the template is for example '@@name your code is @@pin' and the argument has a property name: 'Nick' the message will be 'Nick your code is 4232'. Note that if the template contains a @@ placeholder and a value is not present in the arguments property it will stay as is.
  - `templateCountry` string — Country in [ISO-3166-1](https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#Officially_assigned_code_elements) alpha 2 format (GR, US etc.). The country to use in order to select a translated template (if defined in Routee web interface)
  - `originator` string — The senderId that will be set when sending the SMS
  - `lifetimeInSeconds` integer — How many seconds this verification will remain active. After that time passes the verification status will be Expired.
  - `maxRetries` integer — Defines the number of times the user can re-confirm the verification before the verification changes its state to Failed.
  - `digits` integer — The number of digits of the generated random numeric code.
  - `restrictions` object — [OPTIONAL] Provide the registered Content Template ID and Principal Entity ID to ensure the message is not rejected by TRAI regulations.
    - `india` object — [OPTIONAL] If present, template and entity ID must be a number between 12 and 19 digits
      - `templateId` integer — [OPTIONAL], If present, template ID must be a number between 12 and 19 digits
      - `entityId` integer — [OPTIONAL], If present, entity ID must be a number between 12 and 19 digits

## Response `200`

200

- object
  - `trackingId` string
  - `status` string
  - `updatedAt` string
  - `maxRetries` integer
  - `expiresAt` string
  - `timesTried` integer

## Other responses

- `400` — 400

---

[API](https://skmtc.net/routee/apis/auth.md) · [All operations](https://skmtc.net/routee/apis/auth/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/routee/auth/revisions/5cef04e8f7d8/schema)