#### [Abblix\.SharedSignals\.MinimalApi](https://www.abblix.com/en/docs/api/abblix-sharedsignals-minimalapi 'index')

## Abblix\.SharedSignals\.MinimalApi Namespace

| Classes | |
| :--- | :--- |
| [SharedSignalsEndpointOptions](https://www.abblix.com/en/docs/api/abblix-sharedsignals-minimalapi/Abblix.SharedSignals.MinimalApi.SharedSignalsEndpointOptions 'Abblix\.SharedSignals\.MinimalApi\.SharedSignalsEndpointOptions') | What the endpoint adapter leaves to the host: how an authenticated request maps to the receiver identity every management operation is scoped by\. Authentication itself stays with the host's middleware \- SSF 1\.0 Section 7\.1\.1 deliberately leaves the scheme open\. |
| [SharedSignalsEndpointRouteBuilderExtensions](https://www.abblix.com/en/docs/api/abblix-sharedsignals-minimalapi/Abblix.SharedSignals.MinimalApi.SharedSignalsEndpointRouteBuilderExtensions 'Abblix\.SharedSignals\.MinimalApi\.SharedSignalsEndpointRouteBuilderExtensions') | Maps the Shared Signals endpoints as Minimal API route handlers: the whole transmitter management surface in one call, its configuration document in another\. The handlers translate transport to the host\-agnostic services and nothing else \- authentication is the host's middleware, and the receiver identity is read per [SharedSignalsEndpointOptions](https://www.abblix.com/en/docs/api/abblix-sharedsignals-minimalapi/Abblix.SharedSignals.MinimalApi.SharedSignalsEndpointOptions 'Abblix\.SharedSignals\.MinimalApi\.SharedSignalsEndpointOptions')\.   Push delivery is not here. RFC 8935 carries any Security Event Token, not this framework's in particular, so its intake belongs to the package that owns the token - a receiver maps it with `MapPushDeliveryEndpoint` from `Abblix.SecurityEvents.MinimalApi`. |