v0.3.0 - MessageBird & Infobip providers

SmsBridge v0.3.0

This release adds MessageBird and Infobip support and strengthens provider conformance, delivery reporting, and failover safety across the SDK.

New Providers

MessageBird (UseMessageBird())

Sends through the MessageBird SMS API using AccessKey authentication, documented form-encoded requests, automatic GSM/Unicode data coding, and normalized API errors.

.UseMessageBird("messagebird", o =>
{
    o.AccessKey = "...";
    o.From = "MyApp";
})

Infobip (UseInfobip())

Uses Infobip's current SMS API v3 with an account-specific base URL and App API-key authentication.

.UseInfobip("infobip", o =>
{
    o.ApiKey = "...";
    o.BaseUrl = "https://xxxxx.api.infobip.com";
    o.From = "MyApp";
})

Provider Improvements

• Added delivery report parsing for Plivo, Sinch, and Telnyx.
• Added normalized delivery error codes and transient-failure metadata.
• Added optional delivery callback configuration for Twilio, Plivo, and Sinch.
• Added configurable regional Sinch API endpoints.
• Added automatic Unicode selection for Vonage messages outside GSM-7.
• Aligned provider request, response, and retry behavior with current official documentation.

Safer Failover

Automatic failover now avoids ambiguous connection and provider 5xx outcomes where the primary provider may already have accepted the message. This reduces the risk of duplicate SMS delivery.

Stats

• 136 tests passing
• Targets .NET 8 and .NET 9
• Release build: 0 warnings, 0 errors

Upgrading

dotnet add package SmsBridge --version 0.3.0

Full Changelog: v0.2.0...v0.3.0