Changes to Consent status request

Changed in 6 of the 50 revisions of this API.▲31●25○50

1. Feb 25, 202141f56d33cdbf○1
2. Feb 22, 202108bfa9265493▲1
3. Feb 19, 20210d82c4699548▲4●4○26
4. Feb 10, 2021b51fe6ddb1fc▲24●17○6
5. Feb 10, 20213cc5b6a584f1●4○17
6. Feb 10, 2021f324b23056bf▲2

What changed

• Feb 25, 202141f56d33cdbf○1See the full diff
  • ○

    endpoint added

    endpoint-added

• Feb 22, 202108bfa9265493▲1See the full diff
  • ▲

    api path removed without deprecation

    api-path-removed-without-deprecation

• Feb 19, 20210d82c4699548▲4●4○26See the full diff
  • ▲

    added the new path request parameter account-id

    new-request-path-parameter

  • ▲

    added the new required header request parameter Consent-ID

    new-required-request-parameter

  • ▲

    added the new required query request parameter bookingStatus

    new-required-request-parameter

  • ▲

    removed the required property consentStatus from the response with the 200 status

    response-required-property-removed

  • ●

    deleted the path request parameter consentId

    request-parameter-removed

  • ●

    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 new optional query request parameter dateFrom

    new-optional-request-parameter

  • ○

    added the new optional query request parameter dateTo

    new-optional-request-parameter

  • ○

    added the new optional query request parameter deltaList

    new-optional-request-parameter

  • ○

    added the new optional query request parameter entryReferenceFrom

    new-optional-request-parameter

  • ○

    added the new optional query request parameter withBalance

    new-optional-request-parameter

  • ○

    added the optional property _links to the response with the 200 status

    response-optional-property-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 balances to the response with the 200 status

    response-optional-property-added

  • ○

    added the optional property cardAccount to the response with the 200 status

    response-optional-property-added

  • ○

    added the optional property cardTransactions to the response with the 200 status

    response-optional-property-added

  • ○

    added the optional property debitAccounting to the response with the 200 status

    response-optional-property-added

  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●17○6See 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 psuMessage from the response with the 200 status

    response-optional-property-removed

  • ○

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

    request-parameter-type-generalized

  • ○

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

    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

  • ○

    removed the partiallyAuthorised enum value from the consentStatus response property for the response status 200

    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●4○17See the full diff
  • ●

    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 new partiallyAuthorised enum value to the consentStatus response property for the response status 200

    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 psuMessage to the response with the 200 status

    response-optional-property-added

  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 format changed from no format to uuid

    request-parameter-type-changed

  • ▲

    for the header request parameter X-Request-ID, the format changed from no format to 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.