Skip to main content

Endpoint

GET /v1/analyses/{analysisId}

Request

curl -X GET "http://client-omni-api.argosidentity.com/v1/analyses/{analysisId}?waitForReport=true&timeoutSeconds=120" \
  -H "x-api-key: your-api-key-here"

Query Parameters

ParameterTypeRequiredDefaultDescription
waitForReportbooleanfalseWait for report generation (long polling)
timeoutSecondsnumber120Max wait time in seconds (10–300)
When waitForReport is set to true, the request will hold the connection open until the report is generated or the timeoutSeconds threshold is reached. This is useful for synchronous workflows where you need the report immediately after analysis completes.

Response Structure

The analysis response has a fixed skeleton (top-level fields, risk assessment, system metadata, findings, etc.) that is always present regardless of your workflow configuration.
The extractedData and outputSchema sections are determined by your workflow’s output schema configuration. The fields inside them change depending on how you defined your output schema. The example below shows a KYB verification workflow — your results will have different fields based on your own schema.

Top-Level Fields

These fields are always present in every analysis response.
id
string
required
Unique analysis ID (analysis_ prefix)
profileId
string
required
Profile ID this analysis belongs to
folderId
string | null
required
Target folder ID (null for full-profile analysis)
engineId
string | null
required
Engine ID used (null when using default engine)
playbookId
string
required
Playbook ID used for the analysis (PB- prefix)
engine
object | null
required
Engine details (null when using default engine)
status
string
required
Analysis status: pending / processing / completed / failed
processingTimeMs
number
required
Processing time in milliseconds
verificationStatus
string
required
Final verification status: pending_review / approved / rejected
error
string | null
required
Error message (null on success)
options
object | null
Options passed when the analysis was requested
clientMetadata
object | null
Client metadata passed when the analysis was requested
primaryReportId
string | null
Primary report ID generated for this analysis (rpt_ prefix)
requestedAt
string
required
Analysis request time (ISO 8601)
completedAt
string | null
required
Analysis completion time (ISO 8601, null if not completed)
createdAt
string
required
Record creation time (ISO 8601)

riskAssessment — Risk Assessment

Final risk assessment computed by the AI agent after all verification steps.
FieldTypeDescription
riskLevelstringRisk level: low / medium / high
riskScorenumberRisk score (0–100, higher = riskier)
riskFactorsstring[]List of factors contributing to the risk level

systemMetadata — Execution Metadata

Internal execution information from the AI agent during analysis.
FieldTypeDescription
totalIterationsnumberTotal iterations performed by the agent
completedWorkIdsnumber[]IDs of successfully completed work items
workflowHistoryobject[]Execution summary for each work item

systemMetadata.workflowHistory[]

FieldTypeDescription
workIdnumberWork sequence number (starts at 1)
actionNamestringExecuted action function name
querystringQuery/instruction used by the agent
reasonstringAgent’s reasoning for the result
successbooleanWhether the work succeeded
iterationnumberIteration number when completed
timestampstringCompletion time (ISO 8601)

extractedData — Extracted Structured Data

This section is dynamic. The fields inside extractedData are determined by the output schema you defined in your workflow. The example below is from a KYB workflow with business registration verification — your fields will differ.
The AI extracts data from documents and structures it according to your output schema. The following sub-sections are common patterns:

extractedData.review_result — Final Review Result

FieldTypeDescription
final_actionstringFinal action: approve / reject / manual_review
final_risk_levelstringFinal risk level: low / medium / high
final_action_reasonstringReasoning for the final action
final_risk_level_reasonstringReasoning for the final risk level

extractedData.extracted_values — Raw Extracted Values

Values extracted directly from submitted documents. The fields depend on your output schema definition. Example (KYB with business registration):
FieldTypeDescription
brc_business_namestringCompany name from business registration certificate
brc_business_registration_numberstringBusiness registration number
brc_corporate_registration_numberstringCorporate registration number
brc_representative_namestringRepresentative name
brc_addressstringBusiness address
brc_opening_datestringOpening date
brc_issue_datestringIssue date

extractedData.category_judgements — Verification Judgements

Per-category verification results with pass/fail status and reasoning.
FieldTypeDescription
{field}_check_resultstringCheck result: pass / fail / unverifiable / needs_review
{field}_check_reasonstringReasoning for the check result
overall_consistency_resultstringOverall consistency: pass / needs_review / fail
overall_consistency_reasonstringReasoning for overall consistency

extractedData.document_validations — Document Validity

FieldTypeDescription
{document}_is_validbooleanWhether the document is valid
{document}_is_valid_reasonstringReasoning for validity check

outputSchema — Enriched Output Schema

Contains the same data as extractedData, structured as your workflow’s JSON Schema with actual values filled in. Use extractedData as the canonical field.

Common fields in outputSchema.properties

FieldTypeDescription
request_idstringRequest identifier (same as profile ID)
policy_flagsstring[]Policy violation/caution flags
review_resultobjectFinal review result
extracted_valuesobjectRaw extracted values from documents
category_judgementsobjectPer-category verification judgements
document_validationsobjectDocument validity results
recommended_next_stepsstring[]AI-recommended follow-up actions

extractionStatus — Field Extraction Status

Status map indicating whether each top-level output schema field was successfully extracted.
ValueMeaning
"extracted"Field was successfully extracted/generated
"missing"Field extraction failed (no document or information)

rawActionResults — Raw Action Results

Raw result data returned by each AI action. Keys are actionName.
FieldTypeDescription
answerstringAction result text (RAG response or LLM output)
workIdnumberWork sequence number
citationsCountnumberNumber of citation chunks used
verificationStatusstringVerification result: passed / needs_review / failed

agentAuditLog[] — Agent Audit Log

Detailed execution log of every step the AI agent performed. More granular than rawActionResults, includes MCP tool call details.
FieldTypeDescription
workIdnumberWork sequence number
actionNamestringAction name
categorystringAction category. Examples include Document Classification, Data Extraction, Format Validation, Status Validation, Data Consistency, Document Processing, and mcp (external tools). Actual values depend on the workflow policy.
querystringQuery or instruction sent by the agent
reasoningstringAgent’s reasoning (may be empty)
successbooleanWhether execution succeeded
iterationnumberIteration number
durationMsnumberExecution duration in milliseconds
executedAtstringExecution time (ISO 8601)
verificationStatus`stringnull`Per-step verification outcome when applicable (e.g., passed / needs_review / failed). May be omitted for steps that do not produce a pass/fail (such as some MCP-only actions).
targetItemIdsstring[]Item IDs referenced by this action
ragResponse`objectnull`RAG query result (if applicable)
mcpToolCalls`object[]null`MCP tool call details (if applicable)

agentAuditLog[].ragResponse

Present only for actions that performed RAG queries.
FieldTypeDescription
answerstringRAG-generated response text
citationsobject[]Citation chunks used in the response
chunksSearchednumberNumber of chunks searched
processingTimeMsnumberRAG processing time in milliseconds

agentAuditLog[].mcpToolCalls[]

Present only for actions that called MCP external tools (e.g., AML screening).
FieldTypeDescription
toolNamestringMCP tool name (e.g., search_individual)
engineCodestringEngine identifier for this tool (e.g., aml-search)
engineNamestringDisplay name of the engine (e.g., AML Search - Person)
paramsobjectTool call parameters
successbooleanWhether the call succeeded
startedAtstringCall start time (ISO 8601)
executionTimeMsnumberTool call duration in milliseconds
rawContentobjectRaw response data from the tool
fallbackToRagbooleanWhether RAG fallback was triggered on failure
selectionReasonstringAgent’s reason for selecting this tool

findings[] — Verification Findings

Sorted summary of each action’s result. Designed for UI display.
FieldTypeDescription
idstringFinding ID (af_ prefix)
categorystringCategory (same as action name)
resultstringResult: passed / warning / failed
detailsstringResult details (may be truncated)
sortOrdernumberDisplay order

recommendations[] — Recommendations

System-generated follow-up action recommendations.
FieldTypeDescription
idstringRecommendation ID (ar_ prefix)
contentstringRecommendation content
prioritynumberPriority (lower = higher priority)
sortOrdernumberDisplay order

targetItems[] — Target Items

Items referenced in this analysis.
FieldTypeDescription
itemIdstringItem ID (item_ prefix)
namestringItem name
typestringItem type: file / text / json
sourceRef`stringnull`Source reference info

Status Enums

ValueDescription
pendingAwaiting analysis
processingAnalysis in progress
completedAnalysis complete
failedAnalysis failed