# Data Event List

Schema: #/components/schemas/data_event_list

Method: SCHEMA
Version: 2.7
Security: bearerAuth

## Schema fields:

  - `type` (string)
    The type of the object
    Enum: "event.list"

  - `events` (array)
    A list of data events

  - `events.type` (string)
    The type of the object
    Enum: "event"

  - `events.event_name` (string, required)
    The name of the event that occurred. This is presented to your App's admins when filtering and creating segments - a good event name is typically a past tense 'verb-noun' combination, to improve readability, for example `updated-plan`.
    Example: invited-friend

  - `events.created_at` (integer, required)
    The time the event occurred as a UTC Unix timestamp
    Example: 1671028894

  - `events.user_id` (string)
    Your identifier for the user.
    Example: 314159

  - `events.id` (string)
    Your identifier for a lead or a user.
    Example: 8a88a590-e1c3-41e2-a502-e0649dbf721c

  - `events.intercom_user_id` (string)
    The Intercom identifier for the user.
    Example: 63a0979a5eeebeaf28dd56ba

  - `events.email` (string)
    An email address for your user. An email should only be used where your application uses email to uniquely identify users.
    Example: frodo.baggins@example.com

  - `events.metadata` (object)
    Optional metadata about the event.
    Example: {"invite_code":"ADDAFRIEND"}

  - `pages` (object)
    Pagination

  - `pages.next` (string)
    Example: https://api.intercom.io/events?per_page=2&before=1389913941064&intercom_user_id=63a0979a5eeebeaf28dd56ba&type=user"

  - `pages.since` (string)
    Example: https://api.intercom.io/events?intercom_user_id=63a0979a5eeebeaf28dd56ba&type=user&since=1389913941065

