This package wraps the Campaign Monitor API so that .NET applications may interface with it, implementing the full functionality of the API. Maintained by Campaign Monitor, the library is actively supported and well-documented with code examples and implementation walkthroughs. The Campaign Monitor API allows users to interact and "sync" with their Campaign Monitor account via simple web-based methods. Common uses of the API include: *Automatically sync subscribers between Campaign Monitor and a third party tool. *Create and send custom email campaigns to segments of subscribers built on the fly. *Develop useful plugins and integrations like these guys for other popular apps *Automatically create a client account, set billing and load it with ready-to-send templates.
Email doesn't need postage, right? Is that old hoax about the postal service charging per message finally coming true? Not really. But PostageApp may be a service worth paying for if you want to send email from your application.
As the number of APIs grows, more people are becoming familiar with the term. I had a taxi driver who knew about APIs, although that was in tech-heavy San Francisco. Despite becoming more known, "API" is not a term most mainstream users will use. Yet many of these same people are already asking for APIs—they’re just not using the term. Here are three ways mainstream users are asking for APIs.