# New Merchant Update Notification


>  


Information about a update in the systems.

This endpoint can be used in the following ways:

  
This will force Keeta to make a new request to the GET /v1/merchant endpoint to update all the merchant information.

  
This will force the opening or closing of the merchant within Keeta, without forcing a new GET /v1/merchant call.

  
This will force  Keeta to update only the sent objects, without forcing a new GET /v1/merchant call.
> 
> 1- Please do not pass  and & at the same time. When  has a value, the request will be regarded as updating only merchant status, and & will be ignored.Please update merchant status and other entity separately. 
> 2- When the  field is populated, the  field cannot be empty.
> 3- It is recommended not to pass an empty body, but to pass a specific entity to be updated to avoid invalid update operations.
> 4- An item must have either a delivery price or a pickup price. Currently, item with only  price is not permitted.
> 5- The business status of a store is determined by many factors (business hours, number of items available for sale, merchant status, etc.).

  
HOST:   

DIRECTION:

  


Endpoint: POST /v1/merchantUpdate/{merchantId}
Version: v.1.0.6
Security: OAuth2, Sig

## Path parameters:

  - `merchantId` (string, required)
    The unique identifier of the merchant. The merchantId is generated by the Software Service.

## Request fields (application/json):

  - `merchantStatus` (string)
    Indicates if the Merchant is Avaliable or Unavaliable. Only use this type when you must close (disable) the merchant due to an unexpected event and you don't know when the service will be re-established (e.g. do not use for holidays).
    Enum: "AVAILABLE", "UNAVAILABLE"

  - `entityType` (string)
    The entity type of the updated object.

## Response 400 fields (application/problem+json):

  - `title` (string, required)
    Short description of the problem.
    Example: "Unexpected error"

  - `status` (integer, required)
    HTTP code of the returned status.
    Example: 500

## Response 401 fields (application/problem+json):

  - `title` (string, required)
    Short description of the problem.
    Example: "Unexpected error"

  - `status` (integer, required)
    HTTP code of the returned status.
    Example: 500

## Response 403 fields (application/problem+json):

  - `title` (string, required)
    Short description of the problem.
    Example: "Unexpected error"

  - `status` (integer, required)
    HTTP code of the returned status.
    Example: 500

## Response 404 fields (application/problem+json):

  - `title` (string, required)
    Short description of the problem.
    Example: "Unexpected error"

  - `status` (integer, required)
    HTTP code of the returned status.
    Example: 500

## Response 503 fields (application/problem+json):

  - `title` (string, required)
    Short description of the problem.
    Example: "Unexpected error"

  - `status` (integer, required)
    HTTP code of the returned status.
    Example: 500