Calling and messaging made easy
For developers, by developers

Flowroute’s SDKs provide developers with tools and solutions to simplify the integration of calling and messaging capabilities into your apps and services. Today, you can access SDKs in Python, NodeJS, PHP and Ruby on Rails. Which streamlines the way you develop contextually smart interactions to differentiate the user experience.
Access the SDKs

Request access to the Flowroute API

The Flowroute API is currently in a closed beta and as such API credentials are not automatically provisioned to every Flowroute account. Follow these steps to get access.

1. Have a Flowroute account

An active Flowroute account is required to access the API. If you do not have an account, sign up for free.

2. Request an API key

Email support@flowroute.com stating that you would like to access the Flowroute API. Include your name, email address, and account tech prefix (found on your dashboard) in the email request.

 

3. View our SDKs and documentation

Once you have your credentials and API key, login to get started. Check out the developer resource center to view our latest SDKs, API documentation and tools.

“Switching from Twilio to Flowroute made our application viable.”
Mark, Co-founder

Features and functionality

[tabby title=”Inbound calling” open=”yes”]

• Ensure all calls get through with unlimited call channels.
• Gain a local presence with local numbers across the US and Canada.
• Boost reachability with North American toll-free numbers.
• Search, add, and drop local and toll-free numbers through our RESTful API.

[tabby title=”Outbound calling”]

• Get high quality audio with low latency because call audio isn’t proxied through Flowroute servers.
• Always have enough call channels with unlimited outbound trunks
• Protect your investment with customizable fraud controls
• Real-time traffic monitoring shuts down fraudulent traffic coming  your account

[tabby title=”ID Services”]

• Display the name associated with each caller using CNAM Lookup
• Transmit a unique customizable name with CNAM Storage
• Identify extensions down to the room with our advanced E911 service
• Track traffic, usage, and forwarding with advanced signaling fields

[tabbyending]

1. Identify phone type

The ISUP-OLI field contains the originating line identifier, a.k.a. ANI-II or calling party category (CPC). This feature is useful for toll-free billing, and internal tracking and routing.

2. Manage caller ID

Caller ID is passed through the P-Asserted-Identity field. Use this field to customize Caller ID on outbound calls. For toll-free inbound, and on all inbound services for carrier customers, Flowroute passes private and restricted caller IDs in this field.

3. Maintain privacy

The Privacy: id header carries Caller ID privacy restriction. When included on an inbound SIP INVITE, it shows a privacy request for the call. Privacy: id allows you to pass a Caller ID for outbound calls while restricting it from presentation.

4. Call forwarding

Call forwarding history is passed through the Diversion header. This field contains the call legs taken to reroute a call to its eventual destination. It’s crucial in call routing and message delivery logic for voicemail systems.

5. Label your calls

The X-Tag header supports CDR tagging. You can add custom labels your CDRs for easier identification and management. Inbound calls can be labeled with an X-Tag when the header is included in a response.

6. Prevent runaway calls

Session timers are supported through the Session-Expires and Min-SE headers to ensure that calls are terminated when you hang up.

1. Identify phone type

The ISUP-OLI field contains the originating line identifier, a.k.a. ANI-II or calling party category (CPC). This feature is useful for toll-free billing, and internal tracking and routing.

2. Manage caller ID

Caller ID is passed through the P-Asserted-Identity field. Use this field to customize Caller ID on outbound calls. For toll-free inbound, and on all inbound services for carrier customers, Flowroute passes private and restricted caller IDs in this field.

3. Maintain privacy

The Privacy: id header carries Caller ID privacy restriction. When included on an inbound SIP INVITE, it shows a privacy request for the call. Privacy: id allows you to pass a Caller ID for outbound calls while restricting it from presentation.

4. Call forwarding

Call forwarding history is passed through the Diversion header. This field contains the call legs taken to reroute a call to its eventual destination. It’s crucial in call routing and message delivery logic for voicemail systems.

5. Label your calls

The X-Tag header supports CDR tagging. You can add custom labels your CDRs for easier identification and management. Inbound calls can be labeled with an X-Tag when the header is included in a response.

6. Prevent runaway calls

Session timers are supported through the Session-Expires and Min-SE headers to ensure that calls are terminated when you hang up.

Phone number management and messaging API

The Flowroute API will allow you to quickly program voice and messaging services into your applications.

 

• Send and receive SMS: Create customer interactions via text messaging from an existing toll-free or long code phone number.
• View current and add new phone numbers: Manage all phone numbers including adding new phone numbers from Flowroute’s inventory.
• Manage phone number routing: Add and change routing in real-time.

Stay tuned for the release of our intuitive, extensible, and RESTful API.