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
Request body wrapper removed
Twenty methods previously accepted { body: { ... } } and now accept the fields directly at the top level.
Affected methods
bill.addBillcustomer.addCustomerhostedPaymentPages.newPageinvoice.addInvoiceinvoice.editInvoicelineItem.addItemmoneyIn.getpaidmoneyIn.authorizemoneyIn.getpaidv2moneyIn.authorizev2moneyOut.authorizeOutmoneyOut.reissueOutsubscription.newSubscriptionpayoutSubscription.createPayoutSubscriptionnotificationlogs.searchNotificationLogspaymentLink.addPayLinkFromInvoicepaymentLink.addPayLinkFromBillpaymentLink.addPayLinkFromBillLotNumbertokenStorage.addMethodtokenStorage.updateMethod
The bill.sendToApprovalBill and moneyOut.captureAllOut methods retain their body: field because those endpoints accept a raw array as the HTTP body.
query.listTransfersOrg signature change
orgId is now a required first positional argument and has been removed from ListTransfersRequestOrg:
MoneyOutTypesRequestOutAuthorize renamed
The request type for moneyOut.authorizeOut is now RequestOutAuthorize. The fields are unchanged, but the body: wrapper property has been removed — all payout fields are now top-level properties.
query.listBatchDetailsOrg return type changed
Return type changed from Payabli.QueryResponseSettlements to Payabli.QueryBatchesDetailResponse.