Pending review, grouped by counterparty
get_pending_by_counterpartySummarises the review queue clustered by counterparty and direction — the exact grain a rule is keyed on. Each group carries the counterparty_key, a human label, direction (inbound = money in, outbound = money out), how many events, and their total in cents. Lets you decide once per vendor instead of per transaction: read this, then call create_counterparty_rule to categorise a whole counterparty (existing pending events and all future ones) in one step. Groups are ordered largest-first.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "get_pending_by_counterparty"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| org_id | No | Optional. Defaults to the organisation the authenticated API key is bound to, so you normally omit it and never need to ask the user for their organisation UUID. If provided, it must match the key’s org or the request is rejected. | 0e91146d-511c-469f-bdee-5c867b26ae0d |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| groups | Yes |