Rules and Rule Sets
Read the rules derived from a framework, regenerate them, and group rules from several frameworks into named rule sets that document sets are judged against.
Rules are what evaluations check. The platform derives them from the text of a framework document: each rule has a text, an obligation of must, should or may, and where available a section, an applicability, a condition, a threshold and the source_quote, the framework's own words the rule rests on. A rule's origin records whether it is ai (as generated), edited (a person changed it) or manual (a person wrote it). The routes in this section read and regenerate rules; they do not edit single rules.
rule_code is the framework's own numbering when it has one. testable says whether a document can be checked against the rule. source_fields names the captured fields a rule comes from, or is null when unknown. These are the editable rules, not the fields captured from the framework: the extracted fields of a framework are counted separately as rule_count on the framework row.
/v1/compliance/frameworks/{documentId}/rulesRule fields
/v1/compliance/frameworks/{documentId}/rules/generatePath parameters
Rule Sets
A rule set is a named, hand-picked list of rules from one or several frameworks. A document set linked to a rule set is judged only against that list instead of every rule of every ON framework, which keeps an evaluation focused on the rules that matter to the documents. Every rule put into a rule set must belong to a framework that is ON and completed; up to 1000 rules fit in one set.
A rule set's view lists only the rules whose framework is ON: rule_ids holds the rules in force and frameworks summarises where they come from. A rule of an OFF framework stays stored in the set but is left out of the view, so turning a framework OFF and ON again loses nothing. updated_at changes with the rules, not with a rename.
/v1/compliance/rule-sets/v1/compliance/rule-setsBody fields
cURL: Create a rule set
curl -X POST "https://api.talonic.com/v1/compliance/rule-sets" \
-H "Authorization: Bearer $TALONIC_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"name": "Supplier onboarding",
"rule_ids": ["0f3d8a52-1b6c-4e97-a2d4-8c5e91b07f36", "7a19c4e8-5d20-43b1-9f68-d3e0a4b52c19"]
}'Response: 201 Rule set
{
"id": "e41b9d07-2c85-4a3f-b6d1-90f7c2a8e553",
"name": "Supplier onboarding",
"rule_ids": ["0f3d8a52-1b6c-4e97-a2d4-8c5e91b07f36", "7a19c4e8-5d20-43b1-9f68-d3e0a4b52c19"],
"frameworks": [
{ "document_id": "9d0c4f6e-3b1a-4c53-8f0e-2a7b6c1d5e40", "name": "Supplier Code of Conduct", "rule_count": 2 }
],
"created_at": "2026-10-20T10:30:00.000Z",
"updated_at": "2026-10-20T10:30:00.000Z"
}/v1/compliance/rule-sets/{ruleSetId}Path and body
/v1/compliance/rule-sets/{ruleSetId}