Veriff

Identity verification with document scanning, biometric checks, and PEP/sanctions screening.

Detail	Value
Category	iGaming
Base URL	https://stationapi.veriff.com
Authentication	HMAC-SHA256
Endpoints	8
Connector key	veriff

Using Veriff in a workflow

1. Go to Connections and click New Connection.
2. Pick Veriff from the marketplace.
3. Enter your credentials (see Authentication above for what's expected).
4. In a workflow, drop an API Call node and select this connection.
5. Pick the operation you need from the Operation dropdown. The full list is below.

Available endpoints

Endpoint	Summary
POST /v1/sessions	Create verification session
PATCH /v1/sessions/{sessionId}	Submit session for verification
DELETE /v1/sessions/{sessionId}	Delete session
POST /v1/sessions/{sessionId}/media	Upload documents
GET /v1/sessions/{sessionId}/decision	Get verification decision
GET /v1/sessions/{sessionId}/attempts	Get attempt IDs
GET /v1/sessions/{sessionId}/person	Get verified person data
GET /v1/sessions/{sessionId}/watchlist-screening	PEP/sanctions results

Each endpoint is documented in full below. Use the outline on the right to jump to one.

POST /v1/sessions

Create verification session

Detail	Value
Operation ID	kyc.createSession
Method	POST
Path	/v1/sessions

Parameters

No parameters.

Request Body

Field	Type
verification	object

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Veriff connection from the Connection dropdown.
3. In the Operation dropdown, select kyc.createSession.
4. 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 Veriff API reference.

PATCH /v1/sessions/{sessionId}

Submit session for verification

Detail	Value
Operation ID	kyc.submitSession
Method	PATCH
Path	/v1/sessions/{sessionId}

Parameters

Name	Location	Type	Required
sessionId	path	string	Yes

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Veriff connection from the Connection dropdown.
3. In the Operation dropdown, select kyc.submitSession.
4. 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 Veriff API reference.

DELETE /v1/sessions/{sessionId}

Delete session

Detail	Value
Operation ID	kyc.deleteSession
Method	DELETE
Path	/v1/sessions/{sessionId}

Parameters

Name	Location	Type	Required
sessionId	path	string	Yes

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Veriff connection from the Connection dropdown.
3. In the Operation dropdown, select kyc.deleteSession.
4. 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 Veriff API reference.

POST /v1/sessions/{sessionId}/media

Upload documents

Detail	Value
Operation ID	kyc.uploadDocuments
Method	POST
Path	/v1/sessions/{sessionId}/media

Parameters

Name	Location	Type	Required
sessionId	path	string	Yes

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Veriff connection from the Connection dropdown.
3. In the Operation dropdown, select kyc.uploadDocuments.
4. 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 Veriff API reference.

GET /v1/sessions/{sessionId}/decision

Get verification decision

Detail	Value
Operation ID	kyc.getDecision
Method	GET
Path	/v1/sessions/{sessionId}/decision

Parameters

Name	Location	Type	Required
sessionId	path	string	Yes

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Veriff connection from the Connection dropdown.
3. In the Operation dropdown, select kyc.getDecision.
4. 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 Veriff API reference.

GET /v1/sessions/{sessionId}/attempts

Get attempt IDs

Detail	Value
Operation ID	kyc.getAttempts
Method	GET
Path	/v1/sessions/{sessionId}/attempts

Parameters

Name	Location	Type	Required
sessionId	path	string	Yes

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Veriff connection from the Connection dropdown.
3. In the Operation dropdown, select kyc.getAttempts.
4. 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 Veriff API reference.

GET /v1/sessions/{sessionId}/person

Get verified person data

Detail	Value
Operation ID	kyc.getVerifiedPerson
Method	GET
Path	/v1/sessions/{sessionId}/person

Parameters

Name	Location	Type	Required
sessionId	path	string	Yes

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Veriff connection from the Connection dropdown.
3. In the Operation dropdown, select kyc.getVerifiedPerson.
4. 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 Veriff API reference.

GET /v1/sessions/{sessionId}/watchlist-screening

PEP/sanctions results

Detail	Value
Operation ID	kyc.getWatchlistScreening
Method	GET
Path	/v1/sessions/{sessionId}/watchlist-screening

Parameters

Name	Location	Type	Required
sessionId	path	string	Yes

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Veriff connection from the Connection dropdown.
3. In the Operation dropdown, select kyc.getWatchlistScreening.
4. 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 Veriff API reference.