---
title: "Verify MFA token"
method: POST
path: "/api/relay/rest/mfa/{mfa_request_id}/verify"
tags: ["Multi-Factor Authentication"]
---

# Verify MFA token

`POST /api/relay/rest/mfa/{mfa_request_id}/verify`

Checks a submitted code against the multi-factor authentication request identified in the path. Use it after requesting delivery by SMS or voice call and before granting the user access. The request's configured lifetime and attempt limit determine whether further verification is allowed.

#### Permissions

The API token used to authenticate must have the following scope(s) enabled to make a successful request: _Management_.

[Learn more about API scopes](/docs/platform/your-signalwire-api-space).

## Path parameters

- `mfa_request_id` string, uuid, required — Universal Unique Identifier.

## Request body

- MfaVerifyRequest — MFA verification request model.
  - `token` string, required — The token to verify.

## Response `200`

The request has succeeded.

- MfaVerifyResponse — MFA verification response model.
  - `success` boolean, required — Whether the token was successfully verified by the API. When `max_attempts` are reached or the request is no longer valid, the endpoint will return a `404 Not Found`.

## Other responses

- `401` — Access is unauthorized.
- `422` — The request failed validation. See errors for details.
- `500` — An internal server error occurred.

---

[API](https://skmtc.dev/signalwire/apis/signalwire-rest-api.md) · [All operations](https://skmtc.dev/signalwire/apis/signalwire-rest-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/signalwire/signalwire-rest-api/revisions/792d5b8e2970/schema)
