Haskell Client for the Mandrill JSON API
This module implement a low-level, 1:1 mapping API to the Mandrill transactional email service.
Changelog
Version 0.5.2.1
- Added
Functor,FoldableandTraversableinstances toMandrillResponse(Courtesy of @dredozubov)
Version 0.5.2.0
- Added inbound calls (Courtesy of @mwotton)
Version 0.5.1.0
- Relaxed the constraint on
aesonto allow0.11.0.0.
Version 0.5.0.0
-
Changed the
MandrillHeaderstype synonym fromValuetoObject. -
Changed the
mmsg_metadataandmmdt_valuesfields fromMandrillVarstoObject. -
Changed the
mmsg_global_merge_varsandmmvr_varsfields from[MandrillVars]to[MergeVar] -
Added the
MergeVardata type:
data MergeVar = MergeVar {
_mv_name :: !Text
, _mv_content :: Value
}
- Removed the
MandrillVarstype synonym.
Version 0.4.0.0
- Modified the
Base64ByteStringtype to accept another constructor. This allows the user to pass already-encoded Base64 strings which might be coming upstream.
Example
This package was built with pragmatism and reuse in mind. This means this API comes in two flavours: an IO-based and an handy monad transformer which can be plugged in your stack of choice. Example:
{-# LANGUAGE OverloadedStrings #-}
import Text.Email.Validate
import Network.API.Mandrill
main :: IO ()
main = do
case validate "foo@example.com" of
Left err -> print $ "Invalid email!" ++ show err
Right addr -> runMandrill "MYTOKENHERE" $ do
let msg = "<p>My Html</p>"
res <- sendEmail (newTextMessage addr [addr] "Hello" msg)
case res of
MandrillSuccess k -> liftIO (print k)
MandrillFailure f -> liftIO (print f)
Supported API versions
- 1.0 (partially)
- Users call - 100%
- info.json
ping.json(as doesn't return valid json!)- ping2.json
- senders.json
- Messages call
- send.json
- Users call - 100%
Testing online API
To test the online API, first build the package with tests enabled:
cabal install --enable-tests
Then export an environment variable with your Mandrill Test token:
export MANDRILL_API_KEY="YOURKEYGOESHERE"
And finally execute the testsuite:
cabal test
Contributions
This library scratches my own itches, but please fork away! Pull requests are encouraged to implement the part of the API you need.