VertexYDocs

Start Here

  • Platform overview
  • Public sandbox
  • Engineer quickstart
  • Analyst introduction
  • Administrator setup
  • Architecture

Integrate

  • Authentication
  • Assess transactions
  • Event ingestion
  • Signing and reliability
  • Submit feedback
  • Retries and idempotency
  • Go-live checklist

Use the Dashboard

  • Overview dashboard
  • Event Explorer
  • Graph Explorer
  • AI Copilot
  • Reviews
  • Policy
  • Threat Intel

Administer

  • Onboarding
  • Developer Settings
  • Team and access
  • Permissions and features
  • Audit Logs
  • Billing and plans

Reference

  • API reference
  • API introduction
  • Objects
  • Event types
  • Risk scores and reasons
  • Errors
  • Glossary
  • Node.js examples
  • Python examples

Updates and Help

  • Changelog
  • v1.0.0 release
  • Troubleshooting
  • Support
Already a customer? Sign in
VertexYDocs
Docs/Use the Dashboard
analyst

Reviews & Case Management

Create, investigate, and resolve review cases.

Reviewed 2026-08-13Product 1.1

Reviews attach analyst work to a stored risk assessment. They require an admin or analyst role and a plan with the reviews feature.

Create a review#

POST /reviews

json
{
  "assessmentId": "e7d3c2b1-a0f9-4e8d-b7c6-5a4f3e2d1c0b",
  "analystNote": "Checking device history after a velocity spike."
}

The response returns the review ID, linked assessment, open status, authenticated analyst identity, note, and timestamps. Clients do not send analystId or analystEmail.

Status lifecycle#

plaintext
open → in_review → escalated ─┐
                              ├→ confirmed_fraud
                              ├→ false_positive
                              ├→ closed
                              └→ resolved

open, in_review, and escalated are active. The other statuses are terminal and set closedAt.

Update a status with PATCH /reviews/status:

json
{
  "reviewId": "r1a2b3c4-d5e6-7890-abcd-ef1234567890",
  "status": "confirmed_fraud"
}

Find reviews#

  • GET /reviews?page=1&limit=20&status=open returns paginated data and meta; limit defaults to 20 and is capped at 100.
  • GET /reviews/:id returns one review plus assessment score, action, risk level, reason codes, and creation time.

Resolve the operational loop#

  1. Inspect the assessment and linked evidence.
  2. Record notes and move the review through its status.
  3. Set a terminal status when the verdict is known.
  4. Submit the matching outcome through Submit Feedback.

Use Graph Explorer for connected evidence and Risk Scores for decision semantics.

Was this page helpful?

Previous← AI CopilotNextPolicy →

On this page

Create a reviewStatus lifecycleFind reviewsResolve the operational loop