[XBAP-19700] Update BatchPayments endpoint reponses #723
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Adds the following fields in the example BatchPayments responses:
Consumers of the BatchPayments API may receive FX BatchPayments—originating from other parts of Xero—without any way to identify them as such. In coordination with this PR, we are going to be releasing a change to populate the mentioned FX fields in the responses.
This PR updates the example responses to include those FX fields. The fields themselves already exist in the Account, Payment and Invoice objects, so the SDK is already equipped to handle this information.
Release Notes
Adds FX fields to example responses in the BatchPayments endpoints.
Screenshots (if appropriate):
More in https://xero.atlassian.net/browse/XBAP-21152?focusedCommentId=2518540
Types of Changes