Download Flowroute

Overview Flowroute understands the need for immediate assistance and is constantly working on addressing communications needs for its end users. We have expanded our API offerings to now include the ability to programmatically add a valid and highly precise E911 address to your account – including an address type and a corresponding address type number; e.g. Apartment 108 – and associate your newly created E911 record with any of your local (long code) phone numbers. West has put together a great blog post outlining the importance of identifiable e911 locations, and the difference additional information can make for first responders to emergency calls. New to Number Management with Flowroute? This guide assumes that you have an activated Flowroute account and have followed the instructions on Purchase Your First Flowroute Phone Number. Steps Validate and create an E911 record via cURL via the Flowroute Python Library v3 Associate the E911 address with your phone number via cURL via the Flowroute Python Library v3 Verify the E911 and number association in Manage Validate and create an E911 record To associate an E911 address with a local (long code) phone number on your account, you must create a record for the E911 address first. Flowroute's E911 API has two endpoints you can hit to validate the E911 address that you want to add to your account: Endpoint Description Lets you validate and post an E911 address as a record on your Flowroute account. Lets you post an E911 address for validation only. For brevity's sake, we will show you how to work with the first endpoint. For a list of accepted body parameters and an example request, see Create and Validate a New E911 Address. The Flowroute API v2 provides an alternative programmatic way for you to validate and add an E911 address to your account. To only check on the validity of your E911 address, see Validate an E911 Address. For the Manage method of validating and adding an E911 address to your account, see Create an E911 Entry. In this tutorial, we will show you two methods of validating and adding

This guide covers how to set up Flowroute messaging service with the third-party Textable app for use on desktop or mobile devices. IMPORTANT: You should already have an SMS-enabled number with a valid 10DLC and Campaign plus an active SMS billing plan prior to beginning this guide.Log in to your Flowroute account and navigate to the “DIDs” menu to view your SMS-enabled numbers under the “Manage” tab. Your numbers should read as Registered in the “Messaging Status” column. Once you have verified this, you are ready to begin setting up Textable. Keep this tab open. You will return to the Flowroute Customer Portal in latter steps for final configuration with the SMS API credentials.The DID shows “Registered” with the “10DLC Brand ID” and “10DLC Campaign ID” fields populated (redacted).Open another tab and navigate to the Textable website and then create an account. NOTE: You will need to configure the account via the Textable website before you can utilize the mobile app for texting service. Numbers are not configurable via the app.Once you have created a Textable account, navigate to the “My Profile” menu and view the “Account Details” tab. Enter your name and email. In the “Phone Number” field, enter your SMS-enabled number. Depending on your account, choose Flowroute as the “Provider” option in the dropdown menu.The Access Key and Secret Key fields need to be filled in next. Retrieve these from the Flowroute portal. In the Flowroute portal, navigate to the “Preferences” menu and then to the “API Control”

View Repo Overview AWS (Amazon Web Services) has made a lot of waves in the world of cloud computing with its array of cloud services that you can customize to best fit your IT environment. Flowroute is excited to be leveraging their cloud services through the Serverless Framework. In this tutorial, you will learn how to set up a robust and responsive inbound SMS service. You will be diving into AWS Lambda, Amazon API Gateway, and DynamoDB. Follow along and you’ll be sending text messages to your Flowroute number within 10 minutes or so. New to SMS with Flowroute? If you want to understand the basics of how inbound SMS is handled with Flowroute, check out Receive an Inbound Message. Requirements An activated Flowroute account A Flowroute phone number Node.js v4 or higher (required for Serverless) Serverless Framework v1.x An AWS account Setup 1. Add IAM Security Credentials to your local machine Since the example AWS account in this tutorial features multiple users, we have followed Creating, Modifying, and Viewing Access Keys (Console) to create and retrieve access keys for our specific IAM (Identity and Access Management) user. You can also refer to the official Serverless AWS - Credentials guide. Start a command shell session and create a directory for AWS. mkdir ~/.aws After that, create a file for your newly generated access key. You can name it credentials and save it as your default AWS profile.[default]aws_access_key_id=aws_secret_access_key= Alternatively, Serverless provides a convenient way to configure AWS profiles with the help of the serverless config credentials command. Here's an example how you can configure the default AWS profile: serverless config credentials --provider aws --key ACCESS_KEY --secret SECRET_KEY 2. Install Serverless Framework The official Serverless documentation covers installation of Node.js and the Serverless Framework in a very straightforward manner. Depending on your npm permissions, you may be required to preface each npm command with sudo. npm install -g serverless 3. Create Inbound SMS service Use the create command to create your service. You must also pass in a runtime (e.g., node.js, python etc.) that you would like to write the service in. You will be using python in this guide. sls create --template aws-python In running the create command, you will have generated boilerplate template files - handler.py, serverless.yml, and .gitignore. With the aws-python template above, you can define your AWS Lambda Functions, the events that trigger them and any AWS infrastructure

A valuable resource to help developers add communications capabilities into applications quickly and without a significant coding and testing effort. What you'll learn The basics of CPaaS—how it works, benefits, use cases, and trendsHow CPaaS compares to CCaaS and how to choose between themCore components and characteristics of CPaaSOverview of CPaaS APIsTips for selecting a CPaaS partner Why Organizations Love Flowroute Ready why organizations highly recommend Flowroute and trust their business-critical voice applications with us. "I use Flowroute to hold DIDs and for call trunking. The support is amazing, which we all know can be hard to find. I know that if I ever need help or have an issue, it will be resolved quickly." - David Scanlan "Flowroute provides an easy-to-use interface with friendly staff and support to help with any potential issues along the way. Flowroute's support is timely and helpful compared to other organizations we have worked with in the past for DID management." - Financial Services Organization "We can't afford a carrier outage that causes inbound callers not to get through. We have peace of mind that if there is a problem anywhere in the call routing, Flowroute's HyperNetwork will keep us operating as usual. We don't even think about it." - Healthcare Provider Get your free eBook & learn about CPaaS concepts and features you need to know Complete this form to access the eBook.

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 Content Potential Error Codes Return codes in the 400 range typically indicate that there was an issue with the request that was sent. Among other things, this could mean that you did not authenticate correctly, that you are requesting an action that you do not have authorization for, that the object you are requesting does not exist, or that your request is malformed. If you receive a status in the 500 range, this generally indicates a server-side problem. This means that we are having an issue on our end and cannot fulfill your request currently. Here is a list of general errors that you can expect from the Flowroute API. Please refer to the Create and Validate an E911 Address and Assign an E911 Address to Your Phone Number API reference pages for more example errors, an explanation on the accepted request parameters, and other ways to validate and add an E911 address, and associate it with your Flowroute phone number via the API. Verify the E911 and number association in Manage To confirm that your E911 address has been properly assigned to your specified phone number, visit Accounts > Manage your DIDs of the Manage portal. Search for your phone number and review the E911 column of the number record. Notice how pointing the cursor at the E911 label displays the full E911 address. That's it -- you have successfully used the Flowroute API to create an E911 record and assign the newly added address to a phone number on your Flowroute account. For further testing and verification of the association, see Test your E911-enabled phone number using X-Lite.

An E911 address to your account using the Flowroute API v2: Request via cURL Open a command shell session. If you haven't installed cURL previously, download your specific source package here. Copy the following example POST request. curl \-X POST -u accessKey:secretKey \-d '{"data": {"type": "e911", "attributes":{"label": "Pioneer Square Office", "first_name": "Bob", "last_name": "Law", "street_number": "506", "street_name": "2nd Ave", "address_type": "Suite", "address_type_number": "601", "city": "Seattle", "state": "WA", "country": "US", "zip": "98104"}}}' \-H 'Content-Type':'application/vnd+api.json' Replace accessKey:secretKey with your API credentials. In the JSON body parameters section of your cURL request right after the cURL -d flag, replace all the attributes with your E911 address details following the Body Parameters section of "Create and Validate a New E911 Address". Press Enter. Tips To avoid errors, make sure to: Enter your API credentials correctly. Use vertical quotes in your request. Learn more about Unicode and and ISO 10646 standards in ASCII and Unicode quotation marks. Use a backslash (\) at the end of lines to break up a long cURL statement into easier-to-read lines if you're in a UNIX environment. If you're using Windows, replace any backslash at the end of lines with the caret (^) character. Here's a great guide for installing and using cURL. Request via Python To begin, follow the Requirements and Installation sections of the library guide. Open up your preferred text editor and start writing Python code. vim e911-test.py Import the following required libraries. import pprintimport osimport jsonfrom flowroutenumbersandmessaging.flowroutenumbersandmessaging_client import FlowroutenumbersandmessagingClient Assign your Flowroute AccessKey and SecretKey to the following variables or set them as environment variables. basic_auth_user_name = "YOUR_FR_ACCESS_KEY"basic_auth_password = "YOUR_FR_SECRET_KEY" Next, instantiate the API Client and the e911s controllers. client = FlowroutenumbersandmessagingClient(basic_auth_user_name, basic_auth_password)e911s_controller = client.e911s Lastly, specify your body parameters and invoke the Python library v3 create_address method. print("\n--Create and Validate an Address")try: result = e911s_controller.create_address( label="Pioneer Square Office", first_name="Bob", last_name="Law", address_type="Suite", Address_type_number = "601", street_name="2nd Ave", street_number="506", city="Seattle", state="WA", country="US", zipcode="98101") pprint.pprint(result)except Exception as e: print(str(e)) print(e.context.response.raw_body) You're done coding, at least for the E911 address validation and creation portion of this tutorial. Save the file and run it. python e911-test.py Flowroute API Create and