# Pistiik Identity Verification API (`pistiik/pistiik-identity-verification`) Actor

Verify user identities via hosted document and biometric checks. Create verification sessions and retrieve verified results through a simple HTTP API.

- **URL**: https://apify.com/pistiik/pistiik-identity-verification.md
- **Developed by:** [Pistiik OÜ](https://apify.com/pistiik) (community)
- **Categories:** Integrations, AI, Agents
- **Stats:** 1 total users, 0 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1,350.00 / 1,000 "verification session created"s

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.

Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Pistiik Identity Verification API

Verify that the people you deal with online are real — and who they claim to be. Pistiik provides hosted document and biometric identity verification through a simple API: create a verification session, send your user a link, and fetch the verified result. No SDK integration, no compliance infrastructure to build.

Brought to you by [Pistiik](https://pistiik.com), the verification broker.

### How it works

1. **Create a session** — call the API with an optional `refId` (your own reference) and get back a `verificationUrl`.
2. **Send your user the link** — they complete the verification in their browser or phone (document capture, selfie, liveness).
3. **Fetch the result** — poll `GET /verifications/:refId` (or check later) to get the status and the extracted, verified document data.

### Verification flows

| Flow | Description |
|------|-------------|
| `document` | Full document verification: ID capture, data extraction, tampering checks. |
| `humanity` | Liveness check — confirms the person is a real human. |
| `name-check` | Name authenticity — confirms the given name matches a verified identity document. |

### Using the API (Standby mode)

The actor runs as an always-on HTTP API. Authenticate with your Apify API token.

Base URL:

```
https://pistiik--pistiik-identity-verification.apify.actor
```

#### Create a verification session

```bash
curl -X POST "https://pistiik--pistiik-identity-verification.apify.actor/sessions" \
  -H "Authorization: Bearer <YOUR_APIFY_TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{
    "flow": "document",
    "refId": "customer-42",
    "user": { "firstName": "Jane", "lastName": "Doe" },
    "redirectUrl": "https://example.com/verification-done",
    "language": "en"
  }'
```

All fields are optional. If you omit `refId`, one is generated for you — keep it, you need it to fetch the result.

Response `201`:

```json
{
  "refId": "customer-42",
  "verificationUrl": "https://…",
  "expiresAt": "2026-08-09T12:34:56.000Z"
}
```

The `verificationUrl` is valid for 30 minutes. Creating a new session for the same `refId` issues a fresh link.

#### Get a verification result

```bash
curl "https://pistiik--pistiik-identity-verification.apify.actor/verifications/customer-42" \
  -H "Authorization: Bearer <YOUR_APIFY_TOKEN>"
```

Response `200`:

```json
{
  "refId": "customer-42",
  "status": "verified",
  "createdAt": "2026-08-09T12:00:00.000Z",
  "updatedAt": "2026-08-09T12:05:00.000Z",
  "documents": [
    {
      "firstName": "JANE",
      "lastName": "DOE",
      "dateOfBirth": "1990-01-01",
      "gender": "F",
      "idNumber": "AB1234567",
      "dateOfIssue": "2020-01-01",
      "dateOfExpiration": "2030-01-01",
      "type": "PASSPORT",
      "faceMatchLevel": 5,
      "checks": {
        "digitalCopyDetection": "passed",
        "facePhotoTampering": "passed",
        "textTampering": "passed"
      }
    }
  ],
  "metadata": { "ipAddress": "203.0.113.7" }
}
```

#### Statuses

| Status | Meaning |
|--------|---------|
| `open` | The session was created but the user has not started yet. |
| `in_progress` | The user has started but not finished verification. |
| `processing` | Verification is being reviewed. |
| `verified` | All checks passed — you can proceed. |
| `flagged` | Verification failed or requires attention (document mismatch or screening hit). |

### Using the actor with runs

You can also run the actor normally with JSON input — useful for one-off checks or platform integrations (Zapier, Make, Apify schedules):

```json
{ "action": "createSession", "flow": "document", "redirectUrl": "https://example.com/done" }
```

```json
{ "action": "getVerification", "refId": "customer-42" }
```

The result is stored in the run's `OUTPUT` record and default dataset.

### Errors

| HTTP | Code | Meaning |
|------|------|---------|
| 400 | `INVALID_REQUEST` | A field is missing or malformed. |
| 404 | `NOT_FOUND` | No verification exists for this `refId`. |
| 500 | `CONFIGURATION_ERROR` | Service misconfiguration — contact support. |
| 502 | `UPSTREAM_UNAVAILABLE` | Temporary outage — retry with backoff. |

### Support

Questions or custom verification flows? Reach us at [pistiik.com](https://pistiik.com).

# Actor input Schema

## `action` (type: `string`):

Operation to perform.

## `refId` (type: `string`):

Your unique reference for this verification. Required for getVerification; auto-generated for createSession when omitted.

## `flow` (type: `string`):

Which verification flow to run (createSession only).

## `user` (type: `object`):

Optional person details: { "firstName", "lastName", "dateOfBirth" (YYYY-MM-DD), "gender" }. Recommended for name authenticity checks.

## `redirectUrl` (type: `string`):

Where the user is sent after completing verification (createSession only).

## `language` (type: `string`):

Two-letter UI language code for the hosted verification page.

## Actor input object example

```json
{
  "action": "createSession",
  "flow": "document",
  "user": {
    "firstName": "",
    "lastName": ""
  },
  "language": "en"
}
```

# Actor output Schema

## `results` (type: `string`):

The verification result items: session link (createSession) or verification status with extracted document data (getVerification).

## `output` (type: `string`):

The single OUTPUT record of this run: { success, refId, verificationUrl, expiresAt } for createSession, or { success, refId, status, documents } for getVerification.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "user": {
        "firstName": "",
        "lastName": ""
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("pistiik/pistiik-identity-verification").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "user": {
        "firstName": "",
        "lastName": "",
    } }

# Run the Actor and wait for it to finish
run = client.actor("pistiik/pistiik-identity-verification").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "user": {
    "firstName": "",
    "lastName": ""
  }
}' |
apify call pistiik/pistiik-identity-verification --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,pistiik/pistiik-identity-verification"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/jFO6d6nGQrfzZeXH9/builds/w7Fl5epMWzLusqBLx/openapi.json