> ## Documentation Index
> Fetch the complete documentation index at: https://docs.scute.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Tracking Verification Status

# Tracking Verification Status

After creating a verification request, it's important to track its status to understand where it is in the verification lifecycle. This guide explains the possible statuses and how to check them.

## Verification Request Statuses

A verification request can have one of the following statuses:

| Status      | Description                                                                        |
| ----------- | ---------------------------------------------------------------------------------- |
| `pending`   | The verification request has been created but not yet completed by the user        |
| `verified`  | The user has successfully completed the verification process                       |
| `failed`    | The verification attempt was unsuccessful (e.g., wrong OTP entered too many times) |
| `cancelled` | The verification request was cancelled by the system or an administrator           |
| `expired`   | The verification request has expired (time limit exceeded)                         |

## Checking Verification Status

You can check the status of a verification request using our API.

### API Endpoint

```
GET https://api.scute.io/v1/verify/:app_id/verifications/:id
```

#### Request Parameters

| Parameter | Type   | Description                                 |
| --------- | ------ | ------------------------------------------- |
| `app_id`  | string | Your Scute application ID (in the URL path) |
| `id`      | string | The ID of the verification request to check |

#### Example Request

```javascript theme={null}
// Using fetch
const response = await fetch('https://api.scute.io/v1/verify/your-app-id/verifications/verification-id', {
  method: 'GET',
  headers: {
    'Authorization': 'Bearer YOUR_SCUTE_API_KEY'
  }
});

const data = await response.json();
console.log(data.status); // Will show one of: pending, verified, failed, cancelled, expired
```

## Handling Different Statuses

### Pending

When a verification is in the `pending` status:

* The user has not yet completed the verification process
* You may want to display a message to the user or send a reminder

### Verified

When a verification reaches the `verified` status:

* The user has successfully completed verification
* Your application can proceed with the protected action
* This is the successful end state of the verification flow

### Failed

When a verification has the `failed` status:

* The verification attempt was unsuccessful
* You may want to prompt the user to try again with a new verification request

### Cancelled

When a verification is `cancelled`:

* The verification request was stopped prematurely
* This typically happens through admin action or system decision

### Expired

When a verification has `expired`:

* The verification request has exceeded its time limit
* You should prompt the user to start a new verification process