Appearance
Persona
Identity verification platform with inquiry workflows, document checks, and GDPR compliance.
| Detail | Value |
|---|---|
| Category | iGaming |
| Base URL | https://api.withpersona.com |
| Authentication | Bearer Token |
| Endpoints | 9 |
| Connector key | persona |
Using Persona in a workflow
- Go to Connections and click New Connection.
- Pick Persona 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 /api/v1/inquiries | Create inquiry |
GET /api/v1/inquiries/{id} | Get inquiry |
PATCH /api/v1/inquiries/{id} | Update inquiry |
POST /api/v1/inquiries/{id}/approve | Approve |
POST /api/v1/inquiries/{id}/decline | Decline |
DELETE /api/v1/inquiries/{id} | Redact (GDPR) |
GET /api/v1/verifications/{id} | Get verification |
GET /api/v1/accounts/{id} | Get account |
GET /api/v1/reports/{id} | Get report |
Each endpoint is documented in full below. Use the outline on the right to jump to one.
POST /api/v1/inquiries
Create inquiry
| Detail | Value |
|---|---|
| Operation ID | kyc.createInquiry |
| Method | POST |
| Path | /api/v1/inquiries |
Parameters
No parameters.
Request Body
| Field | Type |
|---|---|
data | object |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Persona connection from the Connection dropdown.
- In the Operation dropdown, select
kyc.createInquiry. - 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 Persona API reference.
GET /api/v1/inquiries/{id}
Get inquiry
| Detail | Value |
|---|---|
| Operation ID | kyc.getInquiry |
| Method | GET |
| Path | /api/v1/inquiries/{id} |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
id | path | string | Yes |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Persona connection from the Connection dropdown.
- In the Operation dropdown, select
kyc.getInquiry. - 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 Persona API reference.
PATCH /api/v1/inquiries/{id}
Update inquiry
| Detail | Value |
|---|---|
| Operation ID | kyc.updateInquiry |
| Method | PATCH |
| Path | /api/v1/inquiries/{id} |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
id | path | string | Yes |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Persona connection from the Connection dropdown.
- In the Operation dropdown, select
kyc.updateInquiry. - 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 Persona API reference.
POST /api/v1/inquiries/{id}/approve
Approve
| Detail | Value |
|---|---|
| Operation ID | kyc.approveInquiry |
| Method | POST |
| Path | /api/v1/inquiries/{id}/approve |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
id | path | string | Yes |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Persona connection from the Connection dropdown.
- In the Operation dropdown, select
kyc.approveInquiry. - 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 Persona API reference.
POST /api/v1/inquiries/{id}/decline
Decline
| Detail | Value |
|---|---|
| Operation ID | kyc.declineInquiry |
| Method | POST |
| Path | /api/v1/inquiries/{id}/decline |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
id | path | string | Yes |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Persona connection from the Connection dropdown.
- In the Operation dropdown, select
kyc.declineInquiry. - 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 Persona API reference.
DELETE /api/v1/inquiries/{id}
Redact (GDPR)
| Detail | Value |
|---|---|
| Operation ID | kyc.redactInquiry |
| Method | DELETE |
| Path | /api/v1/inquiries/{id} |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
id | path | string | Yes |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Persona connection from the Connection dropdown.
- In the Operation dropdown, select
kyc.redactInquiry. - 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 Persona API reference.
GET /api/v1/verifications/{id}
Get verification
| Detail | Value |
|---|---|
| Operation ID | kyc.getVerification |
| Method | GET |
| Path | /api/v1/verifications/{id} |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
id | path | string | Yes |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Persona connection from the Connection dropdown.
- In the Operation dropdown, select
kyc.getVerification. - 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 Persona API reference.
GET /api/v1/accounts/{id}
Get account
| Detail | Value |
|---|---|
| Operation ID | kyc.getAccount |
| Method | GET |
| Path | /api/v1/accounts/{id} |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
id | path | string | Yes |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Persona connection from the Connection dropdown.
- In the Operation dropdown, select
kyc.getAccount. - 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 Persona API reference.
GET /api/v1/reports/{id}
Get report
| Detail | Value |
|---|---|
| Operation ID | kyc.getReport |
| Method | GET |
| Path | /api/v1/reports/{id} |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
id | path | string | Yes |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Persona connection from the Connection dropdown.
- In the Operation dropdown, select
kyc.getReport. - 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 Persona API reference.