Changes to Read account list

Changed in 4 of the 50 revisions of this API.▲30●25○43

1. Feb 19, 20210d82c4699548▲2●3○19
2. Feb 10, 2021b51fe6ddb1fc▲24●19○5
3. Feb 10, 20213cc5b6a584f1▲2●3○19
4. Feb 10, 2021f324b23056bf▲2

What changed

• Feb 19, 20210d82c4699548▲2●3○19See the full diff
  • ▲

    the accounts/items/details response property's maxLength was increased from 140 to 500 for the response status 200

    response-property-max-length-increased

  • ▲

    the accounts/items/name response property's maxLength was increased from 35 to 70 for the response status 200

    response-property-max-length-increased

  • ●

    added the new SCA_INVALID enum value to the additionalErrors/items/code response property for the response status 400 (media type: application/problem+json)

    response-property-enum-value-added

  • ●

    added the new SCA_INVALID enum value to the code response property for the response status 400 (media type: application/problem+json)

    response-property-enum-value-added

  • ●

    added the new SCA_INVALID enum value to the tppMessages/items/code response property for the response status 400 (media type: application/json)

    response-property-enum-value-added

  • ○

    added the optional property _links/confirmation to the response with the 400 status (media type: application/json)

    response-optional-property-added

  • ○

    added the optional property _links/confirmation to the response with the 400 status (media type: application/problem+json)

    response-optional-property-added

  • ○

    added the optional property _links/confirmation to the response with the 401 status (media type: application/json)

    response-optional-property-added

  • ○

    added the optional property _links/confirmation to the response with the 401 status (media type: application/problem+json)

    response-optional-property-added

  • ○

    added the optional property _links/confirmation to the response with the 403 status (media type: application/json)

    response-optional-property-added

  • ○

    added the optional property _links/confirmation to the response with the 403 status (media type: application/problem+json)

    response-optional-property-added

  • ○

    added the optional property _links/confirmation to the response with the 404 status (media type: application/json)

    response-optional-property-added

  • ○

    added the optional property _links/confirmation to the response with the 404 status (media type: application/problem+json)

    response-optional-property-added

  • ○

    added the optional property _links/confirmation to the response with the 405 status (media type: application/json)

    response-optional-property-added

  • ○

    added the optional property _links/confirmation to the response with the 405 status (media type: application/problem+json)

    response-optional-property-added

  • ○

    added the optional property _links/confirmation to the response with the 406 status (media type: application/json)

    response-optional-property-added

  • ○

    added the optional property _links/confirmation to the response with the 406 status (media type: application/problem+json)

    response-optional-property-added

  • ○

    added the optional property _links/confirmation to the response with the 409 status (media type: application/json)

    response-optional-property-added

  • ○

    added the optional property _links/confirmation to the response with the 409 status (media type: application/problem+json)

    response-optional-property-added

  • ○

    added the optional property _links/confirmation to the response with the 429 status (media type: application/json)

    response-optional-property-added

  • ○

    added the optional property _links/confirmation to the response with the 429 status (media type: application/problem+json)

    response-optional-property-added

  • ○

    added the optional property accounts/items/displayName to the response with the 200 status

    response-optional-property-added

  • ○

    added the optional property accounts/items/ownerName to the response with the 200 status

    response-optional-property-added

  • ○

    removed the authorised enum value from the accounts/items/balances/items/balanceType response property for the response status 200

    response-property-enum-value-removed

  This revision also has 3 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog

• Feb 10, 2021b51fe6ddb1fc▲24●19○5See the full diff
  • ▲

    the additionalErrors/items/detail response property's maxLength was increased from 500 to 512 for the response status 400 (media type: application/problem+json)

    response-property-max-length-increased

  • ▲

    the additionalErrors/items/detail response property's maxLength was increased from 500 to 512 for the response status 401 (media type: application/problem+json)

    response-property-max-length-increased

  • ▲

    the additionalErrors/items/detail response property's maxLength was increased from 500 to 512 for the response status 403 (media type: application/problem+json)

    response-property-max-length-increased

  • ▲

    the additionalErrors/items/detail response property's maxLength was increased from 500 to 512 for the response status 404 (media type: application/problem+json)

    response-property-max-length-increased

  • ▲

    the additionalErrors/items/detail response property's maxLength was increased from 500 to 512 for the response status 405 (media type: application/problem+json)

    response-property-max-length-increased

  • ▲

    the additionalErrors/items/detail response property's maxLength was increased from 500 to 512 for the response status 406 (media type: application/problem+json)

    response-property-max-length-increased

  • ▲

    the additionalErrors/items/detail response property's maxLength was increased from 500 to 512 for the response status 409 (media type: application/problem+json)

    response-property-max-length-increased

  • ▲

    the additionalErrors/items/detail response property's maxLength was increased from 500 to 512 for the response status 429 (media type: application/problem+json)

    response-property-max-length-increased

  • ▲

    the detail response property's maxLength was increased from 500 to 512 for the response status 400 (media type: application/problem+json)

    response-property-max-length-increased

  • ▲

    the detail response property's maxLength was increased from 500 to 512 for the response status 401 (media type: application/problem+json)

    response-property-max-length-increased

  • ▲

    the detail response property's maxLength was increased from 500 to 512 for the response status 403 (media type: application/problem+json)

    response-property-max-length-increased

  • ▲

    the detail response property's maxLength was increased from 500 to 512 for the response status 404 (media type: application/problem+json)

    response-property-max-length-increased

  • ▲

    the detail response property's maxLength was increased from 500 to 512 for the response status 405 (media type: application/problem+json)

    response-property-max-length-increased

  • ▲

    the detail response property's maxLength was increased from 500 to 512 for the response status 406 (media type: application/problem+json)

    response-property-max-length-increased

  • ▲

    the detail response property's maxLength was increased from 500 to 512 for the response status 409 (media type: application/problem+json)

    response-property-max-length-increased

  • ▲

    the detail response property's maxLength was increased from 500 to 512 for the response status 429 (media type: application/problem+json)

    response-property-max-length-increased

  • ▲

    the tppMessages/items/text response property's maxLength was increased from 500 to 512 for the response status 400 (media type: application/json)

    response-property-max-length-increased

  • ▲

    the tppMessages/items/text response property's maxLength was increased from 500 to 512 for the response status 401 (media type: application/json)

    response-property-max-length-increased

  • ▲

    the tppMessages/items/text response property's maxLength was increased from 500 to 512 for the response status 403 (media type: application/json)

    response-property-max-length-increased

  • ▲

    the tppMessages/items/text response property's maxLength was increased from 500 to 512 for the response status 404 (media type: application/json)

    response-property-max-length-increased

  • ▲

    the tppMessages/items/text response property's maxLength was increased from 500 to 512 for the response status 405 (media type: application/json)

    response-property-max-length-increased

  • ▲

    the tppMessages/items/text response property's maxLength was increased from 500 to 512 for the response status 406 (media type: application/json)

    response-property-max-length-increased

  • ▲

    the tppMessages/items/text response property's maxLength was increased from 500 to 512 for the response status 409 (media type: application/json)

    response-property-max-length-increased

  • ▲

    the tppMessages/items/text response property's maxLength was increased from 500 to 512 for the response status 429 (media type: application/json)

    response-property-max-length-increased

  • ●

    removed the optional property _links/confirmation from the response with the 400 status (media type: application/json)

    response-optional-property-removed

  • ●

    removed the optional property _links/confirmation from the response with the 400 status (media type: application/problem+json)

    response-optional-property-removed

  • ●

    removed the optional property _links/confirmation from the response with the 401 status (media type: application/json)

    response-optional-property-removed

  • ●

    removed the optional property _links/confirmation from the response with the 401 status (media type: application/problem+json)

    response-optional-property-removed

  • ●

    removed the optional property _links/confirmation from the response with the 403 status (media type: application/json)

    response-optional-property-removed

  • ●

    removed the optional property _links/confirmation from the response with the 403 status (media type: application/problem+json)

    response-optional-property-removed

  • ●

    removed the optional property _links/confirmation from the response with the 404 status (media type: application/json)

    response-optional-property-removed

  • ●

    removed the optional property _links/confirmation from the response with the 404 status (media type: application/problem+json)

    response-optional-property-removed

  • ●

    removed the optional property _links/confirmation from the response with the 405 status (media type: application/json)

    response-optional-property-removed

  • ●

    removed the optional property _links/confirmation from the response with the 405 status (media type: application/problem+json)

    response-optional-property-removed

  • ●

    removed the optional property _links/confirmation from the response with the 406 status (media type: application/json)

    response-optional-property-removed

  • ●

    removed the optional property _links/confirmation from the response with the 406 status (media type: application/problem+json)

    response-optional-property-removed

  • ●

    removed the optional property _links/confirmation from the response with the 409 status (media type: application/json)

    response-optional-property-removed

  • ●

    removed the optional property _links/confirmation from the response with the 409 status (media type: application/problem+json)

    response-optional-property-removed

  • ●

    removed the optional property _links/confirmation from the response with the 429 status (media type: application/json)

    response-optional-property-removed

  • ●

    removed the optional property _links/confirmation from the response with the 429 status (media type: application/problem+json)

    response-optional-property-removed

  • ●

    removed the optional property accounts/items/displayName from the response with the 200 status

    response-optional-property-removed

  • ●

    removed the optional property accounts/items/ownerName from the response with the 200 status

    response-optional-property-removed

  • ●

    added the new authorised enum value to the accounts/items/balances/items/balanceType response property for the response status 200

    response-property-enum-value-added

  • ○

    for the header request parameter PSU-Device-ID, the type/format was generalized from string/uuid to string/

    request-parameter-type-generalized

  • ○

    for the header request parameter X-Request-ID, the type/format was generalized from string/uuid to string/

    request-parameter-type-generalized

  • ○

    removed the SCA_INVALID enum value from the additionalErrors/items/code response property for the response status 400 (media type: application/problem+json)

    response-property-enum-value-removed

  • ○

    removed the SCA_INVALID enum value from the code response property for the response status 400 (media type: application/problem+json)

    response-property-enum-value-removed

  • ○

    removed the SCA_INVALID enum value from the tppMessages/items/code response property for the response status 400 (media type: application/json)

    response-property-enum-value-removed

  This revision also has 23 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog

• Feb 10, 20213cc5b6a584f1▲2●3○19See the full diff
  • ▲

    the accounts/items/details response property's maxLength was increased from 140 to 500 for the response status 200

    response-property-max-length-increased

  • ▲

    the accounts/items/name response property's maxLength was increased from 35 to 70 for the response status 200

    response-property-max-length-increased

  • ●

    added the new SCA_INVALID enum value to the additionalErrors/items/code response property for the response status 400 (media type: application/problem+json)

    response-property-enum-value-added

  • ●

    added the new SCA_INVALID enum value to the code response property for the response status 400 (media type: application/problem+json)

    response-property-enum-value-added

  • ●

    added the new SCA_INVALID enum value to the tppMessages/items/code response property for the response status 400 (media type: application/json)

    response-property-enum-value-added

  • ○

    added the optional property _links/confirmation to the response with the 400 status (media type: application/json)

    response-optional-property-added

  • ○

    added the optional property _links/confirmation to the response with the 400 status (media type: application/problem+json)

    response-optional-property-added

  • ○

    added the optional property _links/confirmation to the response with the 401 status (media type: application/json)

    response-optional-property-added

  • ○

    added the optional property _links/confirmation to the response with the 401 status (media type: application/problem+json)

    response-optional-property-added

  • ○

    added the optional property _links/confirmation to the response with the 403 status (media type: application/json)

    response-optional-property-added

  • ○

    added the optional property _links/confirmation to the response with the 403 status (media type: application/problem+json)

    response-optional-property-added

  • ○

    added the optional property _links/confirmation to the response with the 404 status (media type: application/json)

    response-optional-property-added

  • ○

    added the optional property _links/confirmation to the response with the 404 status (media type: application/problem+json)

    response-optional-property-added

  • ○

    added the optional property _links/confirmation to the response with the 405 status (media type: application/json)

    response-optional-property-added

  • ○

    added the optional property _links/confirmation to the response with the 405 status (media type: application/problem+json)

    response-optional-property-added

  • ○

    added the optional property _links/confirmation to the response with the 406 status (media type: application/json)

    response-optional-property-added

  • ○

    added the optional property _links/confirmation to the response with the 406 status (media type: application/problem+json)

    response-optional-property-added

  • ○

    added the optional property _links/confirmation to the response with the 409 status (media type: application/json)

    response-optional-property-added

  • ○

    added the optional property _links/confirmation to the response with the 409 status (media type: application/problem+json)

    response-optional-property-added

  • ○

    added the optional property _links/confirmation to the response with the 429 status (media type: application/json)

    response-optional-property-added

  • ○

    added the optional property _links/confirmation to the response with the 429 status (media type: application/problem+json)

    response-optional-property-added

  • ○

    added the optional property accounts/items/displayName to the response with the 200 status

    response-optional-property-added

  • ○

    added the optional property accounts/items/ownerName to the response with the 200 status

    response-optional-property-added

  • ○

    removed the authorised enum value from the accounts/items/balances/items/balanceType response property for the response status 200

    response-property-enum-value-removed

  This revision also has 3 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog

• Feb 10, 2021f324b23056bf▲2See the full diff
  • ▲

    for the header request parameter PSU-Device-ID, the type/format was changed from string/ to string/uuid

    request-parameter-type-changed

  • ▲

    for the header request parameter X-Request-ID, the type/format was changed from string/ to string/uuid

    request-parameter-type-changed

  This revision also has 10 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog

Of the 50 revisions, 1 has no diff computed.