POST api/v1/case-management/create
Documentation Index
Fetch the complete documentation index at: https://sigma-docs.pastel.africa/llms.txt
Use this file to discover all available pages before exploring further.
assignedTo field must be a valid user ID from your Sigma account. You can find user IDs under Account → Team Members & Roles in the dashboard. The user must have the can assign case permission to be assigned a case.A short, descriptive title for the case. Shown in the case list.
"High-value transaction requiring review"
A detailed description of why the case was opened and what needs to be investigated.
"A transfer of ₦4,500,000 was flagged by the fraud scoring engine with a score of 87. The customer has no prior history of transactions of this size. Requires manual review before release."
The urgency level of the case.
low, medium, high "high"
The ID of the team member responsible for this case. Must be a valid user in your Sigma account with the can assign case permission.
"64a9f1c2d3e4b5a6c7d8e9f0"
The Sigma product area this case relates to. Use one of the standard module values or omit and provide customModule instead.
transaction-monitoring, aml, cdd, kyc, reporting "transaction-monitoring"
A custom module name for cases that do not fit a standard Sigma product module. Provide either module or customModule, not both.
"internal-audit"
A reference to an existing Sigma record to link to this case.
The deadline for resolving this case. ISO 8601 format. Cases past their due date are flagged as overdue in analytics.
"2026-04-25T23:59:59.000Z"
An optional checklist of steps the investigator should complete. Each string becomes a task item on the case.
[
"Review customer transaction history for the last 90 days",
"Verify source of funds documentation",
"Record final decision with supporting notes"
]
File paths for any attachments to include with the case at creation.
[]
The ID of a senior team member to escalate this case to, if needed.
null