Skip to content

TRIP-62641 Document sorted=false fast path on /ledger/posting/openPost#131

Open
radres wants to merge 1 commit into
masterfrom
TRIP-62641-openpost-sorted-docs
Open

TRIP-62641 Document sorted=false fast path on /ledger/posting/openPost#131
radres wants to merge 1 commit into
masterfrom
TRIP-62641-openpost-sorted-docs

Conversation

@radres

@radres radres commented Jun 23, 2026

Copy link
Copy Markdown
Contributor

What

Documents the new optional sorted query parameter on GET /ledger/posting/openPost:

  • changelog.md — new 2.75.06 entry describing the parameter and its values.
  • FAQ.md — a performance tip (placed next to the existing fields effectivity Q&A) showing how to use sorted=false to speed up the endpoint on large accounts.

Why

GET /ledger/posting/openPost sorts the result by voucher by default, which is very expensive on accounts with a large number of open postings (some integrations see multi-minute responses). The backend now supports sorted=false, which returns the same set of open postings, unordered, on a fast path. The default (sorted=true) is unchanged, so existing callers are unaffected.

Backend change: Tripletex-AS/tripletex#9431 (live in prod since 2026-06-23). This docs PR lets API consumers discover and adopt the faster option.

Note for the reviewer

The monolith API_VERSION constant is currently still 2.75.05 (the backend change did not bump it). I used 2.75.06 (2026-06-23) as the next patch entry — please align the version / bump the constant to match the intended release if needed.

🤖 Generated with Claude Code

…ing/openPost

Add changelog entry and FAQ tip for the new optional `sorted` query
parameter on GET /ledger/posting/openPost. Default (sorted=true) is
unchanged; sorted=false returns the same open postings unordered and is
significantly faster on accounts with many postings.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants