Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.corsa.finance/llms.txt

Use this file to discover all available pages before exploring further.

Sub-dispositions let you extend Corsa’s standard alert and case statuses with custom resolution reasons. For example, a RESOLVED alert can carry a sub-disposition of true_positive_filed_sar or false_positive_rule_tuning so analysts capture the specific outcome without losing the normalized parent status. Full API reference is available in the API Reference.

​
Overview

Each sub-disposition belongs to:
  • A parent status — the standard Corsa status it qualifies (RESOLVED, ESCALATED, CLOSED_DISMISSED, or CLOSED_ESCALATION_TO_SAR)
  • An entity type — either ALERT or CASE
Sub-dispositions can be preset (system-defined, always available) or custom (created via API). Custom sub-dispositions can be toggled active/inactive without deletion, preserving historical audit data. Parent statuses:
StatusApplies to
RESOLVEDAlerts and Cases
ESCALATEDAlerts and Cases
CLOSED_DISMISSEDCases
CLOSED_ESCALATION_TO_SARCases

​
List Sub-Dispositions

Endpoint: GET /v1/sub-dispositions Returns all sub-dispositions (preset and custom) for the platform. 
GET /v1/sub-dispositions

​
Create a Sub-Disposition

Endpoint: POST /v1/sub-dispositions 
POST /v1/sub-dispositions
Content-Type: application/json

{
  "name": "false_positive_rule_tuning",
  "displayName": "False Positive — Rule Tuning",
  "parentStatus": "RESOLVED",
  "entityType": "ALERT"
}

​
Request Fields

FieldRequiredDescription
nameYesInternal key in lower_snake_case — used in API requests and exports
parentStatusYesThe parent status this sub-disposition qualifies: RESOLVED, ESCALATED, CLOSED_DISMISSED, or CLOSED_ESCALATION_TO_SAR
entityTypeYesEntity this applies to: ALERT or CASE
displayNameNoHuman-readable label shown to analysts. Defaults to title-cased name if omitted

​
Get a Sub-Disposition

Endpoint: GET /v1/sub-dispositions/{id} 
GET /v1/sub-dispositions/sd_abc123

​
Update a Sub-Disposition

Endpoint: PATCH /v1/sub-dispositions/{id} You can update the display name or toggle the active state. Custom sub-dispositions cannot have their name, parentStatus, or entityType changed after creation. 
PATCH /v1/sub-dispositions/sd_abc123
Content-Type: application/json

{
  "displayName": "False Positive — Rule Needs Tuning",
  "isActive": true
}

​
Delete a Sub-Disposition

Endpoint: DELETE /v1/sub-dispositions/{id} Soft-deletes the sub-disposition. Only custom sub-dispositions can be deleted — preset sub-dispositions cannot be removed. 
DELETE /v1/sub-dispositions/sd_abc123

​
Sub-Disposition Response Object

{
  "id": "sd_abc123",
  "platformId": "platform_xyz",
  "name": "false_positive_rule_tuning",
  "displayName": "False Positive — Rule Tuning",
  "parentStatus": "RESOLVED",
  "entityType": "ALERT",
  "isPreset": false,
  "isActive": true,
  "createdAt": "2024-01-15T10:00:00Z",
  "updatedAt": "2024-01-15T10:00:00Z"
}