# Get New Events

Polls events for any orders from merchants associated with the authenticated user.  
Each event received from this endpoint must be properly acknowledged, otherwise it will continue to be returned on further requests.

> Important: The software service  to register the store before calling this endpoint, otherwise the polling endpoint will not be able to obtain the events.


HOST: 

DIRECTION:

  


Endpoint: GET /v1/events:polling
Version: v.1.0.6
Security: OAuth2, Sig

## Header parameters:

  - `x-polling-merchants` (array)
    Subset of merchants to fetch events from. Must either be omitted or non-empty.
    Example: ["22815773000169-dbc7e35a-c936-4665-9e13-eb55eb8b6824"]

## Query parameters:

  - `eventType` (array)
    Desired event types. All other events not selected by group will be automatically acknowledged and omitted from the response. 
Must either be omitted or non-empty.


>  : Order created.\
>  : Order confirmed.       
> : Order ready for pickup by the customer or delivery person.\
>  : Order went out for delivery.\
>  : Order has been picked up by customer.\
>  : Order has been delivered to customer.\
>  : Order completed.\
>  : Sent by the Software Service to Keeta.\
>  : When the order is actually cancelled.\
>  : Sent by Keeta to the Software Service.\
>  : Sent by Keeta to the Software Service.\
>  : Sent by Keeta to the Software Service.
    Enum: "CREATED", "CONFIRMED", "DISPATCHED", "READY_FOR_PICKUP", "PICKED_UP", "DELIVERED", "CONCLUDED", "CANCELLATION_REQUESTED", "CANCELLED", "USER_REFUND_REQUEST", "REFUNDED", "REFUND_FAILED"

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