# Contract Signing

POST /partner/v2/shops/:shop_uuid/contracts/:contract_uuid/signings

After the customer accepts the credit offer and has reviewed the contract, they can proceed to contract signing which is done via the POST /partner/v2/shops/:shop_uuid/contracts/:contract_uuid/signings endpoint. There are the following signing methods available:

- redirect - the method is used for contract signing by redirecting the client to a separate environment. The response to this request returns the URL to which the client should be redirected. The signing environment can be built into your site as an iFrame or just opened in a new browser tab. This signing method is available for the Inbank Hire Purchase payment product.
- digital - the method is used in cases when the partner has a separate signing solution. The request with the digital signing method is used as a confirmation that signing has been successful. This signing method is available for the Inbank Hire Purchase payment product.
- paper - the method is used if you are collecting paper contracts signed by the customer. This signing method is available for Split into parts and Inbank Hire Purchase payment products.
- sms - with this method the signing is done using an SMS code. After you send the request, the customer will receive an SMS with the code from Inbank. After that, the code is sent over to Inbank for confirmation via the PATCH /contracts/:contract_uuid/signings request. This signing method is available for the Split into Parts payment products.
- send_to_signing_sms and send_to_signing_email methods send a link to the Inbank environment where customers can sign the contract. The link is sent to the mobile number / email address which was indicated in the credit application. This signing method is available for the Inbank Hire Purchase payment product.

Endpoint: POST /partner/v2/shops/{shop_uuid}/contracts/{contract_uuid}/signings
Security: bearerAuth

## Path parameters:

  - `shop_uuid` (string, required)
    The unique identifier of the shop.
    Example: "a93f1f44-d5dd-4469-bfcc-c1de9e969213"

  - `contract_uuid` (string, required)
    The unique identifier of the contract.
    Example: "788ec8c4-c497-470b-8505-2303f151d427"

## Request fields (application/json):

  - `method` (string, required)
    The signing method to be used.
    Enum: "paper", "digital", "sms", "sms_nexmo", "redirect", "payment", "send_to_signing_email", "send_to_signing_sms"

## Response 201 fields (application/json):

  - `contract` (object)

  - `contract.uuid` (string)
    The unique identifier of the contract.
    Example: "6b9fd89c-ddbd-4e27-9291-3de50d000000"

  - `contract.number` (string)
    Contract number.
    Example: 89003110000

  - `contract.customer_signed` (string)
    Customer signed.

  - `contract.redirect_url` (string)
    Redirect URL.
    Example: "https://gateway-sandbox.dokobit.com/signing/e1a14498554d876"

## Response 401 fields (application/json):

  - `message` (string)
    Unauthorized
    Example: "unauthorized"

## Response 403 fields (application/json):

  - `message` (string)
    Unauthorized access
    Example: "User is not authorized to access this resource with an explicit deny"

## Response 404 fields (application/json):

  - `message` (string)
    Not found

## Response 422 fields (application/json):

  - `message` (string)
    Unprocessable Entity

## Response 500 fields (application/json):

  - `message` (string)
    Internal server error
    Example: "internal_server_error"