Appearance
Shufti Pro
KYC/AML identity verification for iGaming with face, document, and address checks.
| Detail | Value |
|---|---|
| Category | iGaming |
| Base URL | https://api.shuftipro.com |
| Authentication | Basic Auth |
| Endpoints | 7 |
| Connector key | shuftipro |
Using Shufti Pro in a workflow
- Go to Connections and click New Connection.
- Pick Shufti Pro from the marketplace.
- Enter your credentials (see Authentication above for what's expected).
- In a workflow, drop an API Call node and select this connection.
- Pick the operation you need from the Operation dropdown — the full list is below.
Available endpoints
| Endpoint | Summary |
|---|---|
POST / | Submit verification request |
POST /status | Get verification status |
POST /delete | Delete verification data (GDPR) |
POST /access_token | Generate temp access token |
POST /kyb | Know Your Business verification |
POST /aml | AML background checks |
POST /questionnaire | Questionnaire verification |
Each endpoint is documented in full below. Use the outline on the right to jump to one.
POST /
Submit verification request
| Detail | Value |
|---|---|
| Operation ID | kyc.submitVerification |
| Method | POST |
| Path | / |
Parameters
No parameters.
Request Body
| Field | Type |
|---|---|
reference | string |
callback_url | string |
face | object |
document | object |
address | object |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Shufti Pro connection from the Connection dropdown.
- In the Operation dropdown, select
kyc.submitVerification. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked — fill them or the call will fail at runtime.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Shufti Pro API reference.
POST /status
Get verification status
| Detail | Value |
|---|---|
| Operation ID | kyc.getVerificationStatus |
| Method | POST |
| Path | /status |
Parameters
No parameters.
Request Body
| Field | Type |
|---|---|
reference | string |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Shufti Pro connection from the Connection dropdown.
- In the Operation dropdown, select
kyc.getVerificationStatus. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked — fill them or the call will fail at runtime.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Shufti Pro API reference.
POST /delete
Delete verification data (GDPR)
| Detail | Value |
|---|---|
| Operation ID | kyc.deleteVerification |
| Method | POST |
| Path | /delete |
Parameters
No parameters.
Request Body
| Field | Type |
|---|---|
reference | string |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Shufti Pro connection from the Connection dropdown.
- In the Operation dropdown, select
kyc.deleteVerification. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked — fill them or the call will fail at runtime.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Shufti Pro API reference.
POST /access_token
Generate temp access token
| Detail | Value |
|---|---|
| Operation ID | kyc.generateAccessToken |
| Method | POST |
| Path | /access_token |
Parameters
No parameters.
Request Body
| Field | Type |
|---|---|
reference | string |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Shufti Pro connection from the Connection dropdown.
- In the Operation dropdown, select
kyc.generateAccessToken. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked — fill them or the call will fail at runtime.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Shufti Pro API reference.
POST /kyb
Know Your Business verification
| Detail | Value |
|---|---|
| Operation ID | kyc.kybVerification |
| Method | POST |
| Path | /kyb |
Parameters
No parameters.
Request Body
| Field | Type |
|---|---|
reference | string |
callback_url | string |
company_name | string |
registration_number | string |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Shufti Pro connection from the Connection dropdown.
- In the Operation dropdown, select
kyc.kybVerification. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked — fill them or the call will fail at runtime.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Shufti Pro API reference.
POST /aml
AML background checks
| Detail | Value |
|---|---|
| Operation ID | kyc.amlCheck |
| Method | POST |
| Path | /aml |
Parameters
No parameters.
Request Body
| Field | Type |
|---|---|
reference | string |
callback_url | string |
name | object |
dob | string |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Shufti Pro connection from the Connection dropdown.
- In the Operation dropdown, select
kyc.amlCheck. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked — fill them or the call will fail at runtime.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Shufti Pro API reference.
POST /questionnaire
Questionnaire verification
| Detail | Value |
|---|---|
| Operation ID | kyc.questionnaire |
| Method | POST |
| Path | /questionnaire |
Parameters
No parameters.
Request Body
| Field | Type |
|---|---|
reference | string |
callback_url | string |
questionnaire | object |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Shufti Pro connection from the Connection dropdown.
- In the Operation dropdown, select
kyc.questionnaire. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked — fill them or the call will fail at runtime.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Shufti Pro API reference.