--- title: "Returns the content of an signing basket object" method: GET path: "/v1/signing-baskets/{basketId}" tags: ["Signing Baskets Service (SBS)"] --- # Returns the content of an signing basket object `GET /v1/signing-baskets/{basketId}` Returns the content of a signing basket object. ## Path parameters - `basketId` string, required — Resource identification of the generated signing basket resource. ## Headers - `X-Request-ID` string, required - `Digest` string - `Signature` string - `TPP-Signature-Certificate` string, byte - `PSU-IP-Address` string, ipv4 - `PSU-IP-Port` string - `PSU-Accept` string - `PSU-Accept-Charset` string - `PSU-Accept-Encoding` string - `PSU-Accept-Language` string - `PSU-User-Agent` string - `PSU-Http-Method` 'GET' | 'POST' | 'PUT' | 'PATCH' | 'DELETE' - `PSU-Device-ID` string - `PSU-Geo-Location` string ## Response `200` OK - SigningBasketResponse200 — Body of the JSON response for a successful get signing basket request. * 'payments': payment initiations which shall be authorised through this signing basket. * 'consents': consent objects which shall be authorised through this signing basket. * 'transactionStatus': Only the codes RCVD, ACTC, RJCT are used. * '_links': The ASPSP might integrate hyperlinks to indicate next (authorisation) steps to be taken. - `payments` PaymentId[] — A list of paymentIds. - `consents` ConsentId[] — A list of consentIds. - `transactionStatus` 'ACSC' | 'ACTC' | 'PATC' | 'RCVD' | 'RJCT' | 'CANC', required — The transaction status is filled with codes of the ISO 20022 data table. Only the codes RCVD, PATC, ACTC, ACWC and RJCT are used: - 'ACSP': 'AcceptedSettlementInProcess' - All preceding checks such as technical validation and customer profile were successful and therefore the payment initiation has been accepted for execution. - 'ACTC': 'AcceptedTechnicalValidation' - Authentication and syntactical and semantical validation are successful. - 'ACWC': 'AcceptedWithChange' - Instruction is accepted but a change will be made, such as date or remittance not sent. - 'RCVD': 'Received' - Payment initiation has been received by the receiving agent. - 'RJCT': 'Rejected' - Payment initiation or individual transaction included in the payment initiation has been rejected. - `_links` LinksSigningBasket — A list of hyperlinks to be recognised by the TPP. The actual hyperlinks used in the response depend on the dynamical decisions of the ASPSP when processing the request. Remark: All links can be relative or full links, to be decided by the ASPSP. Type of links admitted in this response, (further links might be added for ASPSP defined extensions): * 'scaRedirect': In case of an SCA Redirect Approach, the ASPSP is transmitting the link to which to redirect the PSU browser. * 'scaOAuth': In case of a SCA OAuth2 Approach, the ASPSP is transmitting the URI where the configuration of the Authorisation Server can be retrieved. The configuration follows the OAuth 2.0 Authorisation Server Metadata specification. * 'startAuthorisation': In case, where an explicit start of the transaction authorisation is needed, but no more data needs to be updated (no authentication method to be selected, no PSU identification nor PSU authentication data to be uploaded). * 'startAuthorisationWithPsuIdentification': The link to the authorisation end-point, where the authorisation sub-resource has to be generated while uploading the PSU identification data. * 'startAuthorisationWithPsuAuthentication': The link to the authorisation end-point, where the authorisation sub-resource has to be generated while uploading the PSU authentication data. * 'startAuthorisationWithEncryptedPsuAuthentication': The link to the authorisation end-point, where the authorisation sub-resource has to be generated while uploading the encrypted PSU authentication data. * 'startAuthorisationWithAuthenticationMethodSelection': The link to the authorisation end-point, where the authorisation sub-resource has to be generated while selecting the authentication method. This link is contained under exactly the same conditions as the data element 'scaMethods' * 'startAuthorisationWithTransactionAuthorisation': The link to the authorisation end-point, where the authorisation sub-resource has to be generated while authorising the transaction e.g. by uploading an OTP received by SMS. * 'self': The link to the payment initiation resource created by this request. This link can be used to retrieve the resource data. * 'status': The link to retrieve the transaction status of the payment initiation. * 'scaStatus': The link to retrieve the scaStatus of the corresponding authorisation sub-resource. This link is only contained, if an authorisation sub-resource has been already created. - `scaRedirect` HrefType — Link to a resource. - `href` string — Link to a resource. - `scaOAuth` HrefType — Link to a resource. - `href` string — Link to a resource. - `startAuthorisation` HrefType — Link to a resource. - `href` string — Link to a resource. - `startAuthorisationWithPsuIdentification` HrefType — Link to a resource. - `href` string — Link to a resource. - `startAuthorisationWithPsuAuthentication` HrefType — Link to a resource. - `href` string — Link to a resource. - `startAuthorisationWithEncryptedPsuAuthentication` HrefType — Link to a resource. - `href` string — Link to a resource. - `startAuthorisationWithAuthenticationMethodSelection` HrefType — Link to a resource. - `href` string — Link to a resource. - `startAuthorisationWithTransactionAuthorisation` HrefType — Link to a resource. - `href` string — Link to a resource. - `self` HrefType — Link to a resource. - `href` string — Link to a resource. - `status` HrefType — Link to a resource. - `href` string — Link to a resource. - `scaStatus` HrefType — Link to a resource. - `href` string — Link to a resource. ## Other responses - `400` — Bad Request - `401` — Unauthorized - `403` — Forbidden - `404` — Not found - `405` — Method Not Allowed - `406` — Not Acceptable - `408` — Request Timeout - `409` — Conflict - `415` — Unsupported Media Type - `429` — Too Many Requests - `500` — Internal Server Error - `503` — Service Unavailable --- [API](https://skmtc.net/openbankingproject-ch/apis/swiss-nextgen-banking-api-framework.md) · [All operations](https://skmtc.net/openbankingproject-ch/apis/swiss-nextgen-banking-api-framework/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/openbankingproject-ch/swiss-nextgen-banking-api-framework/revisions/c32e86db40b4/schema)