Channel Provider Registry
Register, discover and test notification channels through SDK v2.
Register and discover channels
ChannelProviderRegistry maps manifest driver keys to ChannelDriver implementations. Core registers email, database and broadcast. Plugins declare channel_drivers[] and call PluginRegistrar::channelDriver(). The registration key must equal driver->key(); registration also rejects two drivers for one logical channel.
drivers() returns config/address schemas and labels; keys(), channels(), has(), hasChannel(), packageFor() and isPluginDriver() support discovery. logicalChannelOptions() returns labels for workflow and preference controls, mapping the core aliases to email and in_app. No provider names are hard-coded.
resolve(driverKey: ...) or resolve(channel: ...) returns a driver. Plugin calls are wrapped in their owning execution scope. Drivers implement addressField(): ?ChannelAddressFieldData and send(): ChannelSendResult in SDK v2. test(TestChannelProviderData) validates the recipient against that field and uses its saved providerId for scoped HTTP.
send(ChannelSendData) is a low-level queued driver call:
$registry->send(new ChannelSendData(
driverKey: 'acme.card', notifiableId: 1, notifiableType: 'account',
subject: 'Ready', body: 'Your record is ready.',
config: $config,
));
Normal notifications use SendNotification → RegistryBackedNotificationChannel, which owns provider selection, addresses, templates, opt-out and log transitions. The bridge selects a matching warehouse before an unscoped row, with default rows first. Disabled drivers leave saved rows inert and suppress queued deliveries. Re-enabling restores the registered driver without exposing its encrypted configuration.
See Plugin Channel Providers for the complete delivery pipeline, SDK-only Acme Notify examples, authentication, callbacks and upgrade instructions.