# Message configuration

## Supported payload types

Each destination type has specific schema structures tailored to its supported payload types. For generic HTTPS, a default output type exists.

| Payload type | `payload_type` API value | Description           |
| ------------ | ------------------------ | --------------------- |
| **Default**  | `default`                | Default payload type. |

## Default payload type

| UI label    | API field name | Type            | Required | Description                                                                                            |
| ----------- | -------------- | --------------- | -------- | ------------------------------------------------------------------------------------------------------ |
| **Headers** | `headers`      | `KeyValuePairs` | false    | HTTP header to include in the request. Represents a JSON object where each key maps to a string value. |
| **Body**    | `body`         | `JSONObject`    | false    | JSON object representing the body of the request.                                                      |

Note

The message configuration should include only the notification content and details related to the event. Authentication and connection settings, such as API keys, should be defined in the [connector configuration](https://coralogix.com/docs/user-guides/notification-center/destination-types/https/connector-config/index.md).

## Next steps

Configure the Generic HTTPS destination type for OpsGenie or Jira Service Management in [OpsGenie and JSM configuration via HTTPS](https://coralogix.com/docs/user-guides/notification-center/destination-types/https/support-for-opsgenie/index.md).