Rules API
The Rules API allows you to manage automated categorization rules for transactions.
Endpoints
| Method | Endpoint | Description |
|---|---|---|
| GET | /api/v1/rules | List all rules |
| GET | /api/v1/rules/:id | Get a single rule |
| POST | /api/v1/rules | Create a new rule |
| PUT | /api/v1/rules/:id | Update a rule |
| DELETE | /api/v1/rules/:id | Delete a rule |
| POST | /api/v1/rules/:id/run | Execute rule on matching transactions |
| GET | /api/v1/rules/:id/preview | Dry-run: see which transactions a rule would match |
How Rules Work
- Rules are evaluated in priority order (lowest number first)
- When a transaction matches a rule's conditions, the rule's actions are applied
- Multiple rules can match the same transaction
- If rules conflict, higher priority (lower number) wins
Quick Example
curl -X POST "https://statements.finopsbricks.com/api/v1/rules" \
-H "api-key: fob_stm_xxxxxxxxxxxx" \
-H "api-secret: xxxxxxxxxxxxxxxx" \
-H "Content-Type: application/json" \
-d '{
"name": "Salary Income",
"conditions": [{"field": "particulars", "operator": "contains", "value": "SALARY"}],
"actions": [{"field": "category", "value": "income"}]
}'
Related
- Rule Object - Data structure reference
- Transactions Search - Uses same condition format
- Transactions API - Apply rules to transactions