diff --git a/docs/includes/archives b/docs/includes/archives index 86f0c815..aae09c2e 100644 --- a/docs/includes/archives +++ b/docs/includes/archives @@ -9,6 +9,11 @@ +24/04/2023 +1.23.0 +Changes arising from Decision Proposal 298 + + 22/03/2023 1.22.1 Changes arising from Change Request 576 (Maintenance iteration 14) diff --git a/docs/includes/cds_admin b/docs/includes/cds_admin index d4b76784..ca2da9d6 100644 --- a/docs/includes/cds_admin +++ b/docs/includes/cds_admin @@ -226,7 +226,7 @@ This operation may only be called by the CDR Register query string optional -The period of metrics to be requested. Values can be CURRENT (meaning metrics for current day), HISTORIC (meaning metrics for previous days or months) or ALL. If absent the default is ALL. +The period of metrics to be requested. Values can be CURRENT (meaning metrics for current period, dependent on the metric type), HISTORIC (meaning metrics for previous period, depending on the metric type) or ALL. If absent the default is ALL. x-v @@ -1551,7 +1551,7 @@ This operation may only be called by the CDR Register unauthenticated object mandatory -Rejection counts for all uauthenticated end points +Rejection counts for all unauthenticated end points » currentDay @@ -1618,7 +1618,7 @@ This operation may only be called by the CDR Register rejections object mandatory -Number of calls resulting in a rejection due to server execution over time +Number of calls rejected due to traffic thresholds over time » currentDay diff --git a/docs/includes/cds_banking b/docs/includes/cds_banking index 93c25ba9..33250f5a 100644 --- a/docs/includes/cds_banking +++ b/docs/includes/cds_banking @@ -1626,7 +1626,7 @@ To perform this operation, you must be authenticated and authorised with the fol
  • A reasonable date/time nominated by the data holder using internal data structures
  • For transaction amounts it should be assumed that a negative value indicates a reduction of the available balance on the account while a positive value indicates an increase in the available balance on the account
  • -
  • For aggregated transactions (ie. groups of sub transactions reported as a single entry for the account) only the aggregated information, with as much consistent information accross the subsidiary transactions as possible, is required to be shared
  • +
  • For aggregated transactions (ie. groups of sub transactions reported as a single entry for the account) only the aggregated information, with as much consistent information across the subsidiary transactions as possible, is required to be shared
  • Endpoint Version

    @@ -8295,7 +8295,7 @@ This operation does not require authentication - + @@ -8857,7 +8857,7 @@ This operation does not require authentication - + @@ -9964,7 +9964,7 @@ This operation does not require authentication - + diff --git a/docs/includes/cds_common b/docs/includes/cds_common index c4900769..5e2b7388 100644 --- a/docs/includes/cds_common +++ b/docs/includes/cds_common @@ -99,7 +99,7 @@ - + @@ -327,7 +327,7 @@ To perform this operation, you must be authenticated and authorised with the fol - + diff --git a/docs/includes/cds_dcr b/docs/includes/cds_dcr index 4dc4e9d1..d5269973 100644 --- a/docs/includes/cds_dcr +++ b/docs/includes/cds_dcr @@ -28,7 +28,9 @@

    POST /register

    -

    Register a client using a CDR Register issued Software Statement Assertion.

    +

    Register a client using a CDR Register issued Software Statement Assertion.

    + +

    This endpoint does not require CORS.

    Body parameter

    diff --git a/docs/includes/cds_energy b/docs/includes/cds_energy index bdc4fe47..9ccdf187 100644 --- a/docs/includes/cds_energy +++ b/docs/includes/cds_energy @@ -281,27 +281,6 @@ x-min-v: string
    - - - - - - - - - - - - - - - - - - - - -
    » lendingRates [BankingProductLendingRateV2] optionalFully described deposit rates for this account based on the equivalent structure in Product ReferenceFully described lending rates for this account based on the equivalent structure in Product Reference
    » featurescrn string conditionalBPAY CRN for the transaction (if available).
    Where the CRN contains sensitive information, it should be masked in line with how the Data Holder currently displays account identifiers in their existing online banking channels. If the contents of the CRN match the format of a Credit Card PAN they should be masked according to the rules applicable for MaskedPANString. If the contents are are otherwise sensitive, then it should be masked using the rules applicable for the MaskedAccountString common type.
    BPAY CRN for the transaction (if available).
    Where the CRN contains sensitive information, it should be masked in line with how the Data Holder currently displays account identifiers in their existing online banking channels. If the contents of the CRN match the format of a Credit Card PAN they should be masked according to the rules applicable for MaskedPANString. If the contents are otherwise sensitive, then it should be masked using the rules applicable for the MaskedAccountString common type.
    apcaNumbercrn string conditionalBPAY CRN of the Biller (if available).
    Where the CRN contains sensitive information, it should be masked in line with how the Data Holder currently displays account identifiers in their existing online banking channels. If the contents of the CRN match the format of a Credit Card PAN they should be masked according to the rules applicable for MaskedPANString. If the contents are are otherwise sensitive, then it should be masked using the rules applicable for the MaskedAccountString common type.
    BPAY CRN of the Biller (if available).
    Where the CRN contains sensitive information, it should be masked in line with how the Data Holder currently displays account identifiers in their existing online banking channels. If the contents of the CRN match the format of a Credit Card PAN they should be masked according to the rules applicable for MaskedPANString. If the contents are otherwise sensitive, then it should be masked using the rules applicable for the MaskedAccountString common type.
    billerNameheader string conditionalThe time when the customer last logged in to the Data Recipient Software Product. Required for all resource calls (customer present and unattended) if the customer is currently logged. Otherwise optional where the customer has not logged in. Not to be included for unauthenticated calls.The time when the customer last logged in to the Data Recipient Software Product as described in [FAPI-R-Draft]. Required for all resource calls (customer present and unattended). Not required for unauthenticated calls.
    x-fapi-customer-ip-addressheader string conditionalThe time when the customer last logged in to the Data Recipient Software Product. Required for all resource calls (customer present and unattended) if the customer is currently logged. Otherwise optional where the customer has not logged in. Not to be included for unauthenticated calls.The time when the customer last logged in to the Data Recipient Software Product as described in [FAPI-R-Draft]. Required for all resource calls (customer present and unattended). Not required for unauthenticated calls.
    x-fapi-customer-ip-address The version of the API end point that the data holder has responded with.
    400x-fapi-interaction-idstringAn [RFC4122] UUID used as a correlation id. If provided, the data holder must play back this value in the x-fapi-interaction-id response header. If not provided a [RFC4122] UUID value is required to be provided in the response header to track the interaction.
    406x-fapi-interaction-idstringAn [RFC4122] UUID used as a correlation id. If provided, the data holder must play back this value in the x-fapi-interaction-id response header. If not provided a [RFC4122] UUID value is required to be provided in the response header to track the interaction.
    422x-fapi-interaction-idstringAn [RFC4122] UUID used as a correlation id. If provided, the data holder must play back this value in the x-fapi-interaction-id response header. If not provided a [RFC4122] UUID value is required to be provided in the response header to track the interaction.