Sentdm 0.6.0

Sent Dm C# API Library

The Sent Dm C# SDK provides convenient access to the Sent Dm REST API from applications written in C#.

It is generated with Stainless.

The REST API documentation can be found on docs.sent.dm.

Installation

Install the package from NuGet:

dotnet add package Sentdm

Requirements

This library requires .NET Standard 2.0 or later.

Usage

See the examples directory for complete and runnable examples.

using System.Collections.Generic;
using Sentdm;
using Sentdm.Models.Messages;

SentDmClient client = new();

MessageSendToPhoneParams parameters = new()
{
    PhoneNumber = "+1234567890",
    TemplateID = "7ba7b820-9dad-11d1-80b4-00c04fd430c8",
    TemplateVariables = new Dictionary<string, string>()
    {
        { "name", "John Doe" }, { "order_id", "12345" }
    },
};

await client.Messages.SendToPhone(parameters);

Client configuration

Configure the client using environment variables:

using Sentdm;

// Configured using the SENT_DM_API_KEY, SENT_DM_SENDER_ID and SENT_DM_BASE_URL environment variables
SentDmClient client = new();

Or manually:

using Sentdm;

SentDmClient client = new()
{
    ApiKey = "My API Key",
    SenderID = "My Sender ID",
};

Or using a combination of the two approaches.

See this table for the available options:

Modifying configuration

To temporarily use a modified client configuration, while reusing the same connection and thread pools, call WithOptions on any client or service:

using System;

await client
    .WithOptions(options =>
        options with
        {
            BaseUrl = "https://example.com",
            Timeout = TimeSpan.FromSeconds(42),
        }
    )
    .Messages.SendToPhone(parameters);

Using a with expression makes it easy to construct the modified options.

The WithOptions method does not affect the original client or service.

Requests and responses

To send a request to the Sent Dm API, build an instance of some Params class and pass it to the corresponding client method. When the response is received, it will be deserialized into an instance of a C# class.

For example, client.Contacts.List should be called with an instance of ContactListParams, and it will return an instance of Task<ContactListResponse>.

Raw responses

The SDK defines methods that deserialize responses into instances of C# classes. However, these methods don't provide access to the response headers, status code, or the raw response body.

To access this data, prefix any HTTP method call on a client or service with WithRawResponse:

var response = await client.WithRawResponse.Messages.SendToPhone(parameters);
var statusCode = response.StatusCode;
var headers = response.Headers;

The raw HttpResponseMessage can also be accessed through the RawMessage property.

For non-streaming responses, you can deserialize the response into an instance of a C# class if needed:

using System;
using Sentdm.Models.Contacts;

var response = await client.WithRawResponse.Contacts.List(parameters);
ContactListResponse deserialized = await response.Deserialize();
Console.WriteLine(deserialized);

Error handling

The SDK throws custom unchecked exception types:

• SentDmApiException: Base class for API errors. See this table for which exception subclass is thrown for each HTTP status code:

Additionally, all 4xx errors inherit from SentDm4xxException.

false

• SentDmIOException: I/O networking errors.

• SentDmInvalidDataException: Failure to interpret successfully parsed data. For example, when accessing a property that's supposed to be required, but the API unexpectedly omitted it from the response.

• SentDmException: Base class for all exceptions.

Network options

Retries

The SDK automatically retries 2 times by default, with a short exponential backoff between requests.

Only the following error types are retried:

• Connection errors (for example, due to a network connectivity problem)
• 408 Request Timeout
• 409 Conflict
• 429 Rate Limit
• 5xx Internal

The API may also explicitly instruct the SDK to retry or not retry a request.

To set a custom number of retries, configure the client using the MaxRetries method:

using Sentdm;

SentDmClient client = new() { MaxRetries = 3 };

Or configure a single method call using WithOptions:

await client
    .WithOptions(options =>
        options with { MaxRetries = 3 }
    )
    .Messages.SendToPhone(parameters);

Timeouts

Requests time out after 1 minute by default.

To set a custom timeout, configure the client using the Timeout option:

using System;
using Sentdm;

SentDmClient client = new() { Timeout = TimeSpan.FromSeconds(42) };

Or configure a single method call using WithOptions:

using System;

await client
    .WithOptions(options =>
        options with { Timeout = TimeSpan.FromSeconds(42) }
    )
    .Messages.SendToPhone(parameters);

Undocumented API functionality

The SDK is typed for convenient usage of the documented API. However, it also supports working with undocumented or not yet supported parts of the API.

Response validation

In rare cases, the API may return a response that doesn't match the expected type. For example, the SDK may expect a property to contain a string, but the API could return something else.

By default, the SDK will not throw an exception in this case. It will throw SentDmInvalidDataException only if you directly access the property.

If you would prefer to check that the response is completely well-typed upfront, then either call Validate:

var contacts = client.Contacts.List(parameters);
contacts.Validate();

Or configure the client using the ResponseValidation option:

using Sentdm;

SentDmClient client = new() { ResponseValidation = true };

Or configure a single method call using WithOptions:

using System;

var contacts = await client
    .WithOptions(options =>
        options with { ResponseValidation = true }
    )
    .Contacts.List(parameters);

Console.WriteLine(contacts);

Semantic versioning

This package generally follows SemVer conventions, though certain backwards-incompatible changes may be released as minor versions:

1. Changes to library internals which are technically public but not intended or documented for external use. (Please open a GitHub issue to let us know if you are relying on such internals.)
2. Changes that we do not expect to impact the vast majority of users in practice.

We take backwards-compatibility seriously and work hard to ensure you can rely on a smooth upgrade experience.

We are keen for your feedback; please open an issue with questions, bugs, or suggestions.