---
title: "Get Team Analysis"
method: GET
path: "/api/analysis/{team_key}/analyses/{source_psa}/{ticket_id}"
tags: ["analysis"]
---

# Get Team Analysis

`GET /api/analysis/{team_key}/analyses/{source_psa}/{ticket_id}`

## Request

- Base URL: `https://api.superit.ai` (the document declares no server; this is the origin it was published from)
- URL: `https://api.superit.ai/api/analysis/{team_key}/analyses/{source_psa}/{ticket_id}`
- Auth: HTTP bearer

Get single analysis by ticket ID.

## Path parameters

- `source_psa` string, required
- `ticket_id` string, required
- `team_key` string, required

## Response `200`

Successful Response

- AnalysisDetailResponse
  - `key` string, required
  - `source_psa` string, required
  - `source_ticket_id` string, required
  - `status` 'queued' | 'preparing' | 'triaging' | 'analysing' | 'failed' | 'skipped_deterministic' | 'skipped_triage' | 'cancelled' | 'analysed', required: Status of a ticket analysis through the pipeline.
  - `skip_reason` string, nullable
  - `analysed_at` string, date-time, nullable
  - `analysis_version` string, required
  - `analysis_data` TicketAnalysis: Complete structured analysis of an IT support ticket.
    - `ticketSpecification` 'service_request' | 'incident' | 'other', required: Whether a ticket is a service request, an incident, or other.
    - `category` 'access' | 'network' | 'performance' | 'printer' | 'file' | 'email' | 'hardware' | 'software' | 'security' | 'service_request' | 'other', required: Primary category for ticket.
    - `complexity` 'simple' | 'moderate' | 'complex', required: Ticket complexity assessment.
    - `oneSentenceSummary` string, required: Short plain-language summary of the ticket
    - `rootCause` RootCauseAnalysis: Analysis of what caused the issue or triggered the request.
      - `rootCauseCategory` 'user_error' | 'configuration_issue' | 'software_bug' | 'hardware_failure' | 'network_issue' | 'external_service' | 'capacity_exhaustion' | 'security_incident' | 'change_related' | 'environmental' | 'unknown', required: Category of root cause.
      - `rootCauseDetail` string, nullable: 1-2 sentence explanation of the root cause. Omit if insufficient information.
      - `contributingFactors` string[]: Other factors that contributed to the issue
      - `wasPreventable` boolean, nullable: Whether this could have been prevented. Omit if not determinable.
      - `preventionSuggestion` string, nullable: How to prevent recurrence, if preventable
    - `technologies` string[]: Key technologies and products involved, e.g. ['Microsoft 365', 'Azure AD', 'GlobalProtect VPN']
    - `capabilityAssessment` SuperITCapabilityAssessment, required: Assessment of how well SuperIT could handle this ticket autonomously today.
      - `verdict` 'fully_autonomous' | 'mostly_autonomous' | 'assisted_resolution' | 'triage_and_discovery' | 'human_required', required: Assessment of SuperIT's ability to handle a ticket.
      - `verdictRationale` string, required: 1-2 sentence explanation of why this verdict was chosen
      - `resolution` 'full' | 'partial' | 'unsure' | 'no': Whether SuperIT could resolve a ticket like this, given its toolkit.
      - `automation` 'workflow' | 'autonomous' | 'hitl_user' | 'hitl_engineer' | 'none': How much of the resolution SuperIT can automate.
      - `confidence` 'low' | 'medium' | 'high': Confidence in the resolution + automation assessment.
      - `capabilityGaps` CapabilityGap[]: Specific capabilities needed for SuperIT to achieve a higher autonomy verdict
        - `description` string, required: What capability is missing, e.g. 'Direct M365 password reset via Graph API'
        - `gapType` 'integration' | 'tool' | 'knowledge' | 'context' | 'permission', required: Type of capability gap.
        - `impact` 'blocking' | 'significant' | 'minor', required: Impact level of a capability gap.
        - `effort` 'trivial' | 'small' | 'medium' | 'large' | 'requires_research', required: Effort required to address a capability gap.
    - `knowledgeArtifacts` KnowledgeArtifactExtraction[]: Reusable knowledge extracted from this ticket
      - `artifactType` 'procedure' | 'troubleshooting' | 'known_issue' | 'workaround' | 'faq' | 'fact' | 'configuration' | 'policy' | 'warning' | 'glossary_term', required: Type of knowledge artifact extracted from analysis.
      - `scope` 'it_team' | 'client' | 'user', required: Scope/tier of a knowledge artifact.
      - `title` string, required: Short descriptive title
      - `content` string, required: The knowledge content — procedure steps, facts, or guidance
      - `reusability` string: Why this knowledge would help resolve a different future ticket with a similar but not identical situation. If you cannot articulate this clearly, do not include the artifact.
      - `tags` string[]: Searchable tags for categorisation, e.g. ['outlook', 'exchange', 'profile']
    - `actionableInsights` ActionableInsight[]: Actionable insights for the IT team or client
      - `insightType` 'sales_opportunity' | 'security_concern' | 'training_need' | 'process_improvement' | 'documentation_gap' | 'recurring_issue' | 'satisfaction_risk' | 'capacity_planning' | 'vendor_issue', required: Type of actionable insight.
      - `title` string, required: Short descriptive title
      - `content` string, required: Detailed description of the insight
      - `recommendedAction` string, required: Specific action to take to address this insight
      - `urgency` 'low' | 'medium' | 'high' | 'critical', required: Urgency level of an actionable insight.
      - `estimatedImpact` string: Who and how many are affected, e.g. '~15 users in sales dept', 'All devices on Windows 10'
      - `stakeholders` Stakeholder[], required: Who should see this insight
    - `workflowRecommendations` WorkflowRecommendation[]: New automation workflows worth building for this recurring, automatable class of ticket. Only when automation == workflow and the recommendation transfers to future similar tickets; empty otherwise.
      - `title` string, required: Short name for the proposed workflow, e.g. 'Restore shared-drive access after security-group re-scope'
      - `trigger` string, required: The class of ticket / condition this workflow should fire on — general, not this one ticket.
      - `outline` string, required: The steps the workflow would automate (a runbook sketch).
      - `reusability` string, required: Why building this resolves DIFFERENT future tickets with a similar (not identical) situation. If you cannot articulate this clearly, do not include the recommendation.
  - `ticket_specification` string, nullable
  - `one_sentence_summary` string, nullable
  - `category` string, nullable
  - `complexity` string, nullable

## Other responses

- `400`: Invalid input
- `401`: Not authenticated
- `403`: Forbidden
- `404`: Not found
- `405`: Method not allowed
- `409`: Conflict
- `422`: Validation Error

---

[API](https://skmtc.dev/superit/apis/super-it-api.md) - [All operations](https://skmtc.dev/superit/apis/super-it-api/llms.txt) - [OpenAPI document](https://skmtc.dev/superit/apis/super-it-api/revisions/4944d556c2bb?raw)