[CDS Spec documentation bug- Is x-fapi-auth-date header mandatory or optional]

[AnantVijay-Cuscal]

Description

On CDS API specs x-fapi-auth-date is Optional for Banking and Common APIs. However, the description says "Required for all resource calls (customer present and unattended). Not to be included for unauthenticated calls." https://consumerdatastandardsaustralia.github.io/standards/#banking-apis
Could you please update the Required and Description column to align with each other.

Area Affected

Required column in Parameter section of CDS API specifications for Banking and Common APIs. Also the swaggers for these APIs

Change Proposed

On CDS API specs x-fapi-auth-date is Optional for Banking and Common APIs. However, the description says "Required for all resource calls (customer present and unattended). Not to be included for unauthenticated calls." https://consumerdatastan

dardsaustralia.github.io/standards/#banking-apis
Could you please update the Required and Description column to align with each other.

[CDR-API-Stream]

Hi @AnantVijay-Cuscal,

This is a documentation error. "x-fapi-auth-date" is mandatory for all authenticated resource endpoints but not the unauthenticated endpoints as described in the HTTP Headers section.

In the resource endpoint descriptions, we have "Optional" in the required column (see Get Accounts). This is a documentation error and it should read "Mandatory".

This issue will be fixed in the next version of the standards.

[CDR-API-Stream]

These changes have been staged for review: ConsumerDataStandardsAustralia/standards-staging@release/1.15.0...maintenance/430

[CDR-API-Stream]

This change was incorporated into release v1.15.0. Refer to Decision 212 for further details.