The Flowroute Ruby Library v3 provides methods for interacting with Numbers v2 – which includes inbound voice routes, E911 addresses, and CNAM storage – and Messages v2.1 of the Flowroute API.
TopicsRequirements
- Flowroute API credentials
- Ruby 2.0.0 or higher
Installation
First, start a shell session and clone the SDK:
via HTTPS:
git clone https://github.com/flowroute/flowroute-sdk-v3-ruby.gitvia SSH:
git@github.com:flowroute/flowroute-sdk-v3-ruby.gitSwitch to the newly-created flowroute-sdk-v3-ruby directory and run the following to build the Flowroute gem:
gem build flowroute_numbers_and_messaging.gemspecThis version of the library has been tested with Ruby 2.5.0 for Mac OS X. To see which version of ruby is installed on your machine, run the following:
ruby --versionOnce built, run the following to install the gem in the current directory:
gem install flowroute_numbers_and_messaging-3.0.0.gem
Usage
In Flowroute's approach to building the Ruby library v3, HTTP requests are handled by controllers named after the API resources they represent: Numbers, Routes, Messages, E911s, and CNAMs. These controllers contain the methods used to perform messaging and number management which includes programmatic configuration of inbound voice routes, E911 addresses, and CNAM storage within the Ruby library.
Controllers
NumbersController
Contains all of the methods necessary to search through Flowroute's phone number inventory, purchase a phone number, and review details of your account phone numbers.
- list_available_area_codes() - Returns a list of all Numbering Plan Area (NPA) codes containing purchasable phone numbers. All request parameters are optional. If you don't specify a limit, results are limited to the first 10 items.
- list_available_exchange_codes() - Returns a list of all Central Office (exchange) codes containing purchasable phone numbers. All request parameters are optional.
- search_for_purchasable_phone_numbers() - Searches for purchasable phone numbers by state or rate center, or by your specified search value.
- purchase_a_phone_number(purchasable_number) - Lets you purchase a phone number from available Flowroute inventory.
- list_account_phone_numbers() - Returns a list of all phone numbers currently on your Flowroute account.
- list_phone_number_details(number_id) - Returns details on a specific phone number associated with your account, including primary voice route, and failover voice route if previously configured.
RoutesController
Contains the methods required to create new inbound routes, view all of your account routes, and update primary and failover voice routes for your phone numbers.
- create_an_inbound_route(route_body) - Creates a new inbound route which can then be assigned as either a primary or a failover voice route for a phone number on your account.
- list_inbound_routes() - Returns a list of your inbound routes. From the list, you can then select routes to use as the primary and failover voice routes for phone numbers on your account.
- update_primary_voice_route(number_id, route_body) - Updates the primary voice route for a phone number. You must create the route first via the create_an_inbound_route(routebody) method.
- update_failover_voice_route(number_id, route_body) - Updates the failover voice route for a phone number. You must create the route first via the create_an_inbound_route(routebody) method.
MessagesController
Contains the methods required to send an MMS or SMS, and review a specific Message Detail Record (MDR) or a set of messages.
- send_a_message(message_body) - Sends an SMS or MMS from a Flowroute long code or toll-free phone number to another valid phone number.
- look_up_a_message_detail_record() - Searches for a specific message record ID and returns a Message Detail Record (in MDR2 format).
- look_up_a_set_of_messages() - Retrieves a list of Message Detail Records (MDRs) within a specified date range. Date and time is based on Coordinated Universal Time (UTC).
E911sController
Contains all of the methods necessary to create, validate, update, and delete an E911 address on your account as well as assigning an E911 record to a phone number and if necessary, deactivating the E911 service for said phone number.
- create(e911_address_to_json()) - Lets you create and validate an E911 address within the US and Canada which can then be assigned to any of the long code or toll-free numbers on your account. To assign an E911 address to your number, see Assign a Valid E911 Address to Your Phone Number.
- list_e911s(options) - Returns a list of all E911 records on your account by default. You can apply search filters using any of the optional query parameters.
- e911_details(e911_id) - Returns details on a specified E911 record ID.
- validate(e911_address_to_json()) - Lets you validate an E911 address whether it is a new or an existing address on your account.
- update(e911_id, e911_address_to_json()) - Lets you update and validate an existing E911 address on your account. You must create the E911 address first by following Create and Validate a New E911 Address.
- associate(number_id, e911_id) - Lets you assign a valid E911 address to a specific long code or toll-free phone number in your account. This endpoint does not return an error for subsequent attempts at associating a phone number with the same E911 record. The E911 record assignment charge only occurs on the first successful attempt. Note that you can later assign a different e911_id to the same phone number and will be charged accordingly.
- unassociate(number_id) - Lets you deactivate the current E911 service for your phone number.
- list_associations(e911_id) - Returns a list of your Flowroute long code or toll-free phone numbers associated with a specified E911 record.
- delete_record(e911_id) - Lets you delete an E911 address associated with your account. You must remove all phone number associations first before you can successfully delete the specified E911 record.
CNAMsController
Contains all of the methods necessary to create, delete, assign and unassign CNAM records, as well as view and filter for specific CNAM records on your Flowroute account.
- create(cnam_value) - Lets you create a Caller ID record for your account which can then be assigned to any of your long code numbers. To assign a CNAM record to your number, see "Assign a CNAM Record to a Phone Number".
- list_cnams(options) - Returns a list of all CNAM records on your account by default. You can apply search filters using any of the optional query parameters.
- cnam_details(cnam_id) - Returns details pertaining to a specific CNAM record on your account, including long code numbers that are associated with the record.
- associate(number_id, cnam_id) - Lets you associate a CNAM record with a specified long code number on your account. The CNAM value will be the Caller ID name displayed when making outbound calls on the specified long code number. Your CNAM must be approved before you can associate it with a number. Note that CNAM association with a phone number takes 5-7 business days.
- unassociate(number_id) - Lets you unassign a CNAM record associated with a specified long code number on your account without deleting the CNAM record itself.
- delete_record(cnam_id) - Lets you delete a CNAM record from your account. This will automatically disassociate all numbers associated with this CNAM record.
The following shows an example of a single Ruby file that imports the Flowroute API client and all the required modules. The Ruby Library comes with a demo.rb file that you can edit and run as an example.
require 'flowroute_numbers_and_messaging'
require 'pp'
Configuration
Credentials
In demo.rb, replace basic_auth_user_name with your API Access Key and basic_auth_password with your API Secret Key from the Flowroute Manager. Note that in our example, we are accessing your Flowroute credentials as environment variables. To learn more about setting environment variables, see How To Read and Set Environmental and Shell Variables. Alternatively, you can edit the configuration file, lib/flowroute_numbers_and_messaging/configuration.rb, and replace basic_auth_user_name with your Flowroute access key and basic_auth_password with your Flowroute secret key.
# Set up your api credentials and test mobile number for outbound SMS or MMS
basic_auth_user_name = ENV['FR_ACCESS_KEY'] # Your Flowroute Access Key
basic_auth_password = ENV['FR_SECRET_KEY'] # Your Flowroute Secret Key
mobile_number = "YOUR_MOBILE_NUMBER"
Instantiate API Client and Controllers
Next, instantiate the API Client and its controllers.
# Instantiate API client and create controllers for Numbers, Messages, and Routes
client = FlowrouteNumbersAndMessaging::FlowrouteNumbersAndMessagingClient.new(
basic_auth_user_name: basic_auth_user_name,
basic_auth_password: basic_auth_password
)
numbers_controller = client.numbers
routes_controller = client.routes
messages_controller = client.messages
e911_controller = client.e911
cnam_controller = client.cnam
Methods
The following section will demonstrate the capabilities of Numbers v2, Routes v2, E911s v2, CNAMs v2, and Messages v2.1 that are wrapped in our Ruby library. Note that the example responses have been formatted using Mac's pbpaste and jq. To learn more, see Quickly Tidy Up JSON from the Command Line.
Number Management
Flowroute Ruby Library v3 allows you to make HTTP requests to the numbers resource of Flowroute API v2: https://api.flowroute.com/v2/numbers
list_available_area_codes()
The method accepts limit, offset, and max_setup_cost as parameters which you can learn more about in the API reference.
Example Request
puts("--List Available Area Codes")
max_setup_cost = 3.25
limit = 3
offset = nil
result = numbers_controller.list_available_area_codes(limit, offset, max_setup_cost)
pp(result)
Example Response
On success, the HTTP status code in the response header is 200 OK and the response body contains an array of area code objects in JSON format.
{
"data": [
{
"type": "areacode",
"id": "201",
"links": {
"related": "https://api.flowroute.com/v2/numbers/available/exchanges?areacode=201"
}
},
{
"type": "areacode",
"id": "202",
"links": {
"related": "https://api.flowroute.com/v2/numbers/available/exchanges?areacode=202"
}
},
{
"type": "areacode",
"id": "203",
"links": {
"related": "https://api.flowroute.com/v2/numbers/available/exchanges?areacode=203"
}
}
],
"links": {
"self": "https://api.flowroute.com/v2/numbers/available/areacodes?max_setup_cost=3&limit=3&offset=0",
"next": "https://api.flowroute.com/v2/numbers/available/areacodes?max_setup_cost=3&limit=3&offset=3"
}
}
list_available_exchange_codes()
The method accepts limit, offset, max_setup_cost, and areacode as parameters which you can learn more about in the API reference.
Example Request
puts("--List Available Exchange Codes")
limit = 3
offset = nil
max_setup_cost = nil
areacode = 347
result = numbers_controller.list_available_exchange_codes(limit, offset, max_setup_cost, areacode)
pp(result)
Example Response
On success, the HTTP status code in the response header is 200 OK and the response body contains an array of exchange objects in JSON format.
{
"data": [
{
"type": "exchange",
"id": "347215",
"links": {
"related": "https://api.flowroute.com/v2/numbers/available?starts_with=1347215"
}
},
{
"type": "exchange",
"id": "347325",
"links": {
"related": "https://api.flowroute.com/v2/numbers/available?starts_with=1347325"
}
},
{
"type": "exchange",
"id": "347331",
"links": {
"related": "https://api.flowroute.com/v2/numbers/available?starts_with=1347331"
}
}
],
"links": {
"self": "https://api.flowroute.com/v2/numbers/available/exchanges?areacode=347&limit=3&offset=0",
"next": "https://api.flowroute.com/v2/numbers/available/exchanges?areacode=347&limit=3&offset=3"
}
}
search_for_purchasable_phone_numbers()
The method accepts starts_with, contains, ends_with, limit, offset, rate_center, and state as parameters which you can learn more about in the API reference.
Example Request
puts("--Search for Purchasable Phone Numbers")
starts_with = 646
contains = 3
ends_with = 7
limit = 3
offset = nil
rate_center = nil
state = nil
result = numbers_controller.search_for_purchasable_phone_numbers(starts_with, contains, ends_with, limit, offset, rate_center, state)
pp(result)
Example Response
On success, the HTTP status code in the response header is 200 OK and the response body contains an array of phone number objects in JSON format.
{
"data": [
{
"attributes": {
"rate_center": "nwyrcyzn01",
"value": "16463439507",
"monthly_cost": 1.25,
"state": "ny",
"number_type": "standard",
"setup_cost": 1
},
"type": "number",
"id": "16463439507",
"links": {
"related": "https://api.flowroute.com/v2/numbers/16463439507"
}
},
{
"attributes": {
"rate_center": "nwyrcyzn01",
"value": "16463439617",
"monthly_cost": 1.25,
"state": "ny",
"number_type": "standard",
"setup_cost": 1
},
"type": "number",
"id": "16463439617",
"links": {
"related": "https://api.flowroute.com/v2/numbers/16463439617"
}
},
{
"attributes": {
"rate_center": "nwyrcyzn01",
"value": "16463439667",
"monthly_cost": 1.25,
"state": "ny",
"number_type": "standard",
"setup_cost": 3.99
},
"type": "number",
"id": "16463439667",
"links": {
"related": "https://api.flowroute.com/v2/numbers/16463439667"
}
}
],
"links": {
"self": "https://api.flowroute.com/v2/numbers/available?contains=3&ends_with=7&starts_with=1646&limit=3&offset=0",
"next": "https://api.flowroute.com/v2/numbers/available?contains=3&ends_with=7&starts_with=1646&limit=3&offset=3"
}
}
purchase_a_phone_number(purchasable_number)
The method is used to purchase a telephone number from Flowroute's inventory and accepts the phone number id as a parameter which you can learn more about in the API reference. In the following example, we assign the id of the first phone number in the resulting JSON array as the phone number to be purchased. Note that this function call is currently commented out. Uncomment to test the purchase_a_phone_number method.
Example Request
puts("--Purchase a Phone Number")
purchasable_number = result['data'][0]['id']
result = numbers_controller.purchase_a_phone_number(purchasable_number)
Example Response
On success, the HTTP status code in the response header is 200 OK and the response body contains a phone number object in JSON format.
{
"data": {
"attributes": {
"alias": null,
"cnam_lookups_enabled": true,
"number_type": "standard",
"rate_center": "millbrae",
"state": "ca",
"value": "16502390214"
},
"id": "16502390214",
"links": {
"self": "https://api.flowroute.com/v2/numbers/16502390214"
},
"relationships": {
"cnam_preset": {
"data": null
},
"e911_address": {
"data": null
},
"failover_route": {
"data": null
},
"primary_route": {
"data": {
"id": "0",
"type": "route"
}
}
},
"type": "number"
},
"included": [
{
"attributes": {
"alias": "sip-reg",
"route_type": "sip-reg",
"value": null
},
"id": "0",
"links": {
"self": "https://api.flowroute.com/v2/routes/0"
},
"type": "route"
}
],
"links": {
"self": "https://api.flowroute.com/v2/numbers/16502390214"
}
}
list_account_phone_numbers()
The method accepts starts_with, ends_with, contains, limit, and offset as parameters which you can learn more about in the API reference.
Example Request
puts("--List Account Phone Numbers")
starts_with = 201
ends_with = nil
contains = nil
limit = 3
offset = nil
result = numbers_controller.list_account_phone_numbers(starts_with, ends_with, contains, limit, offset)
pp(result)
Example Response
On success, the HTTP status code in the response header is 200 OK and the response body contains an array of phone number objects in JSON format.
{
"data": [
{
"attributes": {
"rate_center": "oradell",
"value": "12012673227",
"alias": null,
"state": "nj",
"number_type": "standard",
"cnam_lookups_enabled": true
},
"type": "number",
"id": "12012673227",
"links": {
"self": "https://api.flowroute.com/v2/numbers/12012673227"
}
},
{
"attributes": {
"rate_center": "jerseycity",
"value": "12014845220",
"alias": null,
"state": "nj",
"number_type": "standard",
"cnam_lookups_enabled": true
},
"type": "number",
"id": "12014845220",
"links": {
"self": "https://api.flowroute.com/v2/numbers/12014845220"
}
}
],
"links": {
"self": "https://api.flowroute.com/v2/numbers?starts_with=1201&limit=3&offset=0"
}
}
list_phone_number_details(number_id)
The method accepts the number_id as a parameter which you can learn more about in the API reference. In the following example, we request the details of the first phone number returned after calling the list_account_phone_numbers method.
Example Request
puts("--List Phone Number Details")
number_id = result['data'][0]['id']
result = numbers_controller.list_phone_number_details(number_id)
pp(result)
Example Response
On success, the HTTP status code in the response header is 200 OK and the response body contains a phone number object in JSON format.
{
"included": [
{
"attributes": {
"route_type": "sip-reg",
"alias": "sip-reg",
"value": null
},
"type": "route",
"id": "0",
"links": {
"self": "https://api.flowroute.com/v2/routes/0"
}
}
],
"data": {
"relationships": {
"cnam_preset": {
"data": null
},
"e911_address": {
"data": null
},
"failover_route": {
"data": null
},
"primary_route": {
"data": {
"type": "route",
"id": "0"
}
}
},
"attributes": {
"rate_center": "millbrae",
"value": "16502390214",
"alias": null,
"state": "ca",
"number_type": "standard",
"cnam_lookups_enabled": true
},
"type": "number",
"id": "16502390214",
"links": {
"self": "https://api.flowroute.com/v2/numbers/16502390214"
}
},
"links": {
"self": "https://api.flowroute.com/v2/numbers/16502390214"
}
}
Route Management
The Flowroute Ruby Library v3 allows you to make HTTP requests to the routes resource of Flowroute API v2: https://api.flowroute.com/v2/routes
create_an_inbound_route(route_body)
The method accepts the route object in JSON format as a parameter which you can learn more about in the API reference. In the following example, we define a function to generate a six-character random string for our subdomain which we later concatenate with our example domain and assign as our host value. We also generate a unique route_alias.
Example Request
puts ("---Create an Inbound Route")
# Function to generate six-charac random string
genstring = [('a'..'z'), ('A'..'Z')].map(&to_a).flatten
new_route = (0...6).map { genstring[rand(genstring.length)] }.join + '.sonsofodin.com'
range = ((48..57).to_a+(65..90).to_a).map{ |i| i.chr }
route_alias = Array.new(6){ range.sample }.join
request_body = '{
"data": {
"type": "route",
"attributes": {
"route_type": "host",
"value": "' + new_route.to_s + '",
"alias": "' + route_alias.to_s + '"
}
}
}'
result = routes_controller.create_an_inbound_route(request_body)
pp(result)
Example Response
On success, the HTTP status code in the response header is 201 Created and the response body contains a route object in JSON format.
{
"data": {
"attributes": {
"alias": "new route",
"route_type": "host",
"value": "il775u.sonsofodin.com"
},
"id": "98396",
"links": {
"self": "https://api.flowroute.com/routes/98396"
},
"type": "route"
},
"links": {
"self": "https://api.flowroute.com/routes/98396"
}
}
list_inbound_routes()
The method accepts limit and offset as parameters which you can learn more about in the API reference.
Example Request
puts ("---List Inbound Routes")
limit = 3
result = routes_controller.list_inbound_routes(limit)
pp(result)
Example Response
On success, the HTTP status code in the response header is 200 OK and the response body contains an array of route objects in JSON format.
{
"data": [
{
"attributes": {
"route_type": "sip-reg",
"alias": "sip-reg",
"value": null
},
"type": "route",
"id": "0",
"links": {
"self": "https://api.flowroute.com/v2/routes/0"
}
},
{
"attributes": {
"route_type": "number",
"alias": "PSTNroute1",
"value": "12065551212"
},
"type": "route",
"id": "83834",
"links": {
"self": "https://api.flowroute.com/v2/routes/83834"
}
}
],
"links": {
"self": "https://api.flowroute.com/v2/routes?limit=2&offset=0",
"next": "https://api.flowroute.com/v2/routes?limit=2&offset=2"
}
}
update_primary_voice_route(number_id, route_body)
The method accepts a phone number id and a route record object in JSON format as parameters which you can learn more about in the API reference. In the following example, we extract the second route in our list_inbound_routes search result and assign it as the primary voice route for our previously declared number_id.
Example Request
prirouteid = result['data'][1]['id']
request_body = '{
"data": {
"type": "route",
"id": "' + prirouteid +'"
}
}'
puts("---Update Primary Voice Route")
priroute_result = routes_controller.update_primary_voice_route(number_id, request_body)
puts priroute_result
if priroute_result.nil?
puts "204: No Content"
else
puts priroute_result
end
Example Response
On success, the HTTP status code in the response header is 204 No Content which means that the server successfully processed the request and is not returning any content.
204: No Contentupdate_failover_voice_route(number_id, route_body)
The method accepts a phone number id and a route record object in JSON format as parameters which you can learn more about in the API reference. In the following example, we extract the third and last route in our list_inbound_routes search result and assign it as the failover voice route for our previously declared number_id.
Example Request
secrouteid = result['data'][2]['id']
request_body = '{
"data": {
"type": "route",
"id": "' + secrouteid +'"
}
}'
puts ("---Update Failover Voice Route")
secroute_result = routes_controller.update_failover_voice_route(number_id, request_body)
if secroute_result.nil?
puts "204: No Content"
else
puts secroute_result
end
Example Response
On success, the HTTP status code in the response header is 204 No Content which means that the server successfully processed the request and is not returning any content.
204: No ContentMessaging
The Flowroute Ruby Library v3 allows you to make HTTP requests to the messages resource of Flowroute API v2.1: https://api.flowroute.com/v2.1/messages
send_a_message(message_body)
The method accepts a message object in JSON format as a parameter which you can learn more about in the API References for MMS and SMS. In the following example, we are sending an MMS in compact JSON format with a png attachment from the previously declared number_id to your mobile number.
Example Request
#Compact JSON format for outbound MMS
request_body = '{
"to": "' + mobile_number.to_s + '",
"from": "' + number_id.to_s + '",
"body": "hello there",
"is_mms": "true",
"media_urls": ["https://s3-us-west-2.amazonaws.com/mms-testing/01f2c5551bc24c91b22a084081211eb0.png"]
}'
puts("---Send An MMS")
result = messages_controller.send_a_message(request_body)
pp(result)
Note that this function call is currently commented out. Uncomment to test the send_a_message method.
Example Response
On success, the HTTP status code in the response header is 202 Accepted and the response body contains the message record ID with mdr2 prefix.
{
"data": {
"links": {
"self": "https://api.flowroute.com/v2.1/messages/mdr2-39cadeace66e11e7aff806cd7f24ba2d"
},
"type": "message",
"id": "mdr2-39cadeace66e11e7aff806cd7f24ba2d"
}
}
look_up_a_set_of_messages(start_date)
The method accepts start_date, end_date, limit, and offset as parameters which you can learn more about in the API Reference.
Example Request
puts ("---Look Up A Set Of Messages")
start_date = "2017-12-01"
end_date = "2018-01-08"
limit = 2
result = messages_controller.look_up_a_set_of_messages(start_date, end_date, limit)
pp(result)
Example Response
On success, the HTTP status code in the response header is 200 OK and the response body contains an array of message objects in JSON format.
{
"data": [
{
"attributes": {
"body": "Hello are you there? ",
"status": "delivered",
"direction": "inbound",
"amount_nanodollars": 4000000,
"to": "12012673227",
"message_encoding": 0,
"timestamp": "2017-12-22T01:52:39.39Z",
"delivery_receipts": [],
"amount_display": "$0.0040",
"from": "12061231234",
"is_mms": false,
"message_type": "longcode"
},
"type": "message",
"id": "mdr2-ca82be46e6ba11e79d08862d092cf73d"
},
{
"attributes": {
"body": "test sms on v2",
"status": "message buffered",
"direction": "outbound",
"amount_nanodollars": 4000000,
"to": "12061232634",
"message_encoding": 0,
"timestamp": "2017-12-21T16:44:34.93Z",
"delivery_receipts": [
{
"status": "message buffered",
"status_code": 1003,
"status_code_description": "Message accepted by Carrier",
"timestamp": "2017-12-21T16:44:35.00Z",
"level": 2
},
{
"status": "smsc submit",
"status_code": null,
"status_code_description": "Message has been sent",
"timestamp": "2017-12-21T16:44:35.00Z",
"level": 1
}
],
"amount_display": "$0.0040",
"from": "12012673227",
"is_mms": false,
"message_type": "longcode"
},
"type": "message",
"id": "mdr2-39cadeace66e11e7aff806cd7f24ba2d"
}
],
"links": {
"next": "https://api.flowroute.com/v2.1/messages?limit=2&start_date=2017-12-01T00%3A00%3A00%2B00%3A00&end_date=2018-01-08T00%3A00%3A00%2B00%3A00&offset=2"
}
}
look_up_a_message_detail_record(message_id)
The method accepts a message id in MDR2 format as a parameter which you can learn more about in the API Reference. In the following example, we retrieve the details of the first message in our look_up_a_set_of_messages search result.
Example Request
puts ("---Look Up A Message Detail Record")
message_id = result['data'][0]['id']
result = messages_controller.look_up_a_message_detail_record(message_id)
pp(result)
Example Response
On success, the HTTP status code in the response header is 200 OK and the response body contains the message object for our specified message id.
{
"data": {
"attributes": {
"body": "Hello are you there? ",
"status": "delivered",
"direction": "inbound",
"amount_nanodollars": 4000000,
"to": "12012673227",
"message_encoding": 0,
"timestamp": "2017-12-22T01:52:39.39Z",
"delivery_receipts": [],
"amount_display": "$0.0040",
"from": "12061232634",
"is_mms": false,
"message_type": "longcode"
},
"type": "message",
"id": "mdr2-ca82be46e6ba11e79d08862d092cf73d"
}
}
E911 Address Management
The Flowroute Ruby Library v3 allows you to make HTTP requests to the e911s resource of Flowroute API v2: https://api.flowroute.com/v2/e911s
list_e911s(options)
The method accepts limit, offset, and state as parameters which you can learn more about in the API reference.
Example Request
puts("---List E911 Records")
result = e911_controller.list_e911s(3, 0)
pp(result)
Example Response
On success, the HTTP status code in the response header is 200 OK and the response body contains an array of e911 objects in JSON format.
---List E911 Records
{
"data": [
{
"attributes": {
"address_type": "",
"address_type_number": "",
"city": "Seattle",
"country": "US",
"first_name": "Death",
"label": "Funeral Homes",
"last_name": "Crow",
"state": "WA",
"street_name": "Smith St",
"street_number": "123",
"zip": "98101"
},
"id": "22127",
"links": {
"self": "https://api.flowroute.com/v2/e911s/22127"
},
"type": "e911"
},
{
"attributes": {
"address_type": "",
"address_type_number": "",
"city": "Seattle",
"country": "US",
"first_name": "Jim",
"label": "Smith Tower",
"last_name": "Law",
"state": "WA",
"street_name": "Smith St",
"street_number": "123",
"zip": "98101"
},
"id": "22124",
"links": {
"self": "https://api.flowroute.com/v2/e911s/22124"
},
"self": "https://api.flowroute.com/v2/e911s/22124"
},
"type": "e911"
},
{
"attributes": {
"address_type": "",
"address_type_number": "",
"city": "Seattle",
"country": "US",
"first_name": "Bob",
"label": "First e911 record",
"last_name": "Law",
"state": "WA",
"street_name": "Smith St",
"street_number": "123",
"zip": "98101"
},
"id": "22120",
"links": {
"self": "https://api.flowroute.com/v2/e911s/22120"
},
"type": "e911"
}
],
"links": {
"next": "https://api.flowroute.com/v2/e911s?state=WA&limit=3&offset=3",
"self": "https://api.flowroute.com/v2/e911s?state=WA&limit=3&offset=0"
}
}
e911_details(e911_id)
The method accepts an e911_id as a parameter which you can learn more about in the API reference.
Example Request
puts("---Show E911 Detail")
e911_id = result['data'][0]['id']
result = e911_controller.e911_details(e911_id)
pp(result)
Example Response
On success, the HTTP status code in the response header is 200 OK and the response body contains a detailed e911 object in JSON format.
---Show E911 Detail
{
"data": {
"attributes": {
"address_type": "",
"address_type_number": "",
"city": "Seattle",
"country": "US",
"first_name": "Death",
"label": "Funeral Homes",
"last_name": "Crow",
"state": "WA",
"street_name": "Smith St",
"street_number": "123",
"zip": "98101"
},
"id": "22127",
"links": {
"self": "https://api.flowroute.com/v2/e911s/22127"
},
"type": "e911"
}
}
validate(e911_address_to_json())
In the following example request, we instantiate an E911 address variable, e911_record, directly initializing its different data attributes with example values. Learn more about the different body parameters in the API reference. We then pass e911_record as a parameter for the validate method and invoke the to_json() to convert the e911_record string into the required JSON object.
Example Request
puts("---Validate an E911 Address")
e911_record = FlowrouteNumbersAndMessaging::E911.new('N Vassault', '3910', nil, nil, 'Tacoma', 'WA', '98407', 'US', 'Janet', 'Doe', 'Home')
result = e911_controller.validate(e911_record.to_json())
pp(result)
Example Response
On success, the HTTP status code in the response header is 204 No Content which means that the server successfully processed the request and is not returning any content.
nil (204 No Content)create(e911_address_to_json())
The method accepts an E911 object with its different attributes as a parameter. Learn more about the different E911 attributes in the API reference. In the following example request, we pass our previously validated E911 string, e911_record, as a parameter for the create function and invoke the to_json() method to convert the e911_record string into the required JSON object.
Example Request
puts("---Create an E911 Address")
e911_record = FlowrouteNumbersAndMessaging::E911.new('N Vassault', '3910', 'SUITE', '200', 'Tacoma', 'WA', '98407', 'US', 'Janet', 'Doe', 'Home')
result = e911_controller.create(e911_record.to_json())
pp(result)
Example Response
On success, the HTTP status code in the response header is 201 Created and the response body contains the newly created e911 object in JSON format. On error, a printable representation of the detailed API response is displayed.
---Create an E911 Address
{
"data": {
"attributes": {
"address_type": "Suite",
"address_type_number": "200",
"city": "Tacoma",
"country": "US",
"first_name": "Janet",
"label": "Home",
"last_name": "Doe",
"state": "WA",
"street_name": "N Vassault",
"street_number": "3910",
"zip": "98407"
},
"id": "21907",
"links": {
"self": "https://api.flowroute.com/v2/e911s/21907"
},
"type": "e911"
}
}
update(e911_id, e911_address.to_json()
The method accepts an E911 address and an E911 record ID as parameters. Learn more about the different E911 attributes that you can update in the API reference. In the following example, we will retrieve the record ID of our newly added E911 address. We then update the attributes of our E911 address by invoking the from_hash method and passing the result from our previous method call, "Create An E911 Record".
Example Request
puts("---Update an E911 Record")
e911_id = result['data']['id']
e911_record = FlowrouteNumbersAndMessaging::E911.from_hash(result)
result = e911_controller.update(e911_id, e911_record.to_json())
pp(result)
Example Response
On success, the HTTP status code in the response header is 200 OK and the response body contains the newly updated e911 object in JSON format. On error, a printable representation of the detailed API response is displayed.
{
"data": {
"attributes": {
"address_type": "Apartment",
"address_type_number": "666",
"city": "Seattle",
"country": "US",
"first_name": "Jim",
"label": "Funeral Homes",
"last_name": "Law",
"state": "WA",
"street_name": "Smith St",
"street_number": "123",
"zip": "98101"
},
"id": "21907",
"links": {
"self": "https://api.flowroute.com/v2/e911s/21907"
},
"type": "e911"
}
}
associate(number_id, e911_id)
The method accepts an E911 record ID and a phone number as parameters which you can learn more about in the API reference. In the following example, we pass the previously declared variable, number_id, and our previously declared e911_id, then make the association between them.
Example Request
result = numbers_controller.list_account_phone_numbers(starts_with, ends_with, contains, limit, offset)
number_id = result['data'][0]['id']
puts("---Associate an E911 Address with a DID")
result = e911_controller.associate(number_id, e911_id)
pp(result)
Example Response
On success, the HTTP status code in the response header is 204 No Content which means that the server successfully processed the request and is not returning any content.
---Associate an E911 Address with a DID
nil (204 No Content)
list_associations(e911_id)
The method accepts an E911 record ID as a parameter which you can learn more about in the API reference. In the following example, we retrieve the list of phone numbers associated with our previously declared e911_id.
Example Request
puts("---List All DIDs Associated with an E911 Record")
result = e911_controller.list_associations(e911_id)
pp(result)
Example Response
On success, the HTTP status code in the response header is 200 OK and the response body contains an array of related number objects in JSON format.
---List All DIDs Associated with an E911 Record
{
"data": [
{
"attributes": {
"alias": null,
"value": "12062011682"
},
"id": "12062011682",
"links": {
"self": "https://api.flowroute.com/v2/numbers/12062011682"
},
"type": "number"
}
],
"links": {
"self": "https://api.flowroute.com/v2/e911s/21907/relationships/numbers?limit=10&offset=0"
}
}
unassociate(number_id)
The method accepts a phone number as a parameter which you can learn more about in the API reference. In the following example, we deactivate the E911 service for our previously assigned phone number ID.
Example Request
puts("---Un-associate an E911 Record from a DID")
result = e911_controller.unassociate(number_id)
pp(result)
Example Response
On success, the HTTP status code in the response header is 204 No Content which means that the server successfully processed the request and is not returning any content.
---Un-associate an E911 Record from a DID
nil (204 No Content)
delete_record(e911_id)
The method accepts an E911 record ID as a parameter which you can learn more about in the API reference. Note that all phone number associations must be removed first before you are able to delete the specified E911 ID. In the following example, we will attempt to delete the previously assigned E911 ID.
Example Request
puts("---Delete an E911 Record")
result = e911_controller.delete_record(e911_id)
pp(result)
Example Response
On success, the HTTP status code in the response header is 204 No Content which means that the server successfully processed the request and is not returning any content.
---Delete an E911 Record
nil (204 No Content)
CNAM Record Management
Flowroute Ruby Library v3 allows you to make HTTP requests to the cnams resource of Flowroute API v2: https://api.flowroute.com/v2/cnams
list_cnams(options)
The method accepts limit, offset, and is_approved boolean status as parameters which you can learn more about in the API reference. In the following example request, we will only retrieve 3 approved CNAM records.
Example Request
puts("---List Approved CNAM Records")
result = cnam_controller.list_cnams(3, 0, 'true')
cnam_id = result['data'][0]['id']
pp(result)
Example Response
On success, the HTTP status code in the response header is 200 OK and the response body contains an array of cnam objects in JSON format.
---List Approved CNAM Records
{
"data": [
{
"attributes": {
"approval_datetime": "2018-04-23 17:04:30.829341+00:00",
"creation_datetime": "2018-04-19 21:03:04.932192+00:00",
"is_approved": true,
"rejection_reason": null,
"value": "BROWN BAG"
},
"id": "22790",
"links": {
"self": "https://api.flowroute.com/v2/cnams/22790"
},
"type": "cnam"
},
{
"attributes": {
"approval_datetime": "2018-05-23 18:58:46.052602+00:00",
"creation_datetime": "2018-05-22 23:38:27.794911+00:00",
"is_approved": true,
"rejection_reason": null,
"value": "LEATHER REBEL"
},
"id": "23221",
"links": {
"self": "https://api.flowroute.com/v2/cnams/23221"
},
"type": "cnam"
},
{
"attributes": {
"approval_datetime": "2018-05-23 18:58:46.052602+00:00",
"creation_datetime": "2018-05-22 23:42:00.786818+00:00",
"is_approved": true,
"rejection_reason": null,
"value": "MORBO"
},
"id": "23224",
"links": {
"self": "https://api.flowroute.com/v2/cnams/23224"
},
"type": "cnam"
}
],
"links": {
"next": "https://api.flowroute.com/v2/cnams?is_approved=True&limit=3&offset=3",
"self": "https://api.flowroute.com/v2/cnams?is_approved=True&limit=3&offset=0"
}
}
cnam_details(cnam_id)
The method accepts a cnam_id as a parameter which you can learn more about in the API reference.
In the following example, we assign the ID of the first record returned from our previous API query and retrieve the details of that specific CNAM record.Example Request
puts("---Get Details for a CNAM Record")
cnam_id = result['data'][0]['id']
result = cnam_controller.cnam_details(cnam_id)
pp(result)
Example Response
On success, the HTTP status code in the response header is 200 OK and the response body contains a detailed cnam object in JSON format.
---Get Details for a CNAM Record
{
"data": {
"attributes": {
"approval_datetime": "2018-04-23 17:04:30.829341+00:00",
"creation_datetime": "2018-04-19 21:03:04.932192+00:00",
"is_approved": true,
"rejection_reason": null,
"value": "BROWN BAG"
},
"id": "22790",
"links": {
"self": "https://api.flowroute.com/v2/cnams/22790"
},
"relationships": {
"numbers": {
"data": []
}
},
"type": "cnam"
}
}
create(cnam_value)
The method accepts a Caller ID value as a parameter which you can learn more about in the API reference. In the following example, we will reference our previously declared variable, route_alias, and pass the string as our CNAM value to the create method.
CNAM Storage Rules
Example Request
puts("---Create a CNAM Record " + route_alias.to_s)
result = cnam_controller.create(route_alias.to_s)
new_cnam_id = result['data']['id']
pp(result)
Example Response
On success, the HTTP status code in the response header is 201 Created and the response body contains the newly created cnam object in JSON format. Note that CNAM records take up to 48 hours to be approved on your account and further association with a phone number takes 5-7 business days.
---Create a CNAM Record
{
"data": {
"attributes": {
"approval_datetime": null,
"creation_datetime": "2018-07-10 23:14:28.529156+00:00",
"is_approved": false,
"rejection_reason": null,
"value": "AH76WX"
},
"id": "24169",
"links": {
"self": "https://api.flowroute.com/v2/cnams/24169"
},
"type": "cnam"
}
}
associate(number_id, cnam_id)
The method accepts a CNAM record ID and a phone number as parameters which you can learn more about in the API reference. In the following example, we will associate our previously declared `number_id` with our previously declared `cnam_id` for the "Get Details for a CNAM Record" method call.
Example Request
puts("---Associate a CNAM Record with a DID " + number_id + " with " + cnam_id)
result = cnam_controller.associate(number_id, cnam_id)
pp(result)
Example Response
On success, the HTTP status code in the response header is 202 Accepted and the response body contains an attributes dictionary containing the `date_created` field and the assigned cnam object in JSON format. This request will fail if the CNAM you are trying to associate has not yet been approved.
---Associate a CNAM Record with a DID
{'data': {'attributes': {'date_created': 'Fri, 01 Jun 2018 00:17:52 GMT'},
'id': 22790,
'type': 'cnam'}}
unassociate(number_id)
The method accepts a phone number as a parameter which you can learn more about in the API reference. In the following example, we we will disassociate the same phone number that we've used in the "Associate a CNAM Record with a DID" method call.
Example Request
puts("---Un-associate a CNAM Record from a DID " + number_id)
result = cnam_controller.unassociate(number_id)
pp(result)
Example Response
On success, the HTTP status code in the response header is 202 Accepted and the response body contains an attributes object with the date the CNAM was requested to be disassociated from the phone number, and the updated cnam object in JSON format.
---Un-associate a CNAM Record from a DID
{
"data": {
"attributes": {
"date_created": "Tue, 10 Jul 2018 23:48:50 GMT"
},
"id": null,
"type": "cnam"
}
}
delete_record(cnam_id)
The method accepts a CNAM record ID as a parameter which you can learn more about in the API reference. In the following example, we will be deleting our previously assigned new_cnam_id which is the ID of our newly created CNAM record.
Example Request
puts("---Delete a CNAM Record " + new_cnam_id)
result = cnam_controller.delete_record(new_cnam_id)
pp(result)
Example Response
On success, the HTTP status code in the response header is 204 No Content which means that the server successfully processed the request and is not returning any content.
---Delete a CNAM Record 24169
nil (204 No Content)
Errors
In cases of method errors, the Ruby library raises an exception which includes the HTTP status description and an error message. You can add more error logging if necessary.
Example Error
FlowrouteNumbersAndMessaging::ErrorException (Unauthorized – There was an issue with your API credentials.)