Flowroute Telephony API
40
AI ReadinessNon-Ready (F)40/100
Agent-ready OpenAPI document · curated by JenticCommunicationsVoice Telephonybasic8 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Search and purchase phone numbers, send SMS and MMS messages, and configure call routes on Flowroute from agent code.
Use for: I need to send an SMS to a US phone number through Flowroute, I want to buy a phone number with a specific area code, Search for available 415 numbers in Flowroute's inventory, Find the delivery status of a message I sent yesterday
Not supported: Does not handle email delivery, push notifications, or video calls - use for Flowroute SMS, MMS, phone number provisioning, and call routing only.
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.
Install Jentic One Beta
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.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fflowroute.com%2Fflowroute" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fflowroute.com%2Fflowroute" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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.
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
Configure inbound routes to direct calls and messages to your endpoints
Retrieve metadata for a specific owned number
Inspect routing rules attached to numbers
Use Cases
Patterns agents use Flowroute Telephony 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
GET
/v2/routes
List configured inbound routes
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
F
Flowroute Telephony API
- Non-Ready (F)40/100
90
Foundational Compliance63
Developer Experience & Jentic Compatibility44
AI-Readiness & Agent Experience94
Agent Usability10
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
90
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: ASignals: 4
99%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
60%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
63
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B-Signals: 4
2%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
50%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
44
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: DSignals: 4
21%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
57%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
10
Security
Trust, risk posture, and security compliance.
Grade: FSignals: 1
10%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
100
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A+Signals: 1
100%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Flowroute API by hand means encoding your Access Key and Secret Key into HTTP Basic auth, tracking the split between its v2 number endpoints and v2.2 messaging endpoints, and building your own retry and error handling. Through Jentic you install once, import Flowroute from the API Directory, store the credentials once, and your agent calls it.
Permission scoping
Flowroute carries the message recipient in the request body rather than the URL path, so scoping is operations-only: you limit the agent to the operations it needs, such as sending a message or listing available numbers, and leave out purchasing a number unless you add it. Every operation the agent can run is one you chose.
Credential isolation
Your Flowroute Access Key and Secret Key are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as '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 the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Flowroute Telephony 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 with Jentic One, the self-hosted execution layer.
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 your Jentic One instance 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.
Can I limit what my agent is allowed to do with the Flowroute Telephony API?
Yes. Because Flowroute carries the message recipient in the request body rather than the URL path, scoping is done at the operation level in your own self-hosted Jentic One instance, where your rules decide which operations and credentials the agent may use. You can allow only the operations the agent needs, such as sending a message via POST /v2.2/messages or listing available numbers via GET /v2/numbers/available, while leaving out purchasing a number through POST /v2/numbers unless you add it. Every operation the agent can run is one you chose.
GET STARTED