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
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
Handling Different Statuses
Pending
When a verification is in thepending 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 theverified 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 thefailed 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 iscancelled:
- The verification request was stopped prematurely
- This typically happens through admin action or system decision
Expired
When a verification hasexpired:
- The verification request has exceeded its time limit
- You should prompt the user to start a new verification process