Checklists let your compliance team track required documents and approval steps against any Corsa entity — alerts, cases, or clients. Define a reusable checklist template once, and Corsa automatically attaches a checklist to the relevant entities when triggered. Full API reference is available in the API Reference.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.
Checklist Templates
Templates define the standard items your team must complete for a given entity type. Each template belongs to a specificentityType and contains one or more items. Templates can be toggled active or inactive — inactive templates are not used for new checklists.
Create a Checklist Template
Endpoint:POST /v1/checklist-templates
Request Fields
| Field | Required | Description |
|---|---|---|
entityType | Yes | Entity type this template applies to: ALERT, CASE, INDIVIDUAL_CLIENT, or CORPORATE_CLIENT. |
name | Yes | Display name for the template. |
description | No | Optional description visible to analysts. |
isActive | No | Whether the template is active. Defaults to true. |
items | No | Initial checklist items to include (see item fields below). |
Checklist Item Fields
| Field | Required | Description |
|---|---|---|
name | Yes | Name of the checklist item. |
note | No | Guidance note shown to the analyst. |
category | No | Classification label (e.g., IDENTITY, SCREENING, FINANCIAL). |
statusOptions | No | Custom status options for this item. |
List Checklist Templates
Endpoint:GET /v1/checklist-templates
Returns all checklist templates for the platform.
Get a Checklist Template
Endpoint:GET /v1/checklist-templates/{id}
Update a Checklist Template
Endpoint:PUT /v1/checklist-templates/{id}
Update the template name, description, or active state. Updating a template does not affect checklists already created from it.
Delete a Checklist Template
Endpoint:DELETE /v1/checklist-templates/{id}
Deletes the template. This does not affect checklists already created from it.
Add an Item to a Template
Endpoint:POST /v1/checklist-templates/{id}/items
Add a new item to an existing template.
Update a Template Item
Endpoint:PUT /v1/checklist-templates/items/{itemId}
Delete a Template Item
Endpoint:DELETE /v1/checklist-templates/items/{itemId}
Working with Checklists
Once a template is active, Corsa creates checklists for the matching entity type. You can retrieve and update checklist items through the following endpoints.Get a Checklist for an Entity
Endpoint:GET /v1/checklists/entity
Returns the active checklist for a given entity. Pass the entity ID and type as query parameters.
Query Parameters
| Parameter | Required | Description |
|---|---|---|
entityId | Yes | ID of the entity to retrieve the checklist for. |
entityType | Yes | Entity type: ALERT, CASE, INDIVIDUAL_CLIENT, or CORPORATE_CLIENT. |
Response
Update a Checklist Item
Endpoint:PUT /v1/checklists/{checklistId}/items/{itemId}
Mark an item as completed, attach a document, set an expiration date, or add custom fields.
Request Fields
| Field | Required | Description |
|---|---|---|
status | No | Item status (e.g., PENDING, APPROVED, REJECTED). Available values depend on the template’s statusOptions. |
documentUrl | No | URL of the supporting document. |
attachmentId | No | ID of an attachment already uploaded to Corsa (see Managing Attachments). |
documentMimeType | No | MIME type of the document (e.g., application/pdf, image/jpeg). |
documentSubmissionDate | No | ISO 8601 timestamp of when the document was submitted. |
expirationDate | No | ISO 8601 timestamp of when the document expires. |
note | No | Analyst note for this item. |
customFields | No | Key-value custom fields. |
isArchived | No | Set to true to archive the item without deleting it. |
What’s Next?
Managing Attachments
Upload and link documents to checklist items, alerts, and cases.
Managing Alerts & Cases
Bulk operations, status updates, and entity associations for alerts and cases.