# Contract Merchant Approval

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

Give merchant approval for contract activation. This endpoint can be used only in case it's agreed with Inbank. If used, then contract will not be activated before merchant's approval is given. This endpoint is relevant, for example, when there is a need to double-check that the required goods are available.

If the flow includes merchant approval, the merchant checks if the status of the contract is signed using the GET /partner/v2/shops/:shop_uuid/contracts/:contract_uuid request. When the contract is in the signed status, the merchant needs to approve or cancel the contract.

To approve the contract, the e-shop needs to know the credit contract UUID, which is in the response to the POST/:application_uuid/accept request.

The request does not require any parameters to be passed in its body.

Note that you can also approve contracts in the Partner Portal.

Endpoint: POST /partner/v2/shops/{shop_uuid}/contracts/{contract_uuid}/merchant_approval
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"

## 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 500 fields (application/json):

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


## Response 204 fields