Skip to main content
A read-write PAT can make the same stored underwriting edits available in the Pathway app. These routes update the canonical bank result inside the Book. The next GET /books/{book_id}/analytics call calculates from the new state immediately. Fetch the current analytics after a mutation when your application needs the resulting true revenue, debt metrics, schedules, or screening decision.

Update transaction tags

Get the current tag registry from:
Then apply additions, removals, and replacements to any set of transaction IDs.
Invalid values in add are ignored. A replacement only removes old_tag when new_tag is valid. Use the registry response instead of hard-coding the available set.

Manage debt positions

A stored position groups transactions that belong to one debt relationship. Analytics enrich that stored group with payment schedules, episodes, remittance burden, misses, modifications, and status.

Create and populate a position

Send position_id: null to the assignment endpoint to remove the listed transactions from every position.
Changing a position’s loan type also replaces the old loan tag on its assigned transactions. Deleting with remove_tag: true removes that position’s loan tag from its transactions.

Control analytics exclusions

Each supplied field replaces the complete stored list for that field. Omitted fields remain unchanged. Send an empty list to clear one.
A reparse replaces book_meta, including transaction tags, stored positions, and these exclusion lists. Apply edits after the parse you intend to keep.