Update x-fapi-auth-date description for Customer APIs #532
Labels
Documentation
Improvements, additions or queries related to documentation
Comments
nils-work
added
the
Documentation
CDR-API-Stream
moved this from Full Backlog
to Iteration Candidates
in Data Standards Maintenance
CDR-API-Stream
moved this from Iteration Candidates
to In Progress: Design
in Data Standards Maintenance
CDR-API-Stream
moved this from In Progress: Design
to In Progress: Staging
in Data Standards Maintenance
CDR-API-Stream
moved this from In Progress: Staging
to Awaiting Chair Approval
in Data Standards Maintenance
|
@nils-work our understanding of this change is to fix the documentation only. It does not require any action from the Data Holder with our current implementation. Please correct me if this is misinterpreted. |
|
Hi @cuctrangsb The intention of the change was only to make the description of that header consistent throughout the Standards. It contained slightly different wording in the A diff of the change in staging is available here: ConsumerDataStandardsAustralia/standards-staging@8f4570e. |
CDR-API-Stream
moved this from Awaiting Chair Approval
to Done
in Data Standards Maintenance
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
CR #489 addressed consistency issues regarding the description of the
x-fapi-auth-dateheader in the Banking API resource requests.Customer API resource requests are also inconsistent and require updating to align with the description in the HTTP Headers section.
Area Affected
Customer APIs
Change Proposed
Align to the description in the HTTP Headers section.
The text was updated successfully, but these errors were encountered: