#### [Abblix\.SecurityEvents](https://www.abblix.com/en/docs/api/abblix-securityevents 'index')
### [Abblix\.SecurityEvents\.Events](https://www.abblix.com/en/docs/api/abblix-securityevents/Abblix.SecurityEvents.Events 'Abblix\.SecurityEvents\.Events')

## IEventPayload Interface

Marks a type as the payload of an event statement \(RFC 8417 Section 2: the "payload" is the
JSON object paired with an event identifier inside the "events" claim\)\.

```csharp
public interface IEventPayload
```

Derived  
↳ [UnknownEventPayload](https://www.abblix.com/en/docs/api/abblix-securityevents/Abblix.SecurityEvents.Events.UnknownEventPayload 'Abblix\.SecurityEvents\.Events\.UnknownEventPayload')

### Remarks
The interface carries no members on purpose\. A payload's shape belongs to the profiling
specification that defines the event \(RFC 8417 Section 1\.2\), so the only thing all payloads
share is BEING one \- and the marker is what lets [EventTypeRegistry](https://www.abblix.com/en/docs/api/abblix-securityevents/Abblix.SecurityEvents.Events.EventTypeRegistry 'Abblix\.SecurityEvents\.Events\.EventTypeRegistry') map event
identifier URIs to types without accepting arbitrary classes, the way a string\-to\-Type
dictionary alone would\.