GET v1/signing-baskets/{basketId}/status

Is contained if and only if the "Signature" element is contained in the header of the request.

The forwarded IP Accept header fields consist of the corresponding HTTP request Accept header fields between PSU and TPP, if available.

The forwarded IP Accept header fields consist of the corresponding HTTP request Accept header fields between PSU and TPP, if available.

The forwarded IP Accept header fields consist of the corresponding HTTP request Accept header fields between PSU and TPP, if available.

The forwarded IP Accept header fields consist of the corresponding HTTP request Accept header fields between PSU and TPP, if available.

Might be mandated in the ASPSP's documentation. Only used in a corporate context.

Might be mandated in the ASPSP's documentation. Only used in a corporate context.

UUID (Universally Unique Identifier) for a device, which is used by the PSU, if available. UUID identifies either a device or a device dependant application installation. In case of an installation identification this ID needs to be unaltered until removal from device.

The forwarded Geo Location of the corresponding http request between PSU and TPP if available.

Constraints: {'pattern': 'GEO:-?[0-9]{1,2}\\.[0-9]{6};-?[0-9]{1,3}\\.[0-9]{6}'}

HTTP method used at the PSU ? TPP interface, if available. Valid values are: * GET * POST * PUT * PATCH * DELETE

Constraints: {'enum': ['GET', 'POST', 'PUT', 'PATCH', 'DELETE']}

Client ID of the PSU in the ASPSP client interface. Might be mandated in the ASPSP's documentation. It might be contained even if an OAuth2 based authentication was performed in a pre-step or an OAuth2 based SCA was performed in an preceding AIS service in the same session. In this case the ASPSP might check whether PSU-ID and token match, according to ASPSP documentation.

Type of the PSU-ID, needed in scenarios where PSUs have several PSU-IDs as access possibility. In this case, the mean and use are then defined in the ASPSP's documentation.

The forwarded IP Address header field consists of the corresponding http request IP Address field between PSU and TPP.

The forwarded IP Port header field consists of the corresponding HTTP request IP Port field between PSU and TPP, if available.

The forwarded Agent header field of the HTTP request between PSU and TPP, if available.

A signature of the request by the TPP on application level. This might be mandated by ASPSP.

The certificate used for signing the request, in base64 encoding. Must be contained if a signature is contained.

ID of the request, unique to the call, as determined by the initiating party.

This identification of the corresponding signing basket object.