# New Order Event Notification

>  

Information about a new event in the systems

HOST: 

DIRECTION:

  


Endpoint: POST /v1/newEvent
Version: v.1.0.6

## Header parameters:

  - `X-App-Id` (string, required)
    An unique Identificator of the . The same ID must be sent to all  that implements this webhook.

  - `X-App-MerchantId` (string, required)
    Unique Identifier. Identifies the merchant in the different systems that the merchant will communicate.  
This id must be generated by the merchant's .

> The software service should ensure that merchantId is unique.

> If this is not possible, it is recommended to at least use a UUID.
    Example: "22815773000169-dbc7e35a-c936-4665-9e13-eb55eb8b6824"

  - `X-App-Signature` (string, required)
    SHA256 hash of the request body, using the client secret as the key, and finally encoded into Base64 format.

## Request fields (application/json):

  - `eventId` (string, required)
    A unique identifier of the event.

  - `eventType` (string, required)
    The event type.  for definitions of each type.
    Enum: "CREATED", "CONFIRMED", "DISPATCHED", "READY_FOR_PICKUP", "PICKED_UP", "DELIVERED", "CONCLUDED", "CANCELLATION_REQUESTED", "CANCELLED", "USER_REFUND_REQUEST", "REFUNDED", "REFUND_FAILED"

  - `orderId` (string, required)
    The unique identifier of the order. The order ID is generated by Keeta.

  - `orderURL` (string, required)
    The URL to get the order details

  - `createdAt` (string, required)
    Order creation date and time. 

(UTC date-time in ISO timestamp format. See [Guidelines](#section/General-Guidelines) for more info).

  - `sourceAppId` (string)
    This field must be filled in with the AppId of Keeta that originated the order. This field is to help the applications that will work as a Hub, intermediating the requests from  Keeta with the Software Service.

  - `virtualBrand` (string)
    This field can be used as an alternative id for the merchant, in cases where the same merchant has different identifications or brands (such as dark kitchens). It is important to note that Keeta or Software Hub must know this Id beforehand.

  - `metadata` (string)
    This field will be filled if event type is one of which [, ] and will contain the related details

## 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 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