Flowroute Telephony API

Name: Flowroute Telephony API API
Brand: Flowroute Telephony API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCommunicationsVoice Telephonybasic8 EndpointsREST

For Agents

Search and purchase phone numbers, send SMS and MMS messages, and configure call routes on Flowroute from agent code.

Connect the Flowroute Telephony API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Flowroute Telephony API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Flowroute Telephony API API.

Search the Flowroute inventory for available phone numbers by area code or rate center

Purchase a number and assign it to your account through /v2/numbers

Send SMS and MMS messages via the /v2.2/messages endpoint

Look up the delivery status of a sent message by ID

GET STARTED

Start building with Flowroute Telephony API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Flowroute Telephony API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Flowroute Telephony API, keeping it validated and agent-ready. Flowroute is a US-based telephony provider offering programmatic access to phone numbers, SMS and MMS messaging, and call routing. The API uses JSON:API request and response formatting and is authenticated with HTTP Basic credentials issued from the Flowroute portal. Endpoints cover number search, purchase, message send and lookup, and route configuration.

Use Cases

Patterns agents use Flowroute Telephony API API for, with concrete tasks.

★ Programmatic SMS Sending

Send transactional SMS — order confirmations, two-factor codes, appointment reminders — by calling POST /v2.2/messages with from, to, and body fields. Flowroute returns a message ID you can later use with GET /v2.2/messages/{message_id} to read delivery status. Integration takes a few hours including credential setup and inbound webhook handling.

Send an SMS via POST /v2.2/messages from a Flowroute-owned number to +14155551234 with the body 'Your code is 482915'.

Phone Number Provisioning

Search Flowroute's inventory through GET /v2/numbers/available filtered by area code or rate center, then claim a number by posting to /v2/numbers. This suits agents that spin up dedicated numbers per campaign, customer, or test environment. The purchased number can immediately send and receive SMS and calls.

Search GET /v2/numbers/available for an SMS-capable number with area code 312 and purchase the first match via POST /v2/numbers.

Inbound Call and Message Routing

Configure /v2/routes to point inbound calls and messages at the right SIP endpoint or HTTP webhook. Useful for agents that maintain multiple destinations — for example, routing support calls to a contact center and sales calls to a sales queue. Routes are attached to specific owned numbers.

Update /v2/routes to point a specified Flowroute number at a webhook URL for inbound SMS handling.

AI Agent Telephony Integration via Jentic

Agents use Jentic's intent search to find Flowroute operations, load the schema for the SMS endpoint, and execute calls using a scoped credential. This is the recommended pattern for AI assistants that send verification codes or confirmations as part of a conversation. Jentic keeps the Basic auth credentials isolated.

Use Jentic to search 'send an SMS via Flowroute', load the POST /v2.2/messages schema, and send a message to the user's phone number with the verification code they requested.

Key Endpoints

8 endpoints — jentic publishes the only available openapi specification for flowroute telephony api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/v2/numbers/available

Search inventory for available numbers

POST

/v2/numbers

Purchase a phone number

GET

/v2/numbers/{number_id}

Retrieve metadata for an owned number

POST

/v2.2/messages

Send an SMS or MMS message

GET

/v2.2/messages/{message_id}

Look up message delivery status

GET

/v2/routes

List configured inbound routes

GET

/v2/numbers/available

Search inventory for available numbers

POST

/v2/numbers

Purchase a phone number

GET

/v2/numbers/{number_id}

Retrieve metadata for an owned number

POST

/v2.2/messages

Send an SMS or MMS message

GET

/v2.2/messages/{message_id}

Look up message delivery status

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The Flowroute Access Key and Secret Key (HTTP Basic) are stored encrypted in the Jentic vault (MAXsystem). Agents receive a scoped execution token and never see either credential, which keeps them out of prompts and logs.

Intent-based discovery

Agents search by intent (e.g. 'send an SMS via Flowroute') and Jentic returns the POST /v2.2/messages operation with its input schema, so the agent supplies from, to, and body without browsing Flowroute docs.

Time to first call

Direct Flowroute integration: 1-2 days for HTTP Basic setup, JSON:API serialization, and message status polling. Through Jentic: under an hour — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Twilio API

Mainstream global telephony platform with broader country coverage and richer voice features.

Choose Twilio when the user needs international SMS, voice, video, or programmable conferencing beyond US-focused telephony.

Alternative

Sinch API

Global SMS and voice provider with strong international reach.

Choose Sinch when the priority is multi-region SMS deliverability and operator-grade messaging at scale.

Complementary

SendGrid Mail API

Email delivery to pair with Flowroute SMS for multi-channel notifications.

Use alongside Flowroute when an agent needs to send the same notification by email as a fallback to SMS.

FAQs

Specific to using Flowroute Telephony API API through Jentic.

Why is there no official OpenAPI spec for Flowroute Telephony API?

Flowroute does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Flowroute Telephony API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Flowroute Telephony API use?

The Flowroute Telephony API uses HTTP Basic authentication with an Access Key and Secret Key generated in the Flowroute portal. Jentic stores both halves encrypted in the MAXsystem vault and constructs the Basic header on outbound calls.

Can I send MMS messages with the Flowroute Telephony API?

Yes, POST /v2.2/messages accepts both SMS and MMS payloads. Include media URLs for MMS and use a number that has MMS enabled in Flowroute's inventory.

What are the rate limits for the Flowroute Telephony API?

The OpenAPI spec does not declare explicit rate limits. Flowroute applies messaging throughput limits per number based on the number type (long code, toll-free, short code) — back off on 429 responses and consult Flowroute support for higher throughput.

How do I purchase a phone number through Jentic?

Search Jentic for 'buy a Flowroute phone number', load the GET /v2/numbers/available schema to find a candidate, then load and execute POST /v2/numbers to claim it. The new number is immediately usable for SMS and calls.

Does the Flowroute Telephony API use the JSON:API format?

Yes, both requests and responses follow JSON:API conventions. Payloads are wrapped in 'data' objects with 'type' and 'attributes' fields. Jentic handles this wrapping automatically when an agent executes the tool.