Deepvue Workflows API Docs - Verification Journeys, Runs & Reports
Trigger multi-step verification journeys with one API call. Start runs, poll to completion, resolve human reviews, and pull signed verification reports.
Ship verification journeys, not integrations
Deepvue Workflows turns a multi-step verification journey into a single API call. You compose the journey once in the dashboard, then start runs, follow them to a verdict, and read the report.
Quickstart
Start your first run and read its result in under 5 minutes.
API Reference
Explore all 9 endpoints across workflows, runs, and reviews.
Deepvue Dashboard
Compose workflows, manage credentials, and monitor usage.
Authentication
Authenticate every request with your client ID and API key.
Errors
Understand run error codes and which failures are worth a retry.
Webhooks
Get notified when a run finishes instead of polling for it.
Explore by capability
Workflows
Discover the journeys available to you and every check they can run.
Runs
Start a run, follow six statuses, and know exactly when it is terminal.
Reviews
Work the human queue and record a verdict that settles the run.
Reports
Render results in your own UI, or archive the signed PDF.
Conventions
Timestamps, absent versus null, the list envelope, and the error format.
Platform essentials
| Feature | Details |
|---|---|
| Base URL | https://api.deepvue.link |
| API version | v1 |
| Reference updated | August 2026 |
| Audience | Deepvue customers and partners, authenticated with a client ID and API key |
| Protocol | HTTPS required, REST conventions |
| Auth | client-id + x-api-key headers (details) |
| Timestamps | RFC 3339 UTC, for example 2026-07-30T09:14:02Z |
| List format | Fixed envelope with data, total, limit, offset |
| Run statuses | Six statuses that partition every run (details) |
| Error handling | code, check, and message on a failed run (details) |
Two things that surprise most integrators
completed means the workflow finished, not that every check passed.
Inspect checks[].status to learn the verification outcome.
A run can finish every screen and still be owed a human verdict.
status says how far a run got; decision says where a human verdict on it stands.
The two are independent axes and are AND-ed when you filter.