text APItext.ai ↗
Retrieve Alfi's SMS/RCS phone numbers, WhatsApp contact links, supported messaging platforms, and pre-filled starter messages from text.ai via one endpoint.
What is the text API?
The text.ai API exposes 7 response fields from the text.ai homepage via a single endpoint, get_alfi_contact_info, giving developers programmatic access to the exact phone numbers used to add Alfi to SMS, RCS, or WhatsApp group chats, the messaging platforms the site lists as supported, and the pre-filled starter message attached to the site's SMS link.
No input parameters required.
curl -X GET 'https://api.parse.bot/scraper/9a82ab3d-7e6d-427f-9eb2-bbe06bec0ea4/get_alfi_contact_info' \ -H 'X-API-Key: $PARSE_API_KEY'
Typed, relational, agent-ready
A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.
- Fully typed · autocompletes
- Objects link to objects
- Typed errors & pagination
Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:
uv add parse-sdk uv run parse init uv run parse add --marketplace text-ai-api
uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.
"""Walkthrough: Text.ai Alfi contact info — fetch and display."""
from parse_apis.text_ai_api import TextAi, ParseError
client = TextAi()
# Fetch Alfi's contact details from text.ai
try:
info = client.contact_info.get()
except ParseError as e:
print("Failed to fetch contact info:", e)
raise
# Primary SMS number for adding Alfi to a group chat
print("SMS number:", info.sms_phone_number)
# All linked phone numbers
print("All SMS numbers:", info.sms_phone_numbers)
print("WhatsApp numbers:", info.whatsapp_phone_numbers)
# Starter message the site pre-fills into the SMS link
if info.sms_prefilled_message is not None:
print("Starter message:", info.sms_prefilled_message)
# Supported messaging platforms
print("Platforms:", ", ".join(info.supported_platforms))
# The site's own platform statement, when available
if info.platform_statement is not None:
print("Platform statement:", info.platform_statement)
print("Source:", info.source_url)
print("exercised: contact_info.get")
Reads the text.ai homepage once and returns the exact phone number users can text or add to an SMS/RCS group chat to reach Alfi (taken from the site's 'sms:' links), any WhatsApp number linked on the page, the pre-filled starter message the site attaches to the SMS link, and the list of messaging platforms the page names as supported (from the fixed set SMS, RCS, iMessage, WhatsApp, Telegram, only those actually present on the page), plus the site's own platform statement sentence when present. No parameters; one request; never paginated. Phone numbers are E.164 strings with a leading '+'. sms_prefilled_message and platform_statement may be null if the site drops them.
No input parameters required.
{
"type": "object",
"fields": {
"source_url": "page the data was read from",
"sms_phone_number": "primary E.164 phone number for SMS/RCS group chats",
"sms_phone_numbers": "array of all distinct E.164 SMS numbers linked on the page",
"platform_statement": "the site's own sentence listing supported platforms, or null",
"supported_platforms": "array of messaging platform names the page mentions as supported",
"sms_prefilled_message": "starter text the site's SMS link pre-fills, or null",
"whatsapp_phone_numbers": "array of E.164 numbers behind WhatsApp chat links (may be empty)"
},
"sample": {
"data": {
"source_url": "https://www.text.ai/",
"sms_phone_number": "+1 (555) 012-3456",
"sms_phone_numbers": [
"+1 (555) 012-3456"
],
"platform_statement": "Across SMS, WhatsApp, and Telegram",
"supported_platforms": [
"SMS",
"iMessage",
"WhatsApp",
"Telegram"
],
"sms_prefilled_message": "What can you do do?",
"whatsapp_phone_numbers": [
"+1 (555) 012-3456"
]
},
"status": "success"
}
}About the text API
What the API Returns
The single get_alfi_contact_info endpoint reads the text.ai homepage and returns structured contact data for Alfi, the group-chat AI offered by text.ai. The response includes sms_phone_number (the primary E.164-formatted number for SMS and RCS group chats), sms_phone_numbers (a deduplicated array of every SMS number linked on the page), and whatsapp_phone_numbers (an array of E.164 numbers extracted from WhatsApp chat links, which may be empty if none are present).
Platform and Messaging Context
Beyond raw phone numbers, the endpoint also returns platform_statement, the site's own sentence describing which messaging services are supported (or null if absent), and supported_platforms, a parsed array of individual platform names mentioned on the page. The sms_prefilled_message field captures the starter text that the site pre-populates when a user taps the SMS link — useful for reproducing the intended onboarding flow or verifying that the message has changed. source_url records which page the data was read from.
Inputs and Freshness
get_alfi_contact_info takes no input parameters. Each call reflects whatever contact details text.ai currently shows on its homepage, so if the site updates a phone number or adds a new platform, the response will reflect that on the next request.
The text API is a managed, monitored endpoint for text.ai — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when text.ai changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official text.ai API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Monitor text.ai's listed SMS/RCS number for changes before pushing it to a customer-facing directory or help article.
- Auto-populate onboarding flows with the current
sms_prefilled_messageso users see the canonical starter text. - Verify whether text.ai has added or removed WhatsApp support by checking
whatsapp_phone_numbersperiodically. - Keep a chatbot or virtual assistant's knowledge base current with the latest
supported_platformslist. - Detect platform expansion by diffing
supported_platformsresponses over time and triggering alerts on changes. - Pull the primary
sms_phone_numberinto a mobile app's 'contact via SMS' deep link without hardcoding the number.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 200 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
| Team | $300/mo | 20,000 | 300 req/min |
| Company | $1,000/mo | 100,000 | 500 req/min |
Each endpoint has a fixed posted price per successful call — most fall between 1 and 10 credits — shown on this API's page before you run it. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does text.ai have an official developer API?+
What exactly does `get_alfi_contact_info` return for phone numbers?+
sms_phone_number is the single primary E.164 number for SMS/RCS. sms_phone_numbers is an array of all distinct SMS numbers found on the page — useful if the site links more than one. whatsapp_phone_numbers is a separate array covering WhatsApp-specific numbers; it may return an empty array if no WhatsApp link is present on the page at the time of the request.Does the API cover Alfi's behavior, conversation history, or chat transcripts?+
How current is the data returned by the endpoint?+
Can I retrieve platform support details for messaging apps beyond SMS and WhatsApp?+
supported_platforms array returns every platform name mentioned on the homepage, so coverage depends entirely on what text.ai lists there. If a platform the site doesn't currently mention becomes relevant to your use case, you can fork this API on Parse and revise it to target additional pages or sections of the text.ai site.