# TalonOne::NewEventType ## Properties Name | Type | Description | Notes ------------ | ------------- | ------------- | ------------- **application_ids** | **Array<Integer>** | The IDs of the applications that are related to this entity. | **title** | **String** | The human-friendly display name for this event type. Use a short, past-tense, description of the event. | **name** | **String** | The machine-friendly canonical name for this event type. This will be used in URLs, and cannot be changed after an event type has been created. | **description** | **String** | An explanation of when the event type is triggered. Write this with a campaign manager in mind. For example: > The \"Payment Accepted\" event is triggered after successful processing of a payment by our payment gateway. | **mime_type** | **String** | This defines how the request payload will be parsed before your handler code is run. | **example_payload** | **String** | It is often helpful to include an example payload with the event type definition for documentation purposes. | [optional] **schema** | [**Object**](.md) | It is strongly recommended to define a JSON schema that will be used to perform structural validation of request payloads after parsing. | [optional] **handler_language** | **String** | The language of the handler code. Currently only `\"talang\"` is supported. | [optional] **handler** | **String** | Code that will be run after successful parsing & validation of the payload for this event. This code _may_ choose to evaluate campaign rules. | **version** | **Integer** | The version of this event type. When updating an existing event type this must be **exactly** `currentVersion + 1`. | ## Code Sample ```ruby require 'TalonOne' instance = TalonOne::NewEventType.new(application_ids: null, title: null, name: null, description: null, mime_type: null, example_payload: null, schema: null, handler_language: null, handler: null, version: null) ```