This is a reference Ruby client to interact with the GovDelivery TMS REST API.
gem 'govdelivery-tms'
$ gem install govdelivery-tms
Loading an instance of GovDelivery::TMS::Client
will automatically connect to the API to query the available resources for your account.
# default api root endpoint is https://tms.govdelivery.com
client = GovDelivery::TMS::Client.new('auth_token', :api_root => 'https://stage-tms.govdelivery.com')
Sms and Email messages can be retrieved with the get
collection method. Messages are paged in groups of 50. To retrieve another page, used the next
method. This method will not be defined if another page is not available.
client.sms_messages.get # get the first page of sms messages
client.sms_messages.next.get # get the next page of sms messages
When loading messages, the following parameters can be passed with requests to change the sort order and number of results returned:
page_size: Must be an integer between 1 and 100
client.sms_messages.get({page_size: 2}) # get the first two sms messages
sort_by: Field by which to sort results. Default: created_at.
client.sms_messages.get({sort_by: 'created_at'}) # get the first page of sms messages, sorted by created_at
sort_order: Order by which to sort results. Must be ASC or DESC. Default: DESC.
client.sms_messages.get({sort_order: 'ASC'}) # get the first page of sms messages, sorted by created_at DESC
client.sms_messages.get({sort_by: 'body', sort_order: 'ASC'}) # get the first page of sms messages, sorted by body ASC
message = client.sms_messages.build(:body=>'Test Message!')
message.recipients.build(:phone=>'5551112222')
message.recipients.build(:phone=>'5551112223')
message.recipients.build # invalid - no phone
message.post # true
message.recipients.collection.detect{|r| r.errors } # {"phone"=>["is not a number"]}
# save succeeded, but we have one bad recipient
message.href # "/messages/sms/87"
message.get # <GovDelivery::TMS::SmsMessage href=/messages/sms/87 attributes={...}>
client.inbound_sms_messages.get # <GovDelivery::TMS::InboundSmsMessages href=/inbound/sms attributes={...}>
inbound_sms = client.inbound_sms_messages.collection.first # <GovDelivery::TMS::InboundSmsMessage href=/inbound/sms/10041 attributes={...}>
inbound_sms.to # "+15559999999"
inbound_sms.from # "+15005550006"
inbound_sms.attributes # {:from=>"+15005550006", :to=>"+15559999999", :body=>"test", :command_status=>"success", :keyword_response=>"kwidjebo", :created_at=>"2014-11-05T17:15:01Z"}
message = client.email_messages.build(:body=>'<p><a href="http://example.com">Visit here</a></p>',
:subject => 'Hey')
message.recipients.build(:email=>'[email protected]')
message.recipients.build(:email=>'')
message.post # true
message.recipients.collection.detect{|r| r.errors } # {"email"=>["can't be blank"]}
# save succeeded, but we have one bad recipient
message.href # "/messages/email/87"
message.get # <GovDelivery::TMS::EmailMessage href=/messages/email/88 attributes={...}>
message = client.email_messages.build(:subject=>'Hello!',
:body=>'<p>Hi <span style="color:red;">[[name]]</span>!</p>',
:macros=>{"name"=>"there"})
message.recipients.build(:email=>'[email protected]', :macros=>{"name"=>"Jim"})
message.recipients.build(:email=>'[email protected]', :macros=>{"name"=>"Amy"})
message.recipients.build(:email=>'[email protected]')
message.post
From Addresses are read only resources that define which email addresses you can send an email from and have replies and bounces sent to. From Addresses also have an associated default display name. If you wish to send a message from an address that is not your account's default, you will need to specify a From Address on your Message.
To add or edit From Addresses, you will need to contact your CSC.
# Fetch the from_addresses on your account
client.from_addresses.get
# Get the first from address on your account
from_address = client.from_addresses.collection.first
# Lets see what the emails and display name are
puts from_address.from_email
puts from_address.reply_to_email
puts from_address.bound_email
puts from_address.from_name
# Is this from address the account's default?
puts from_address.is_default
# New messages default to using the default from_address of your account
message = client.email_messages.build(:body=>'<p><a href="http://example.com">Visit here</a></p>',
:subject => 'Hey')
# Specifiy a different from_address using the links hash
message.links[:from_address] = from_address.id
# If you want, you can override the form_name on a message
message.from_name = 'Better Name'
message.post
template = client.email_templates.build(uuid: 'a-new-template',
subject: 'A templated subject',
body: 'Hi [[name]], this body is from a template.',
macros: {"name"=>"person"})
template.post
Note: uuid
cannot be updated.
template = client.email_templates.build(:href => 'template/email/a-new-template')
template.get
template.body = 'Hi [[name]], this body is from a new template.'
template.put
Assuming you created template
above:
message = client.email_messages.build
message.links[:email_template] = template.uuid
message.recipients.build(:email=>'[email protected]', :macros=>{"name"=>"Jim"})
message.recipients.build(:email=>'[email protected]', :macros=>{"name"=>"Amy"})
message.recipients.build(:email=>'[email protected]')
message.post
template = client.sms_templates.build(uuid: 'a_new-template',
body: 'Hi, [[name]] this is a tempalte.')
template.post
Note: uuid
cannot be updated.
template = client.sms_templates.build(href: 'template/sms/a_new-template')
template.get
template.body = 'Hi, [[name]] this is a new tempalte.'
template.put
Assuming you've created template
above:
message = client.email_messages.build
message.links[:sms_template] = template.uuid
message.recipients.build(:phone=>'5551112222')
message.recipients.build(:phone=>'5551112223')
message.post
webhook = client.webhooks.build(:url=>'http://your.url', :event_type=>'blacklisted')
webhook.post # true
POSTs will include in the body the following attributes:
attribute | description |
---|---|
message_type | 'sms' or 'email' |
status: | message state |
recipient_url | recipient URL |
messsage_url | message URL |
error_message | (failures only) |
completed_at | (sent or failed recipients only) |
email_message.get
email_message.clicked.get
email_message.clicked.collection # => [<#EmailRecipient>,...]
email_message.get
email_message.opened.get
email_message.opened.collection # => [<#EmailRecipient>,...]
email_recipient.clicks.get.collection #=> [<#EmailRecipientClick>,...]
email_recipient.opens.get.collection #=> [<#EmailRecipientOpen>,...]
Recipient counts are aggregated across all messages and grouped by message status.
start
and end
are required datetime parameters. They must be truncated to the hour and be in ISO 8601 format (YYYY-MM-DDTHH:MM:SSZ).
End dates are exclusive and all results are based on utc time.
stats = client.reports_messages_email_statistics.get({start: '2017-06-01T10:00:00Z', end: '2017:06:30T18:00:00Z'}) # get email recipient counts for messages sent between 6/1/17 and 6/30/17
stats.recipients
stats = client.reports_messages_sms_statistics.get({start: '2017-06-01T10:00:00Z', end: '2017:06:30T18:00:00Z'}) # get sms recipient counts for messages sent between 6/1/17 and 6/30/17
stats.recipients
Command Types are the available commands that can be used to respond to an incoming SMS message.
command_types = client.command_types.get
command_types.collection.each do |at|
puts at.name # "forward"
puts at.string_fields # ["url", ...]
puts at.array_fields # ["foo", ...]
end
Keywords are chunks of text that are used to match an incoming SMS message.
# CRUD
keyword = client.keywords.build(:name => "BUSRIDE", :response_text => "Visit example.com/rides for more info")
keyword.post # true
keyword.name # 'busride'
keyword.name = "TRAINRIDE"
keyword.put # true
keyword.name # 'trainride'
keyword.delete # true
# list
keywords = client.keywords.get
keywords.collection.each do |k|
puts k.name, k.response_text
end
Commands have a command type and one or more keywords. The example below configures the system to respond to an incoming SMS message containing the string "RIDE" (or "ride") by forwarding an http POST to http://example.com/new_url
. The POST body variables are documented in GovDelivery's TMS REST API documentation.
# CRUD
keyword = client.keywords.build(:name => "RIDE")
keyword.post
command = keyword.commands.build(
:name => "Forward to somewhere else",
:params => {:url => "http://example.com", :http_method => "get"},
:command_type => :forward)
command.post
command.params = {:url => "http://example.com/new_url", :http_method => "post"}
command.put
command.delete
# list
commands = keyword.commands.get
commands.collection.each do |c|
puts c.inspect
end
Each time a given command is executed, a command action is created.
Note The actions relationship does not exist on commands that have 0 command actions. Because of this, an attempt to access the command_actions attribute of a command that has 0 command actions will result in a NoMethodError.
# Using the command from above
begin
command.get
command_actions = command.command_actions
command_actions.get
command_action = command_actions.collection.first
command_action.inbound_sms_message # InboundSmsMessage object that initiated this command execution
command_action.response_body # String returned by the forwarded to URL
command_action.status # HTTP Status returned by the forwarded to URL
command_action.content_type # Content-Type header returned by the forwarded to URL
rescue NoMethodError => e
# No command actions to view
end
Any instance of a Logger-like class can be passed in to the client; incoming and outgoing request information will then be logged to that instance.
The example below configures GovDelivery::TMS::Client
to log to STDOUT
:
logger = Logger.new(STDOUT)
client = GovDelivery::TMS::Client.new('auth_token', :logger => logger)
You can use TMS from the mail gem or ActionMailer as a delivery method.
Gemfile
gem 'govdelivery-tms', :require=>'govdelivery/tms/mail/delivery_method'
config/environment.rb
config.action_mailer.delivery_method = :govdelivery_tms
config.action_mailer.govdelivery_tms_settings = {
:auth_token=>'auth_token',
:api_root=>'https://tms.govdelivery.com'
}
This project uses yard to generate documentation. To generate API documentation yourself, use the following series of commands from the project root:
# install development gems
bundle install
# generate documentation
bundle exec rake yard
The generated documentation will be placed in the doc
folder.
bundle install
bundle exec rake
This project is tested and compatible with Ruby 3.2.2.