---
title: "Resend a token"
method: POST
path: "/v2/users/{userId}/tokens"
tags: ["Tokens", "Users"]
---

# Resend a token

`POST /v2/users/{userId}/tokens`

Resend the specified token

The token to resend must already exist for the user

It will be revoked and a new one issued

## Path parameters

- `userId` string, uuid, required

## Request body

- ResendTokenRequest
  - `tokenType` 'INVITE_MFA_USER' | 'MFA_REGISTRATION', required — The type of the token to resend
  - `verificationCode` string, nullable — <p>Optional property that MUST be suppied when manually verifying a user</p> <p>The user's smsNumber is registered via a separate endpoint and an OTP sent to them</p>

## Response `204`

request completed okay

## Other responses

- `400` — Invalid request. See Error message payload for details of failure
- `401` — Invalid access token. May be expired or invalid
- `403` — The authentication does not have permissions to access the resource This usually occurs when there is a valid authentication instance (client or user) but they do not have the required permissions

---

[API](https://skmtc.net/velopaymentsapi/apis/velo-payments-apis.md) · [All operations](https://skmtc.net/velopaymentsapi/apis/velo-payments-apis/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/velopaymentsapi/velo-payments-apis/revisions/05c3f09fc50a/schema)
