Hello Sinch Developer Community!
The topic for today is our SDK support for .NET. We want to provide a closer look at our philosophy behind the design, how we’re tailoring this to .NET developers, and to provide a space for questions and comments related to .NET.
When we started out with the design of the new SDK components, we wanted to ensure we were building them with the specific language first and foremost. After that, our focus was to keep the design simple for users that only want to leverage specific API calls they use but ensure customizability and future-proof access to other parts of our infrastructure.
Within each SDK we’ve added common capabilities to further streamline the interaction with our platform:
With all these common items, we hope to build out consistent frameworks with functionality all users require.
Another goal of ours while designing this new .NET SDK was to mimic our REST APIs as much as possible, while still providing .NET developer experience. We also use IDE type hints which, along with the REST API specification, allows the user to perform most API interactions without the need to use reference documentation.
Discoverability is one of the key components of great DX, hence .NET SDK namespaces are small and specific yet descriptive.
var response = await sinchClient.Numbers.Available.List(new ListAvailableNumbersRequest()
Type = Types.Mobile,
RegionCode = "US"B
The main client class organizes the Sinch product portfolio (called domains within SDK) and its features into hierarchy that produces an API that is easy to read and discover.
No third-party libraries are used by the NET SDK.
Currently, supported .NET versions: NET 6, NET 7, NET 8. New stable versions will be added in the future, while older/EOL versions will be deprecated.
For now, SMS, Numbers, , Voice, and Verification APIs are supported, with other public Sinch APIs to be added soon.
For further details and to download our SDK, please refer to: