# Retrieve open hit events of the specified contact

Endpoint: GET /targets/{id}/events/hits/open
Version: 8.1.0

## Path parameters:

  - `id` (string, required)
    The id of the contact to retrieve events from.

## Query parameters:

  - `start` (string)
    Defines a start date filter  
Specify this parameter to retrieve only events with a timestamp greater than or equal to the specified value  
You can use an ISO format date or a timestamp

  - `end` (string)
    Defines an end date filter  
Specify this parameter to retrieve only events with a timestamp less than the specified value  
You can use an ISO format date or a timestamp

  - `sort` (string)
    Defines a sort order applied on events timestampBy default, events are unordered and may not streamed in the same order between two requestsYou should use this query parameter if you want to guarantee the sort order of events
    Enum: "asc", "desc"

  - `classification` (string)
    Defines a classifications filter 
Specify this parameter to retrieve only events with robot classification or all hits 
You can use a list of string separeted with ',' for example classifications=genericrobot,mpp,gsr (mpp: Apple Mail Privacy Proxy, gsr: Google Security Robot) 
You should use this query parameter if you want to get the hit events classified as robot

## Header parameters:

  - `X-Key` (string, required)
    A unique API key used to authenticate requests to the NP6 platform. 
This key must be included in every API call to validate the identity and permissions of the client. 
Keep your API key secure and do not expose it in public code or logs.

## Response 200 fields (application/json):

  - `id` (string)
    Uuid of the event

  - `timestamp` (integer)
    Publication timestamp of the event  
This is the number of milliseconds elapsed since January 1, 1970 00:00:00 UTC.

  - `identity` (object)
    Underlying identity of the event

  - `identity.type` (string)

  - `source` (object)
    Source of the event


## Response 401 fields

## Response 404 fields