GET /api/v2/{}/reports/ledger_accounts/{}* → endpoint removal
Deprecated, no date
Moneybird has deprecated the GET /api/v2/{}/reports/ledger_accounts/{}* endpoint without a shutdown date. Calls made to this route are marked as endpoint deprecated and will eventually fail. The change applies to requests querying ledger account reports under this path.
Calls it hits
GET /api/v2/{}/reports/ledger_accounts/{}*
What to use instead of these calls
Read the journal entries report instead by using GET /api/v2/{administration_id}/reports/journal_entries.
In Moneybird API's words
GET /{administration_id}/reports/ledger_accounts/{ledger_account_id}{format} - endpoint deprecated
Facts
- API
- Moneybird API
moneybird.com - Kind
- Endpoint removal
- Announced
- October 21, 2025
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Moneybird API's own pages
Questions
When does this change take effect?
Moneybird API deprecated GET /api/v2/{}/reports/ledger_accounts/{}* without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Moneybird API has not given a shutdown date yet.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
More from Moneybird API 4
-
POST /api/v2/{}/webhooks*Endpoint removal Stopped working -
No date
DELETE /api/v2/{}/purchase_transactions/{}/delete*Endpoint removal Deprecated, no date -
No date
GET /api/v2/{}/import_mappings/*Endpoint removal Deprecated, no date -
No date
GET /api/v2/{}/subscription_templates/{}/checkout_identifier*Endpoint removal Deprecated, no date
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.