Store a new rule
Creates a new rule. The data required can be submitted as a JSON body or as a list of parameters.
Body
JSON array or key=value pairs with the necessary rule information. See the model for the exact specifications.
titlestringrequiredFirst rule title.descriptionstringFirst rule descriptionrule_group_idstringrequiredID of the rule group under which the rule must be stored. Either this field or rule_group_title is mandatory.
81rule_group_titlestringTitle of the rule group under which the rule must be stored. Either this field or rule_group_id is mandatory.
New rule grouporderinteger<int32>5Which action is necessary for the rule to fire? Use either store-journal, update-journal or manual-activation.
store-journalactivebooleantrueWhether or not the rule is even active. Default is true.
truestrictbooleantrueIf the rule is set to be strict, ALL triggers must hit in order for the rule to fire. Otherwise, just one is enough. Default value is true.
truestop_processingbooleanIf this value is true and the rule is triggered, other rules after this one in the group will be skipped. Default value is false.
falseParameters
X-Trace-Idstring<uuid>headerUnique identifier associated with this request.
Response
New rule stored, result in response.
Bad request
Unauthenticated
Page not found
Validation error. The body will have the exact details.
Internal exception
Authorization
firefly_iii_authoauth2OAuth2 authorization code flow. Create a client on your installation's /profile page; it authorizes at /oauth/authorize and issues tokens at /oauth/token there. The URLs below are the demo site's. How to use the API walks through it.
local_bearer_authhttp (bearer)A Personal Access Token, sent as a bearer token. Create one on your installation under Options > Profile > OAuth > Personal Access Tokens.
