Callonfe APIcallonfe.com ↗
Access structured data from callonfe.com: Onfe's phone/SMS contact details, homepage copy, FAQ, and full legal documents via 2 clean API endpoints.
What is the Callonfe API?
The Onfe API exposes 2 endpoints that return structured data from the public callonfe.com website, covering the AI phone and SMS assistant built by EatMate LLC. The get_site_overview endpoint delivers over a dozen named response fields including the official phone number in E.164 and vanity forms, company contact details, all homepage section copy, signup consent text, and links to legal documents. A companion endpoint, get_legal_document, retrieves the full text of any of the three legal documents as structured, anchor-linked sections.
No input parameters required.
curl -X GET 'https://api.parse.bot/scraper/70344187-5bae-4d99-9f59-0c71e9e7194e/get_site_overview' \ -H 'X-API-Key: $PARSE_API_KEY'
Returns the complete public copy of the Onfe homepage as structured data, in one call (two upstream fetches, no pagination). Includes the official phone number in E.164, vanity and digit forms with tel:/sms: links; the support email, company name and postal address; links to the three legal documents; the hero text; the SMS sign-up consent wording and confirmation note (plus the U.S.-numbers-only restriction shown on the form); and every homepage section with its anchor link where the page has one: what_it_does (feature cards, including the 'Group chats' claim about adding Onfe to a group text), how_it_works (steps), why_a_phone_number, get_started (four onboarding methods with their action links), trust_and_control (panels with bullet points), beta_tips (the page's beta notice and tips), faq (question/answer pairs, including device compatibility and how to stop messages), and the closing banner. All strings are the site's own wording and can be quoted verbatim. The homepage publishes no price, usage limit or waitlist; fee and usage-limit language lives in the Terms of Service (see get_legal_document). Section item lists are typed arrays of {title, body} unless noted.
No input parameters required.
{
"type": "object",
"fields": {
"hero": "object: title, tagline, lead, body, number_label, micro",
"phone": "object: e164 (+1XXXXXXXXXX), display (vanity form as shown), digits (all-numeric form), call_link (tel: URI), sms_start_link (sms: URI prefilled with START)",
"company": "object: name, product_line, address (array of address lines)",
"sections": "object keyed what_it_does, how_it_works, why_a_phone_number, get_started, trust_and_control, beta_tips, faq, closing; each has a title and, where present, anchor (URL with fragment), intro/body, and items/steps/panels arrays; faq.items are {question, answer}; get_started.items add action_label and action_link; trust_and_control.panels add points (array of strings)",
"source_url": "homepage URL the copy was read from",
"legal_links": "object: absolute URLs for privacy, terms, call_sms_consent",
"signup_form": "object: consent_text (SMS consent checkbox wording), consent_link_label, confirm_note, number_restriction",
"contact_email": "support email address"
},
"sample": {
"data": {
"hero": {
"body": "Ask a question, set a reminder, give it a task, or bring it into a conversation — not just for you, but for the people around you.",
"lead": "AI that lives in your calls and SMS.",
"micro": "No app to install. Start with the phone you already use.",
"title": "Onfe",
"tagline": "One number for everything.",
"number_label": "Call or text Onfe"
},
"phone": {
"e164": "+1 (555) 012-3456",
"digits": "(555) 012-3456",
"display": "+1 (555) 012-3456",
"call_link": "tel:+15550123456",
"sms_start_link": "sms:+15550123456?body=START"
},
"company": {
"name": "EatMate LLC",
"address": [
"123 Main St",
"Springfield, IL 62704",
"United States"
],
"product_line": "Onfe is a product of EatMate LLC"
},
"sections": {
"faq": {
"items": [
{
"answer": "Any U.S. (+1) number that can make calls and send texts. Message and data rates may apply.",
"question": "Which phones work with Onfe?"
}
],
"title": "Questions before you say hello.",
"anchor": "https://callonfe.com/#faq"
},
"closing": {
"body": "Call, text, ask, remember, connect — Onfe is one AI contact that stays with the conversation.",
"title": "Save one number. Start almost anything."
},
"beta_tips": {
"items": [
{
"body": "Onfe can't replace 911, emergency services, or urgent professional help.",
"title": "Not for emergencies"
}
],
"title": "Onfe is in beta. A few tips help."
},
"get_started": {
"intro": "However the conversation begins, it's the same Onfe on the other end.",
"items": [
{
"body": "Send START to the same number. Reply Y to confirm, then text Onfe like any contact.",
"title": "Text START",
"action_link": "sms:+15550123456?body=START",
"action_label": "Text START"
}
],
"title": "Four ways to say hello.",
"anchor": "https://callonfe.com/#start"
},
"how_it_works": {
"steps": [
{
"body": "Add Onfe to your contacts like anyone else. There's nothing to download and no account to link.",
"label": "Save",
"title": "Save one number."
}
],
"title": "Call it. Text it. Bring it in.",
"anchor": "https://callonfe.com/#how"
},
"what_it_does": {
"intro": "Onfe works inside the phone calls and texts you already have — with you, and between you and the people you talk to every day.",
"items": [
{
"body": "Add Onfe to a group text to answer questions, settle plans, and keep everyone on the same page.",
"title": "Group chats"
}
],
"title": "An AI that joins the conversation.",
"anchor": "https://callonfe.com/#what"
},
"trust_and_control": {
"title": "Helpful AI. People stay in charge.",
"panels": [
{
"body": "Onfe works with what you say and send to it — like a person you can call or text, not an app that needs your accounts.",
"title": "Nothing to hand over.",
"points": [
"No passwords, inbox access, or cards required",
"No app to download to get started",
"Reply STOP any time to opt out, HELP for help"
]
}
]
},
"why_a_phone_number": {
"body": "Onfe doesn't ask for your passwords, your inbox, or your cards. It's more like a helpful person you can call or text — one who can also join your calls and group chats, and reach the people you're connected with.",
"items": [
{
"body": "Text Onfe one-on-one, or add it to a group chat. Answers, follow-ups, and plans stay in the thread.",
"title": "Over text"
}
],
"title": "Onfe lives in the conversation, not in another app."
}
},
"source_url": "https://callonfe.com/",
"legal_links": {
"terms": "https://callonfe.com/terms",
"privacy": "https://callonfe.com/privacy",
"call_sms_consent": "https://callonfe.com/call-sms-consent"
},
"signup_form": {
"confirm_note": "Onfe will text you once to confirm. Messages start only after you reply Y or YES.",
"consent_text": "I agree to receive text messages from Onfe by EatMate LLC in response to my requests and activity. Message frequency varies. Message and data rates may apply. Reply STOP to opt out or HELP for help. Consent is not a condition of purchase.",
"consent_link_label": "SMS Consent",
"number_restriction": "U.S. numbers only. Enter 10 digits; +1 is added automatically."
},
"contact_email": "[email protected]"
},
"status": "success"
}
}About the Callonfe API
Homepage Data via get_site_overview
Calling get_site_overview returns the complete public content of the Onfe homepage in a single response. The phone field includes the number in E.164 format (+1XXXXXXXXXX), a vanity display form, an all-digit form, and ready-to-use tel: and sms: URI links. The company field provides the legal name, product line, and a postal address array. The sections object keys eight named homepage sections — what_it_does, how_it_works, why_a_phone_number, get_started, trust_and_control, beta_tips, faq, and closing — each with a title and body text. The signup_form field includes the SMS consent checkbox wording and a number restriction note, while legal_links gives absolute URLs to the Privacy Policy, Terms of Service, and Call & SMS Consent pages.
Legal Document Text via get_legal_document
The get_legal_document endpoint accepts a single required string parameter, document, which selects among terms, privacy, or call_sms_consent. The response includes a preamble array of introductory paragraphs, a sections array where each item carries an id, heading, a url deep-linking to that heading's anchor on the live page, an ordered paragraphs array, and a list_items array. The last_updated and effective_date fields surface the dates exactly as printed in the document.
Coverage and Freshness
Both endpoints read the live public pages of callonfe.com and return no paginated results — get_site_overview performs two fetches in a single call, and get_legal_document performs one. Coverage is limited to the public marketing and legal content of the Onfe product; no user account data, call logs, or SMS delivery records are included.
The Callonfe API is a managed, monitored endpoint for callonfe.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when callonfe.com 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 callonfe.com 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?+
- Monitoring the official Onfe phone number and SMS contact links for changes using the
phone.e164andphone.sms_start_linkfields. - Auditing changes to the Terms of Service or Privacy Policy by comparing
sections[].paragraphsacross periodic fetches ofget_legal_document. - Extracting the SMS consent checkbox wording from
signup_form.consent_textfor compliance documentation. - Building a reference snapshot of Onfe's beta-status notices and FAQ copy from the
beta_tipsandfaqsections ofget_site_overview. - Retrieving the company's legal name, product line, and mailing address from the
companyfield for business directory or due-diligence use. - Pulling per-section deep-link URLs from
sections[].urlinget_legal_documentto build a navigable legal document index.
| 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 Onfe or EatMate LLC offer an official developer API for callonfe.com?+
What does get_legal_document return for each section, and how do I target a specific document?+
document parameter as one of three values: terms, privacy, or call_sms_consent. The response for each section includes a heading, a deep-link anchor URL, an ordered paragraphs array, and a list_items array. The top-level last_updated and effective_date fields carry the dates as printed on the page.Does the API expose any real-time call or SMS activity data from Onfe users?+
Is historical versioning of the legal documents available?+
last_updated and effective_date fields. Historical versions are not stored or diffed. You can fork this API on Parse and revise it to add a version-archiving endpoint that records snapshots over time.Are there fields for individual FAQ items from the Onfe homepage?+
sections.faq object from get_site_overview returns the FAQ section's title and body text as a block, not as individual question-and-answer pairs. Structured Q&A extraction is not currently available. You can fork this API on Parse and revise it to add a parsed FAQ items endpoint.