Known Issues

See also Resolved Issues for historical issues and their resolution. Please also refer to the known issues section of the Consumer Data Standards.

Issue	Description

Issue

Description

InterimId availability in GetDataHolderBrandSummary APIs

In GetDataHolderBrandSummaryV2, the InterimId field is not included in responses.

This differs from GetDataHolderBrandSummaryV1, where InterimId may have been returned for certain records. Participants who continue to rely on InterimId may choose to temporarily reference GetDataHolderBrandSummaryV1, as the ACCC works on a fix for GetDataHolderBrandSummaryV2.

The DataHolderBrandId remains the primary and supported identifier in the latest API version, and participants are encouraged to adopt it as the authoritative identifier moving forward.

The Token Endpoint is not included in the Consumer Data Standards

Whilst the Register’s Token Endpoint is discoverable from the Get OpenId Provider Config endpoint, it has been included here (Token Endpoint) for completeness and for consistency with the Security Profile for Data Holders.

The Consumer Data Standards define competing responses for Register API errors

The CDR Register Errors section outlines errors that MAY be returned from the CDR Register APIs.

Individual Register API definitions (e.g. Get Data Recipients) also outline the errors that can be returned from the API.

These error definitions are currently not aligned.

In the case that an invalid industry path parameter is provided, the Register APIs will respond differently depending on the version of the API requested.

Current versions will return a 400 Invalid Industry error whilst deprecated versions will return a 404 Not Found error.

For e.g.

Current Endpoint Version

# Request
GET /cdr-register/v1/invalid/data-recipients
x-v: 3

# Response
HTTP/1.1 400 Bad Request
Content-Type: application/json

{
    "errors": [
        {
            "code": "urn:au-cds:error:cds-all:Field/Invalid",
            "title": "Invalid Field",
            "detail": "Invalid Path Parameter"
        }
    ]
}

Deprecated Endpoint Version

# Request
GET /cdr-register/v1/invalid/data-recipients
x-v: 2

# Response
HTTP/1.1 404 Not Found
Content-Type: application/json

{
    "errors": [
        {
            "code": "urn:au-cds:error:cds-register:Field/InvalidIndustry",
            "title": "Invalid Industry",
            "detail": "Industry URL parameter is invalid"
        }
    ]
}