Skip to main content
PATCH
Update Rule

Overview

Updates an existing rule’s configuration. All fields are optional - only include the fields you want to update. Updating a rule automatically increments its version number and maintains version history for audit purposes.

Endpoint

Authentication

Requires a valid API key in the Authorization header:

Path Parameters

string
required
UUID of the rule to update

Request Body

All fields are optional. Only include fields you want to modify.
string
Update rule name
string
Update rule description
string
Update category: kyc, kyb, aml, fraud, compliance, custom
boolean
Enable or disable the rule
number
Update priority (1-100)
number
Update risk score (0-100)
string
Update status: draft, in_progress, in_review, active, shadow, archived, inactive
object
Update condition logic
array
Update actions array
array
Update target entity types
string
Update evaluation mode: sync or async
string
Update associated risk matrix UUID
object
Update scope configuration
array
Update tags array

Response

string
UUID of the updated rule
number
New version number (incremented)
string
UUID of the previous version
string
User ID who updated the rule
string
ISO timestamp of the update
Returns the complete updated rule object with all fields.

Example Requests

Enable/Disable Rule

Update Priority and Score

Update Conditions

Add Actions

Update Status to Shadow Mode

Update Tags

Response Example

Error Responses

404 Not Found

400 Bad Request - Invalid Data

401 Unauthorized

403 Forbidden

409 Conflict

Use Cases

Progressive Rule Refinement

Bulk Update Rules by Category

A/B Testing Rules

Rotate Action Recipients

Best Practices

  1. Partial Updates: Only send fields you want to change
  2. Test First: Use execute endpoint to test before updating production rules
  3. Shadow Mode: Test condition changes in shadow mode before activating
  4. Version History: Keep track of version numbers for rollback capability
  5. Monitor Stats: Watch execution statistics after updates
  6. Gradual Rollout: Update priority gradually when deploying new logic
  7. Tag Changes: Tag rules with update metadata for tracking

Versioning

Each update creates a new version:
  • version: Increments by 1
  • previousVersionId: Links to previous version
  • Version history is maintained for audit and rollback

Notes

  • Updates are applied immediately for sync rules
  • Async rules may take a few minutes to reflect changes
  • Statistics are preserved across updates
  • Disabled rules don’t execute but remain in the system

See Also