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

## SecurityEventTokenMediaTypes Class

The media type a SET travels under \(RFC 8417 Section 7\.3\)\. RFC 8935 Section 2\.1 requires it as
the Content\-Type of a push transmission request; everything else in delivery \-
poll requests, poll responses, error bodies \- is plain application/json, for which the
framework's own constant serves\.

```csharp
public static class SecurityEventTokenMediaTypes
```

Inheritance [System\.Object](https://learn.microsoft.com/en-us/dotnet/api/system.object 'System\.Object') → SecurityEventTokenMediaTypes
### Fields

## SecurityEventTokenMediaTypes\.SecurityEventToken Field {#Abblix.SecurityEvents.Delivery.SecurityEventTokenMediaTypes.SecurityEventToken}

"application/secevent\+jwt": the full media type, as an HTTP header carries it\. The token's
"typ" header uses the short spelling instead \- that value lives on
[TokenType](https://www.abblix.com/en/docs/api/abblix-securityevents/Abblix.SecurityEvents.SecurityEventToken#Abblix.SecurityEvents.SecurityEventToken.TokenType 'Abblix\.SecurityEvents\.SecurityEventToken\.TokenType'), and RFC 7515 Section 4\.1\.9 is what makes the
two the same name; composing the long form from the short one keeps that a fact rather
than a coincidence of two literals\.

```csharp
public const string SecurityEventToken = "application/secevent+jwt";
```

#### Field Value
[System\.String](https://learn.microsoft.com/en-us/dotnet/api/system.string 'System\.String')