Gia APIgia.chat ↗
Fetch GiaChat's SMS contact details via one endpoint: phone number, E.164 format, hero sms: link, all SMS links, and group texting status.
What is the Gia API?
The GiaChat API exposes 1 endpoint, get_sms_contact, that returns 8 structured fields from the GiaChat homepage covering the SMS keyword, displayed phone number, E.164-normalized number, the tap-to-text hero link target, every sms: link on the page, and whether the site states support for group texting. It gives developers a machine-readable snapshot of GiaChat's advertised SMS contact surface without manual parsing.
No input parameters required.
curl -X GET 'https://api.parse.bot/scraper/ce578144-1a68-46b2-89d0-12ea9b71e38f/get_sms_contact' \ -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 gia-chat-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: GiaChat SMS Contact API — fetch and inspect the advertised SMS details."""
from parse_apis.gia_chat_api import GiaChat, ExtractionFailed
client = GiaChat()
# Fetch the single SMS contact record from the GiaChat homepage.
try:
contact = client.contacts.get()
except ExtractionFailed:
print("The homepage no longer carries the SMS number block.")
raise
# Display the hero phone number and whether group texting is supported.
print(contact.sms_phone_number, "—", contact.keyword)
print("E.164:", contact.sms_phone_number_e164)
print("Group texting supported:", contact.group_texting_supported)
# Walk every sms: link found on the page.
for link in contact.all_sms_links:
print(f" {link.label} -> {link.sms_link_target}")
# Show the group-texting marketing statements verbatim.
for stmt in contact.group_texting_statements:
print(f" • {stmt}")
print("exercised: contacts.get")
Reads the GiaChat homepage in one request and returns the SMS contact details as a single object: the keyword to text ("Gia"), the displayed phone number in the site's own formatting plus an E.164 normalization, the tap-to-text link target behind the hero number, every sms: link found on the page with its label and target (the hero link's target may differ from the displayed digits; both are returned verbatim), and a group-texting verdict. group_texting_supported is true when the page contains at least one sentence mentioning "group text(s)"; the matching sentences are returned in group_texting_statements so callers can judge the claim themselves. Takes no parameters. Returns extraction_failed if the homepage no longer carries the SMS number block.
No input parameters required.
{
"type": "object",
"fields": {
"keyword": "string, the word the site asks users to text (currently \"Gia\")",
"source_url": "string, the page the data was read from",
"all_sms_links": "array of {label, sms_link_target} for every sms: link on the homepage",
"sms_phone_number": "string, phone number as displayed in the hero section",
"hero_sms_link_target": "string, the sms: URI behind the hero number link, verbatim",
"sms_phone_number_e164": "string, the displayed number normalized to E.164 (+1 prefix)",
"group_texting_supported": "boolean, true if the site states support for group texts",
"group_texting_statements": "array of sentences from the page mentioning group texts (empty if none)"
},
"sample": {
"data": {
"keyword": "Gia",
"source_url": "https://www.gia.chat/",
"all_sms_links": [
{
"label": "+1 (555) 012-3456",
"sms_link_target": "sms://1-555-012-3456"
},
{
"label": "+1 (555) 012-3456",
"sms_link_target": "sms://1-555-012-3456"
}
],
"sms_phone_number": "+1 (555) 012-3456",
"hero_sms_link_target": "sms://1-555-012-3456",
"sms_phone_number_e164": "+15550123456",
"group_texting_supported": true,
"group_texting_statements": [
"🌟 Meet Gia, your friendly AI assistant, here to revolutionize your daily life through SMS and group texts!",
"We'll notify you as soon as GiaChat is ready to transform your life through SMS and group texts!"
]
},
"status": "success"
}
}About the Gia API
What the API Returns
The single get_sms_contact endpoint reads the GiaChat homepage and returns a flat object. Core fields include sms_phone_number (the number as displayed in the hero section), sms_phone_number_e164 (that same number normalized to +1 E.164 format for direct use in telephony integrations), and keyword (currently "Gia" — the word the site instructs users to text). The hero_sms_link_target field returns the verbatim sms: URI wired to the hero number link, ready to embed in a mobile web experience.
SMS Links and Group Texting
Beyond the hero number, all_sms_links is an array of objects — each with a label and sms_link_target — covering every sms: link present on the homepage. This lets you detect if GiaChat surfaces multiple SMS entry points or changes link labels over time. The group_texting_supported boolean reflects whether the page states that group texts are supported, and group_texting_statements contains the exact sentences from the page that mention group texts (empty array if none are found).
Source Traceability
Every response includes a source_url field that records the page the data was read from, so downstream consumers can log provenance or diff responses across time. The endpoint takes no input parameters — a single call returns the full contact object.
The Gia API is a managed, monitored endpoint for gia.chat — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when gia.chat 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 gia.chat 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?+
- Embed GiaChat's current E.164 phone number (
sms_phone_number_e164) directly into a mobile app's SMS deep-link without hardcoding it - Monitor the
hero_sms_link_targetfield to detect if GiaChat rotates or updates its contact number - Use
group_texting_supportedto conditionally display group-chat feature copy on a comparison or affiliate page - Pull
all_sms_linksto verify that all advertised SMS entry points on the homepage are consistent - Log
group_texting_statementsto track exact wording changes GiaChat makes to its group texting claims over time - Sync
keywordandsms_phone_numberinto a CRM or chatbot onboarding flow that references GiaChat as an integration option
| 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 GiaChat have an official developer API?+
What exactly does get_sms_contact return regarding the phone number?+
sms_phone_number is the number formatted exactly as it appears in the hero section of the homepage, and sms_phone_number_e164 is that same number normalized to E.164 format with a +1 prefix, suitable for use in telephony SDKs and SMS APIs.