Releases: XeroAPI/Xero-OpenAPI
2.39.0
Accounting API
- Updated 1099 report sample JSON response.
- Remove the Contact's SkypeUserName field, from the API.Accouting Contact's endpoints.
- Adds the deletion of allocations to Credit Notes, Prepayments and Overpayments
- Removed random character in getPurchaseOrderAttachmentByFileName
Payroll AU
- Added two new enum values in LeavePeriodStatus
Finance
- Cash Validation Api now has rate limiting, there is a new response type added to reflect that.
2.38.0
AU Payroll API
New endpoints added for expanding Leave functionality for AU Payroll
- LeaveApplications/v2 GET includes REQUESTED and REJECTED leave applications
- LeaveApplications/{id}/approve allows for approval of REQUESTED leave applications
- LeaveApplications/{id}/reject allows for rejection of REQUESTED or SCHEDULED leave applications
Added detail to LeaveApplications POST example to indicate expected inclusion of other attributes
Accounting API
Create compliance tax rates
2.37.0
Description
Finance API
- Updates import source description and the example in the BankStatementsPlus Api response doc
Accounting API
- Added all missing currency codes CLF, EEK, LVL, MRO, MXV, SKK, SLE, STD, VES to enum
- Fixed 2023 Reverse Charge tax rates for Singapore
2.36.0
Description
Files API
- Adds
getAssociationsCountmethod to the Files API
Payroll AU API
- Adds new property
PaidLeaveEarningsto theOpeningBalanceschema definition - Adds new property
PayOutTypeto theLeaveApplicationandLeaveEarningsLineschema definitions
Release Notes
getAssociationsCountenables developers to fetch a count of associations for a list of objects. Previously, developers had to call separately for each object.- https://developer.xero.com/documentation/api/payrollau/stp-changes#opening-balance-paid-leave-earnings
- https://developer.xero.com/documentation/api/payrollau/stp-changes/#cashed-out-leave
Types of Changes
- Bug fix (non-breaking change that fixes an issue)
- New feature (non-breaking change that adds functionality)
- Breaking change (fix or feature that would cause existing functionality to not work as expected)
2.35.0
Description
Payroll AU API
- Adds
AllowanceContributesToAnnualLeaveRateandAllowanceContributesToOvertimeRatebooleans toEarningsRatemodel
Release Notes
As part of STP2, two new checkboxes were added for allowance pay items
Types of Changes
- Bug fix (non-breaking change that fixes an issue)
- New feature (non-breaking change that adds functionality)
- Breaking change (fix or feature that would cause existing functionality to not work as expected)
2.34.1
Description
Finance API
- Reformats descriptions of Indicative Balances so they don't break yaml parsing 😬
Release Notes
- Was breaking API Explorer and SDK Codegen
Types of Changes
- Bug fix (non-breaking change that fixes an issue)
- New feature (non-breaking change that adds functionality)
- Breaking change (fix or feature that would cause existing functionality to not work as expected)
2.34.0
Description
Finance API
- Adds Indicative Balances and Payee to BankStatementsPlus
Payroll UK API
- Update the case in
BackPayproperty ofearningsType
Release Notes
Resolves Xero-Ruby #241
- Argument Error invalid value for earnings_type
Types of Changes
- Bug fix (non-breaking change that fixes an issue)
- New feature (non-breaking change that adds functionality)
- Breaking change (fix or feature that would cause existing functionality to not work as expected)
2.33.1
Description
Accounting API
- Updates data type of
IsReconciledproperty ofBatchPaymentto boolean. - Updates data type of
TotalAmountproperty ofBatchPaymentto decimal
Related to this issue
Release Notes
Resolves Xero-NetStandard #453
- Data types did not align with data returned by Accounting API.
Types of Changes
- Bug fix (non-breaking change that fixes an issue)
- New feature (non-breaking change that adds functionality)
- Breaking change (fix or feature that would cause existing functionality to not work as expected)
2.33.0
Description
Accounting API
- Updates
CreateBrandingThemePaymentServicesmethod to accept an array ofPaymentServiceobjects instead of just onePaymentServiceobject to match API functionality
Release Notes
Resolves Xero-Node #605
This will result in a small breaking change where any projects currently using this method will need to wrap their PaymentService object in a PaymentServices object like so:
{ "PaymentServices": [ { "PaymentServiceID": "54b3b4f6-0443-4fba-bcd1-61ec0c35ca55", "PaymentServiceName": "PayUpNow", "PaymentServiceUrl": "https://www.payupnow.com/", "PaymentServiceType": "Custom", "PayNowText": "Time To Pay" } ] }
Types of Changes
- Bug fix (non-breaking change that fixes an issue)
- New feature (non-breaking change that adds functionality)
- Breaking change (fix or feature that would cause existing functionality to not work as expected)
2.32.0
Description
Accounting API
- Adds 2023 tax rates for Singapore
Types of Changes
- Bug fix (non-breaking change that fixes an issue)
- New feature (non-breaking change that adds functionality)
- Breaking change (fix or feature that would cause existing functionality to not work as expected)