v1.0.0
As part of an ongoing effort to improve the consistency and usability of our SDKs, we’ve updated the SDK generation process. This update introduces breaking changes to the SDK. All breaking changes affect only method signatures and namespacing, not core record types or properties. SDK initialization, configuration, business logic, and workflows remain unchanged. For more information on precise method signatures and example usage, please see the SDK reference on GitHub.
Import paths consolidated
All types are now importable from the top-level payabli package. The following submodules no longer exist:
Removed submodules
payabli.money_in— types moved topayablipayabli.money_out_types— types moved topayablipayabli.query_types— types moved topayablipayabli.v_2_money_in_types— types moved topayabli
Example import changes
Request wrapper types removed
The following wrapper types are deleted. Their fields are now passed directly as keyword arguments to the calling method.
Removed types and their replacements
The notificationlogs.search_notification_logs method now requires start_date and end_date as explicit keyword arguments. They were previously optional fields inside the removed wrapper.
method is now required on all payment types
The method field previously defaulted to a value on each payment type. It’s now required and has no default.
Affected types
V2 error types renamed
The per-endpoint V2 error classes from payabli.v_2_money_in_types.errors are removed. V2 endpoints now raise the same error types as all other methods.
ConflictError has been removed from payabli.errors. PaymentRequiredError has been added.
Type renames
Renamed types
Notification log ID type changed
get_notification_log, retry_notification_log, and bulk_retry_notification_logs now accept str instead of uuid.UUID for ID parameters.
Subscription date format changed
ScheduleDetail.start_date and ScheduleDetail.end_date now use ISO 8601 (YYYY-MM-DD) instead of MM-DD-YYYY.