Pactvera API Integration Flow
This diagram maps the main Pactvera integration path: setup, create, attach, send, and track. Solid arrows are the happy path; dashed edges are optional lookups, edits, or cancellations. Click a node to open its API reference in a new tab.
How to read the diagram
| Lane | Role |
|---|---|
| Integration Partner | Your backend calls ChainIT APIs and receives webhooks (including after send). |
| ChainIT Platform | Orchestrates Pactvera requests, templates, and VDT creation. |
Main flow: List folders → create (template or manual) → get parties → attach → send.
Branches: Template lookups, edit/delete on draft attach, cancel from send, and utility reads (search, details, TouchAudit) sit beside the main path.
Webhooks: After send, ChainIT may emit VDT-created and task-completed events to your registered webhook URL.
Recipient outcomes and Pactvera status
After Send Pactvera, signers and form recipients complete their tasks in the Valitorium mobile app or PWA. ChainIT aggregates each recipient’s response and sets the Pactvera status accordingly:
| Recipient outcome | Pactvera status | When it applies |
|---|---|---|
| All recipients complete their assigned task | VALITORUM | Every party finished (submitted a form or signed a document). |
| Mixed — some accept/complete, some reject | PARTIALLY_REJECTED | e.g. half of recipients accept and half reject. |
| All recipients reject | REJECTED | Every party declined their task. |
These statuses appear on the diagram below Send Pactvera (dashed edges). Use Get Pactvera Details or your webhook payloads to read the current status in your integration.