Skip to content
This repository has been archived by the owner on Jul 29, 2022. It is now read-only.

.NET wrapper for the CakeMail API

License

Notifications You must be signed in to change notification settings

Jericho/CakeMail.RestClient

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

CakeMail.RestClient

License Build status Coverage Status CodeFactor FOSSA Status

About

CakeMail.RestClient is a C# client for the CakeMail service through its RESTful API.

Nuget

CakeMailRestAPI is available as a Nuget package.

NuGet Version

Pre-release packages are available on my MyGet feed:

MyGet Pre Release

Release Notes

  • 7.1
    • Add support for dynamic content which CakeMail already supports when sending bulk emails. In other words, you can have IF ... ELSEIF ... ELSE ... ENDIF in your HTML content, text content and subject as well.
    • Please keep in mind the following the rules established by CakeMail for dynamic content:
      • IF, ELSEIF, ELSE and ENDIF must be upper case which means that [IF `myfield` = "myValue"] is valid but [if `myfield` = "myValue"] is not.
      • square bracket is the delimeter which means that [IF `myfield` = "myValue"] is valid but {IF `myfield` = "myValue"} is not.
      • the name of the data field must be surrounded by back ticks (not to be confused with single quotes) which means that [IF `firstname` = "Bob"] is valid but [IF 'firstname' = "Bob"] is not.
      • you can only compare a field to a constant value and you can't compare a field to another field which means that [IF `firstname` = "Bob"] is valid but [IF `firstname` = `nickname`] is not.
      • the constant value must be surrounded with double quotes when it's a string which means that [IF `firstname` = "Bob"] is valid but [IF `firstname` = 'Bob'] is not.
      • the constant value must not be surrounded by any quotes when it's a numeric value which means that [IF `age` >= 18] is valid.
      • the data field must be on the left side of the comparison which means that [IF `gender` = \"Male\"] is valid but [IF \"Male\" = `gender`] is not.
      • you can have multiple conditions seperated by AND or OR which means that IF `firstname` = "Bob" AND `lastname` = "Smith"] is valid.
      • the acceptable operators when comparing a field to a string value: <, <=, =, !=, >=, >, LIKE and NOT LIKE
      • the acceptable operators when comparing a field to a mumeric value: <, <=, =, !=, >= and >
var subject = "Special sale ends today";
var html = "<html><body>[IF `gender` = \"Male\"]Men's clothing is on sale[ELSE]Women's clothing is on sale[ENDIF]</body></html>";
var text = "[IF `gender` = \"Male\"]Men's clothing is on sale[ELSE]Women's clothing is on sale[ENDIF]";
var mergeData = new Dictionary<string, object>
{
    { "gender", "Male" }
};
var sent = await client.Relays.SendWithoutTrackingAsync(userKey, "recipient@example.com", subject, html, text, "you@yourcompany.com", "Your name", mergeData, null, null, clientId, cancellationToken).ConfigureAwait(false);
  • 7.0
    • Add support for merge fields in html, text content and subject line when sending an email. CakeMail already supports merge fields when sending bulk emails.
    • Please keep in mind the following the rules for merge fields:
      • square bracket is the delimeter which means that [firstname] is valid but {firstname} is not.
      • you can specify a default value (sometimes called "fallback value") by adding a comma after the field name followed by the desired value. This default value is used when the value for the data field is undefined. For example: Dear [firstname, friend] will result in Dear friend if the firstname field is omitted or contains a null value for the current recipient.
      • you can use [TODAY] to print the current date. Please note that [NOW] and [DATE] are also acceptable.
      • when the merge field contains a numeric value or a datetime or when you use the [TODAY] merge field, you can specify a format string by adding the pipe character after the field name followed by the desired format string like so: [TODAY | MMM d yyyy].
      • Documentation for datetime format string
      • Documentation for numeric format string
var subject = "Special sale ends today";
var html = "<html><body>Dear [firstname, friend], our annual sale ends <b>today</b> [TODAY | MMMM d].</body></html>";
var text = "[salutation] [lastname], our annual sale ends <b>today</b> [TODAY | MMMM d].";
var mergeData = new Dictionary<string, object>
{
    { "salutation", "Mr." },
    { "firstname", "Bob" },
    { "lastname", "Smith" }
};
var sent = await client.Relays.SendWithoutTrackingAsync(userKey, "recipient@example.com", subject, html, text, "you@yourcompany.com", "Your name", mergeData, null, null, clientId, cancellationToken).ConfigureAwait(false);
  • 6.0

    • Fix bug when retrieving a Client record and the 'last_activity' field contains empty date
    • Add support for .NET STANDARD 1.3
    • Replace RestSharp with PathosChild.Http.FluentClient
    • Switch unit testing to xUnit
    • Implement GitFlow and repeatable build process
  • 5.0

    • Upgraded to .NET 4.5.2
  • 4.0

    • All methods are now async.
    • You can pass a cancellation token when invoking an async method.

This means, for example, that the following v3.0 call:

var count = cakeMail.Campaigns.GetCount(userKey, MailingStatus.Ongoing);

Has been replaced with the following v4.0 call :

var count = await cakeMail.Campaigns.GetCountAsync(userKey, MailingStatus.Ongoing);
  • 3.0
    • Methods are now logically grouped in separate resources. For instance, all methods related to users are grouped in a resource called 'Users', all methods related to campaigns are grouped in a resource called 'Campaigns', and so on.
    • Methods have been renamed to avoid repetition. For example, GetCampaignsCount has been renamed GetCount off of the new 'Campaigns' resource.

This means, for example, that the following v2.0 call:

var count = cakeMail.GetCampaignsCount(userKey, MailingStatus.Ongoing);

Has been replaced with the following v3.0 call :

var count = cakeMail.Campaigns.GetCount(userKey, MailingStatus.Ongoing);
  • 2.0

    • Unique identifiers changed to 'long' instead of 'int'.
    • "Magic strings" replaced with enums. For example, instead of specifying sort direction with 'asc' and 'desc', you can now use SortDirection.Ascending and SortDirection.Descending.
    • Fix bug in CreateTemplateCategory which prevents creating new categories
    • Fix bug in DeleteTemplateCategory which causes an exception to be thrown despite the fact the category was successfuly deleted
    • Fix bug in GetListMembers which causes exception: 'Json does not contain property members'
    • Fix GetTriggerLinksLogs
    • Added XML comments file for convenient intellisense in Visual Studio
  • 1.0

    • Initial release

Installation

The easiest way to include CakeMail.RestClient in your C# project is by grabing the nuget package:

PM> Install-Package CakeMail.RestClient

Once you have the CakeMail.RestClient library properly referenced in your project, add the following namespace:

using CakeMail.RestClient;

Usage

Login

var apiKey = "... your api key ...";
var userName = "youremail@whatever.com";
var password = "yourpassword";

var cakeMail = new CakeMailRestClient(apiKey);

var loginInfo = await cakeMail.Users.LoginAsync(userName, password);
var userKey = loginInfo.UserKey;

Quick note regarding the user key: this value is valid for several days (I don't know exactly how long though) and therefore can be cached for a reasonable period of time. There is no need to repeatedly invoke the 'Login' method to get this value.

Campaigns

A campaign is simply a way to logically group mailings toghether. You can think of campaigns as 'folders'. In fact, the CakeMail UI has a "Manage folders" button under the "Campaigns" tab where you will see all the campaigns. A word of caution: the word 'Campaign' is used in the CakeMail UI to refer to mailings which is really confusing!

var campaigns = await cakeMail.Campaigns.GetCampaignsAsync(userKey, status: MailingStatus.Ongoing, sortBy: MailingSortBy.Name, sortDirection: SortDirection.Ascending, limit: 50, offset: 0);
var campaignsCount = await cakeMail.Campaigns.GetCountAsync(userKey, MailingStatus.Ongoing);

var campaignId = await cakeMail.Campaigns.CreateAsync(userKey, "2015 User Conference");
var campaign = await cakeMail.Campaigns.GetAsync(userKey, campaignId);
var deleted = await cakeMail.Campaigns.DeleteAsync(userKey, campaignId);

Lists

A List is a collection of subscribers (or List Members, or Records). Each subscriber or List Member is uniquely identified by their email address, and may include an limited amount of Fields containing demographic information associated to each email address.

var lists = await cakeMail.Lists.GetListsAsync(userKey, sortBy: ListSortBy.Name, sortDirection: SortDirection.Descending, limit: 50, offset: 0);
var listsCount = await cakeMail.Lists.GetCountAsync(userKey);

var listId = await cakeMail.Lists.CreateAsync(userKey, "Customers and Prospects", "The XYZ Marketing Group", "marketing@yourcompany.com", true);
await cakeMail.Lists.AddFieldAsync(userKey, listId, "first_name", "text");
await cakeMail.Lists.AddFieldAsync(userKey, listId, "last_name", "text");
await cakeMail.Lists.AddFieldAsync(userKey, listId, "customer_since", "datetime");

You can add members to your list like so:

await cakeMail.Lists.SubscribeAsync(userKey, listId, "bob_the_customer@hotmail.com", true, true, new[]
{
    new KeyValuePair<string, object>("first_name", "Bob"), 
    new KeyValuePair<string, object>("last_name", "Smith"), 
    new KeyValuePair<string, object>("customer_since", DateTime.UtcNow) 
});
await cakeMail.Lists.SubscribeAsync(userKey, listId, "jane_the_prospect@hotmail.com", true, true, new[]
{
    new KeyValuePair<string, object>("first_name", "Jane"), 
    new KeyValuePair<string, object>("last_name", "Doe")
});

or you can import a group of members:

var member1 = new ListMember()
{
    Email = "bob_the_customer@hotmail.com",
    CustomFields = new Dictionary<string, object>()
    {
        { "first_name", "Bob" },
        { "last_name", "Smith" },
        { "customer_since", DateTime.UtcNow }
    }
};

var member2 = new ListMember()
{
    Email = "jane_the_prospect@hotmail.com",
    CustomFields = new Dictionary<string, object>()
    {
        { "first_name", "Jane" },
        { "last_name", "Doe" }
    }
};

var importResult = await cakeMail.Lists.ImportAsync(userKey, listId, new[] { member1, member2 });

Mailings

A mailing is an email campaign. It can be used to send standard email campaigns, A/B split campaigns or recurring campaigns.

var invitationMailingId = await cakeMail.Mailings.CreateAsync(userKey, "2015 User Conference invitation", campaignId);
await cakeMail.Mailings.UpdateAsync(userKey, invitationMailingId, listId: listId, htmlContent: "<html><body>You are invited to attend our annual user conference</body></html>", textContent: "You are invited to attend our annual user conference", subject: "Invitation to our 2015 user conference");
await cakeMail.Mailings.SheduleAsync(userKey, invitationMailingId);

var reminderMailingId = await cakeMail.Mailings.CreateAsync(userKey, "2015 User Conference reminder", campaignId);
await cakeMail.Mailings.UpdateAsync(userKey, reminderMailingId, listId: listId, htmlContent: "<html><body>Don't forget our upcoming annual user conference</body></html>", textContent: "Don't forget our upcoming annual user conference", subject: "Reminder about our 2015 user conference");
await cakeMail.Mailings.SheduleAsync(userKey, reminderMailingId, DateTime.UtcNow.AddDays(2));

License

FOSSA Status