Delivery Dates

The delivery dates do not represent a commitment, guarantee, obligation or promise to deliver any product or feature, or to deliver any product and feature by any particular date, and is intended to outline the general development plans. This roadmap should be used as a guide only.

Definitions

Delivery Date: The scheduled date when the change will be implemented.

Endpoint	Change	Delivery Date
Get Data Holder Brands V1	Remove obsolete endpoint	21 September 2023
Get Software Statement Assertion (SSA) V1	Remove obsolete endpoint	21 September 2023
Get Software Statement Assertion (SSA) V2	Remove obsolete endpoint	21 September 2023
Get Software Products Statuses V1	Remove obsolete endpoint	21 September 2023
Get Data Recipient Statuses V1	Remove obsolete endpoint	21 September 2023
Get Data Recipients V1	Remove obsolete endpoint	21 September 2023
Get Data Recipients V2	Remove obsolete endpoint	21 September 2023
Get Data Holder Brands V2	The `x-v` header will be mandatory for incoming requests.	21 September 2023
Get Software Statement Assertion (SSA) V3	The `x-v` header will be mandatory for incoming requests.	21 September 2023
Get Software Products Statuses V2	The `x-v` header will be mandatory for incoming requests.	21 September 2023
Get Data Recipient Statuses V2	The `x-v` header will be mandatory for incoming requests.	21 September 2023
Get Data Recipients V3	The `x-v` header will be mandatory for incoming requests.	21 September 2023
Private Key JWT Client Authentication	Support RFC7521 such that, until November 13th 2023, clients authenticating using Private Key JWT are recommended to provide the `client_id`, but no longer required. From November 13th 2023, it is then optional to provide the `client_id`. This relates to the CDR Register authenticating with Data Holders and ADRs authenticating with the CDR Register.	21 September 2023