Update a rule
Partially update a rule. At least one field must be provided. If actions is included, it must contain at least one action (empty array is rejected).
Partially updates a rule’s configuration. You can modifyDocumentation Index
Fetch the complete documentation index at: https://docs.scrip.dev/llms.txt
Use this file to discover all available pages before exploring further.
name, description, condition, actions, order, stop_after_match, active_from, active_to, budgets, or status. Only the fields included in the request body are changed; omitted fields remain untouched.
The budgets field is a full replacement when present. The provided array replaces all existing budgets. Omitting the field leaves budgets unchanged. To remove all budgets, send an empty budgets array.
To suspend a rule without archiving it, set status to SUSPENDED. To archive a rule, set status to ARCHIVED. Changing the order field will fail with a 409 if another active rule in the same program already occupies that position.
Archived rules cannot be modified. Rules belonging to an archived program also cannot be modified.
Authorizations
API key passed in the X-API-Key header.
Path Parameters
Rule ID
Body
Fields to update
Request body for updating an existing rule. Only provided fields are updated. At least one field must be specified. If actions is provided, it must be a non-empty array.
Replacement actions array. Omit to leave actions unchanged. If provided, must be non-empty.
Start of the rule's active window (RFC 3339). Send null to clear.
"2024-01-01T00:00:00Z"
End of the rule's active window (RFC 3339). Send null to clear.
"2024-12-31T23:59:59Z"
Replacement budget array. Omit to leave budgets unchanged. Send empty array to remove all budgets.
Updated CEL expression
1"event.type == 'purchase'"
Updated description
1000"Updated description"
Updated display name
1 - 255"Updated Rule Name"
Updated evaluation sequence position
x >= 150
Updated lifecycle status: ACTIVE, SUSPENDED, or ARCHIVED
ACTIVE, SUSPENDED, ARCHIVED "SUSPENDED"
Whether to stop evaluating subsequent rules after this one matches
true
Response
Updated rule
Actions to execute when the condition matches
[
{
"amount": "event.amount * 10",
"asset_id": "550e8400-e29b-41d4-a716-446655440002",
"type": "CREDIT"
}
]Start of the rule's active window (RFC 3339, null if always active)
"2024-01-01T00:00:00Z"
End of the rule's active window (RFC 3339, null if no end date)
"2024-12-31T23:59:59Z"
Budget constraints applied to this rule
CEL expression that determines when the rule fires
"event.type == 'purchase' && event.amount > 0"
When this rule was created (RFC 3339)
"2024-01-15T10:30:00Z"
When this rule was archived (null if not archived)
Human-readable summary of what this rule does
"Awards 10 points per dollar spent"
Unique identifier for this rule
"550e8400-e29b-41d4-a716-446655440000"
Display name
"Purchase Reward"
Evaluation sequence (lower = first, must be unique per program)
100
Program this rule belongs to
"550e8400-e29b-41d4-a716-446655440001"
Lifecycle status: ACTIVE, SUSPENDED, or ARCHIVED
"ACTIVE"
When true, no subsequent rules evaluate after this one matches
false
When this rule was last modified (RFC 3339)
"2024-01-15T10:30:00Z"