Change History

This page serves as a log of all past changes related to the Register, including detailed descriptions of the changes and their delivery dates.

Endpoint	Change	Delivery Date

Endpoint	Change	Delivery Date
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 Statement Assertion (SSA) V3	The `x-v` header will be mandatory for incoming requests.	21 September 2023
Get Software Statement Assertion (SSA) V3	Deprecate endpoint	TBD
Get Software Statement Assertion (SSA) V4	Change Log for Standard Version 1.35 - Consumer Data Standards	TBD
Get Data Holder Brands V1	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 Data Holder Brands V2	Deprecate endpoint	TBD
Get Data Holder Brands V3	Change Log for Standard Version 1.35 - Consumer Data Standards	TBD
Get Software Products Statuses V1	Remove obsolete endpoint	21 September 2023
Get Software Products Statuses V2	The `x-v` header will be mandatory for incoming requests.	21 September 2023
Get Software Products Statuses V2	Deprecate endpoint	TBD
Get Software Products Statuses V3	Change Log for Standard Version 1.35 - Consumer Data Standards	TBD
Get Data Recipient Statuses V1	Remove obsolete endpoint	21 September 2023
Get Data Recipient Statuses V2	The `x-v` header will be mandatory for incoming requests.	21 September 2023
Get Data Recipients Statuses V2	Deprecate endpoint	TBD
Get Data Recipients Statuses V3	Change Log for Standard Version 1.35 - Consumer Data Standards	TBD
Get Data Recipients V1	Remove obsolete endpoint	21 September 2023
Get Data Recipients V2	Remove obsolete endpoint	21 September 2023
Get Data Recipients V3	The `x-v` header will be mandatory for incoming requests.	21 September 2023
Get Data Recipients V3	Deprecate endpoint	TBD
Get Data Recipients V4	Change Log for Standard Version 1.35 - Consumer Data Standards	TBD
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