Skip to content

fix: update client for Ledger v0.20.2 error responses #63

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
wini83 merged 2 commits into from
Oct 17, 2026
Merged

fix: update client for Ledger v0.20.2 error responses #63

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
438fa6a
chore: regenerate client from ledger v0.20.2
github-actions[bot] Oct 17, 2026
0960e65
fix: translate regenerated API errors into public SDK exceptions
wini83 Oct 17, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions docs/reference/exceptions.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,18 @@
# Exceptions

The high-level client raises SDK exceptions for HTTP error responses rather
than returning error models as operation results:

- HTTP 422 raises `OblidogValidationError`.
- Typed integration run conflicts raise `OblidogConflictError`; its `code`
contains the integration conflict reason.
- Other HTTP errors raise `OblidogApiError`.

These exceptions preserve the original HTTP status in `status_code` and the
complete response bytes in `content`, including error codes and `params`.
Undocumented statuses also raise `OblidogApiError` with the generated exception
retained as the cause.

::: oblidog_client.OblidogError

::: oblidog_client.OblidogApiError
Expand Down
Loading
Loading