All SDK examples assume you have initialized the Corsa client as shown in the Node.js SDK Configuration or Python SDK Configuration guide.
Overview
When a third-party vendor (such as Chainalysis or TRM Labs) fires an alert, it includes a vendor-specific rule ID. Without external rules configured, analysts see a raw ID. By registering your external rules in Corsa, alerts from your vendors display human-readable names and descriptions instead. External rules have the same lifecycle as internal rules —draft, active, disabled — and appear alongside internal rules in the Corsa UI.
The
vendorName field cannot be set to Corsa — that value is reserved for rules authored inside the platform.Create an External Rule
Endpoint:POST /v1/external-rules
Request Fields
List External Rules
Endpoint:GET /v1/external-rules
Returns a paginated list of all external rules for the platform.
Filter by Vendor
Use theGET /v1/external-rules/vendors endpoint to retrieve the distinct vendor names in use — useful for building filter UIs or auditing which vendors have rules registered.
REST API
Get an External Rule
Endpoint:GET /v1/external-rules/{id}
Update an External Rule
Endpoint:PUT /v1/external-rules/{id}
All fields are optional — only include the fields you want to change.
Delete an External Rule
Endpoint:DELETE /v1/external-rules/{id}
Soft-deletes the rule. The rule is removed from active matching but its history is preserved for audit purposes.
List Vendors
Endpoint:GET /v1/external-rules/vendors
Returns the distinct vendor names already used across your registered external rules. Use this to ensure consistent naming when registering new rules — for example, to confirm whether you’ve registered rules as "Chainalysis" or "chainalysis" before adding more.