Update Rule
API Reference
Update Rule
Update an existing rule configuration β in the gu1 rules engine for compliance and risk detection, with examples for update use cases.
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
UUID of the rule to update
Request Body
All fields are optional. Only include fields you want to modify.Update rule name
Update rule description
Update category:
kyc, kyb, aml, fraud, compliance, customEnable or disable the rule
Update priority (1-100)
Update risk score (0-100)
Update status:
draft, in_progress, in_review, active, shadow, archived, inactiveUpdate condition logic
Update actions array
Update target entity types
Update evaluation mode:
sync or asyncUpdate associated risk matrix UUID
Update scope configuration
Update tags array
Response
UUID of the updated rule
New version number (incremented)
UUID of the previous version
User ID who updated the rule
ISO timestamp of the update
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
- Partial Updates: Only send fields you want to change
- Test First: Use execute endpoint to test before updating production rules
- Shadow Mode: Test condition changes in shadow mode before activating
- Version History: Keep track of version numbers for rollback capability
- Monitor Stats: Watch execution statistics after updates
- Gradual Rollout: Update priority gradually when deploying new logic
- Tag Changes: Tag rules with update metadata for tracking
Versioning
Each update creates a new version:version: Increments by 1previousVersionId: 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
- Get Rule - Retrieve current rule state
- Execute Rule - Test updated rules
- Create Rule - Create new rules
- List Rules - Query rules