Example for DH calling ADR arrangements endpoint

Question

If a customer actively revokes an arrangement, using the Data Holder (DH) dashboard, the DH is expected to call the Accredited Data Recipient (ADR) arrangements end point to communicate the revocation to the ADR. The ADR then invokes deletion or de-identification according to the customer's election.

An example provided on the standards website, under CDS End Points, shows the request made by the ADR to the DH arrangements endpoint: POST https://data.holder.com.au/arrangements/revoke.

Are there any differences when a DH calls the ADR endpoint? In particular, how is authentication handled in this case?

Answer 

The ADR (Data Recipient Path), discussed under CDS End Points, is of the same form as the DH end point: <RecipientBaseUri>/arrangements/revoke. 

For an example of authentication when a DH calls an ADR endpoint, see CDS Client Authentication.

See the example headed "Non-Normative Example - Data Holder calls the Data Recipient's revocation end point". This non-normative example shows the revocation end point but the authentication aspects are identical.