> For the complete documentation index, see [llms.txt](https://manual.personr.co/api-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://manual.personr.co/api-documentation/applicants/requesting-to-start-the-verification-process.md).
# Requesting to start the verification process
Once you've uploaded all required documents to an applicant, you can request to start the verification.
When all documents and selfie images have been uploaded, use this endpoint to confirm and start the verification process.
{% hint style="warning" %}
Note: You don't need to use this endpoint if you're verifying applicants using a verification link. Verification links submit applicants for processing automatically.
{% endhint %}
Make sure all required documents for your flow have been uploaded before confirming to start the verification process. If all of the documents haven't been uploaded, using this endpoint can be harmful and may affect the verification result.
If you've accidentally called this endpoint and haven't uploaded all required documents, you can either wait until the verification process has completed (likely failing), upload the additional docs and re-send the request call, or create a new applicant, upload all the docs and start the verification process again.
Via both API and Verification Link, an applicant has 5 "attempts" at verification before ending in a rejected status. At this point it is recommended to either manually review in the platform, or create a new applicant entry.
***
## Submit the applicant for processing
`POST` `/api-request-applicant-check`
Once all documents have been uploaded, start the verification process.
| Name | Value |
| ------------- | --------------------- |
| Content-Type | `multipart/form-data` |
| Authorization | `Bearer YOUR_TOKEN` |
**Body**
Name
Type
Description
applicantId
string
Unique applicantId generated on applicant creation (required)
#### Request
{% tabs %}
{% tab title="cURL" %}
```sh
curl --location 'https://enterprise.personr.co/api/1.1/wf/api-request-applicant-check' \
--header 'Authorization: Bearer YOUR_TOKEN' \
--form 'applicantId="4242424242424x424242424242424242"'
```
{% endtab %}
{% tab title="Node.js" %}
```javascript
var axios = require('axios');
var FormData = require('form-data');
var data = new FormData();
data.append('applicantId', '4242424242424x424242424242424242');
var config = {
method: 'post',
maxBodyLength: Infinity,
url: 'https://enterprise.personr.co/api/1.1/wf/api-request-applicant-check',
headers: {
'Authorization': 'Bearer YOUR_TOKEN',
...data.getHeaders()
},
data : data
};
axios(config)
.then(function (response) {
console.log(JSON.stringify(response.data));
})
.catch(function (error) {
console.log(error);
});
```
{% endtab %}
{% tab title="Javascript" %}
```javascript
var form = new FormData();
form.append("applicantId", "4242424242424x424242424242424242");
var settings = {
"url": "https://enterprise.personr.co/api/1.1/wf/api-request-applicant-check",
"method": "POST",
"timeout": 0,
"headers": {
"Authorization": "Bearer YOUR_TOKEN"
},
"processData": false,
"mimeType": "multipart/form-data",
"contentType": false,
"data": form
};
$.ajax(settings).done(function (response) {
console.log(response);
});
```
{% endtab %}
{% tab title="Ruby" %}
```ruby
require "uri"
require "net/http"
url = URI("https://enterprise.personr.co/api/1.1/wf/api-request-applicant-check")
https = Net::HTTP.new(url.host, url.port)
https.use_ssl = true
request = Net::HTTP::Post.new(url)
request["Authorization"] = "Bearer YOUR_TOKEN"
form_data = [['applicantId', '4242424242424x424242424242424242']]
request.set_form form_data, 'multipart/form-data'
response = https.request(request)
puts response.read_body
```
{% endtab %}
{% tab title="Python" %}
```python
import requests
url = "https://enterprise.personr.co/api/1.1/wf/api-request-applicant-check"
payload={'applicantId': '4242424242424x424242424242424242'}
files=[
]
headers = {
'Authorization': 'Bearer YOUR_TOKEN'
}
response = requests.request("POST", url, headers=headers, data=payload, files=files)
print(response.text)
```
{% endtab %}
{% endtabs %}
**Response**
{% tabs %}
{% tab title="200" %}
```json
{
"response": "success"
}
```
{% endtab %}
{% tab title="400" %}
```json
{
"statusCode": 400,
"message": "Error: incorrect applicantId provided"
}
```
{% endtab %}
{% endtabs %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://manual.personr.co/api-documentation/applicants/requesting-to-start-the-verification-process.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.