How Human Plugin works

Deploy it once, then call it from your back-end.

Markdown

1. Deploy Human Plugin in your infrastructure, with your access key and a PostgreSQL database. From then on, you are connected to Unico's network. See Run Human Plugin in your infrastructure.
2. Create a process from your back-end with one of the flows, your clientId, a unique correlationId and the person's document in credential.
3. Read the result: the Human Token tells you who the person is, and the intelligence tells you what that person has done with you.

What every answer has

Field	Meaning
id	The process id. Use it for GET /v1/processes/{id}
state	PROCESS_STATE_CREATED, PROCESS_STATE_FINISHED or PROCESS_STATE_FAILED
data.humanToken	Who the person is. In a revalidation, data.humanTokenMatch
data.ndocs	The person's intelligence

Send the document in credential

The person's document goes only in credential. That is where Human Plugin keeps it in your infrastructure and counts it in the intelligence.

Good to know

• Human Plugin does not authenticate its callers. Keep it reachable only from your back-end: see Networking and security.
• There is no endpoint to list, search or delete processes, and no webhook. A pending process is updated when you read it.

Next

1. Intelligence
2. Prerequisites and access
3. Quickstart