Discover/Leadomi API
live

Leadomi APIleadomi.com ↗

Access Leadomi's pricing plans and resource guides via API. 3 endpoints return plan details in GBP, guide listings, and full guide text for the UK trade market.

Endpoint health
verified 2h ago
list_pricing_plans
list_resources
get_resource
3/3 passing latest checkself-healing
Endpoints
3
Updated
3h ago

What is the Leadomi API?

The Leadomi API provides 3 endpoints that expose public data from leadomi.com, a missed-call text-back service aimed at UK trade businesses. The list_pricing_plans endpoint returns every subscription plan with parsed GBP prices, setup fees, feature lists, and call-to-action links in a single call. The other two endpoints cover the site's resource guide library, letting you list all guides and fetch the full structured text of any individual guide by slug.

This call costs1 credit / call— charged only on success
Try it

No input parameters required.

→ api.parse.bot/scraper/5d1c88da-dc27-4cc7-960e-7612d3c447c8/<endpoint>
Ready to send
Fill in the parameters and hit sign in to send to see live response data here.
Call it over HTTPgrab a free API key at signup
curl -X GET 'https://api.parse.bot/scraper/5d1c88da-dc27-4cc7-960e-7612d3c447c8/list_pricing_plans' \
  -H 'X-API-Key: $PARSE_API_KEY'
Python SDK · recommended

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 leadomi-com-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: Leadomi SDK — pricing plans and resource guides."""
from parse_apis.leadomi_com_api import Leadomi, GuideNotFound

client = Leadomi()

# Fetch pricing in one call — no pagination, just a typed wrapper.
pricing = client.pricing.get()
print(pricing.page_title, f"({pricing.currency})")
for plan in pricing.plans:
    print(f"  {plan.name}: £{plan.monthly_price_gbp}/mo, setup £{plan.setup_fee_gbp}")

# List every published guide summary; limit caps total items.
for guide_summary in client.guide_summaries.list(limit=5):
    print(guide_summary.title, f"[{guide_summary.category}]")

# Drill into the first guide via the summary→detail navigation.
summary = client.guide_summaries.list(limit=1).first()
if summary is not None:
    guide = summary.details()
    print(guide.title)
    for section in guide.sections or []:
        if section.heading:
            print(f"  ## {section.heading}")
        for paragraph in section.paragraphs:
            print(f"    {paragraph[:100]}")

# Point lookup by slug discovered from the listing above.
if summary is not None:
    same_guide = client.guides.get(slug=summary.slug)
    print(same_guide.title, same_guide.url)

# Typed error handling for a guide that does not exist.
try:
    client.guides.get(slug="nonexistent-guide")
except GuideNotFound:
    print("Guide not found — expected for an unknown slug.")

print("exercised: pricing.get / guide_summaries.list / details / guides.get")
All endpoints · 3 totalmissing one? ·

Returns every subscription plan shown on the public pricing page in one request: plan name, optional badge, description, one-off setup fee and monthly price in GBP (parsed numbers, with the original monthly label kept), the bullet feature list and the plan's call-to-action link. One page load, no pagination. badge and setup_fee_note are null when the plan card does not show them.

Input

No input parameters required.

Response
{
  "type": "object",
  "fields": {
    "plans": "array of plan objects: name, badge, description, setup_fee_gbp, setup_fee_note, monthly_price_gbp, monthly_price_label, features (array of strings), cta_label, cta_url",
    "currency": "ISO currency code of the prices (GBP, as shown on the site)",
    "page_title": "heading of the pricing page"
  },
  "sample": {
    "data": {
      "plans": [
        {
          "name": "Starter",
          "badge": "Money-Back Guarantee",
          "cta_url": "https://www.leadomi.com/terms#usage-billing",
          "features": [
            "Missed-call text-back on your existing number",
            "One business number, calendar and service area"
          ],
          "cta_label": "Usage and billing details",
          "description": "Done-for-you missed-call recovery for a UK trade firm. We set up your reply flow, questions and alerts around the way you work.",
          "setup_fee_gbp": 197,
          "setup_fee_note": "Non-refundable setup fee",
          "monthly_price_gbp": 297,
          "monthly_price_label": "£297 /month"
        },
        {
          "name": "Managed",
          "badge": null,
          "cta_url": "https://www.leadomi.com/terms#usage-billing",
          "features": [
            "Everything in Starter",
            "SMS and WhatsApp follow-up"
          ],
          "cta_label": "Usage and billing details",
          "description": "For busy firms that want Leadomi to manage a fuller enquiry and follow-up system across phone, web and WhatsApp.",
          "setup_fee_gbp": 1997,
          "setup_fee_note": null,
          "monthly_price_gbp": 497,
          "monthly_price_label": "£497 /month"
        }
      ],
      "currency": "GBP",
      "page_title": "Predictable Plans & Pricing for UK Trade Firms"
    },
    "status": "success"
  }
}

About the Leadomi API

Pricing Plan Data

list_pricing_plans returns the complete set of subscription plans from Leadomi's public pricing page. Each plan object includes name, optional badge, description, setup_fee_gbp, setup_fee_note, monthly_price_gbp, monthly_price_label, a features array of bullet-point items, and a CTA link. Prices are parsed numbers in GBP; the currency field always returns GBP and page_title carries the page heading. No input parameters are required.

Resource Guide Listing

list_resources returns the full contents of Leadomi's Resources section in one unpaginated call. Each entry in the resources array includes slug, title, category, summary, and url. The count field reports how many guides were returned. Because the library is small and not paginated, a single request is sufficient to enumerate all published guides.

Full Guide Content

get_resource takes a single required slug parameter — the last path segment of a guide URL, as returned by list_resources — and returns the guide's complete text. Content is structured as a sections array, where each element has a heading (null for intro content before the first heading) and a paragraphs array of text blocks. The trailing call-to-action block appears as the final section. The response also includes url, title, and meta_description (null if absent on the source page).

Reliability & maintenanceVerified

The Leadomi API is a managed, monitored endpoint for leadomi.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when leadomi.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 leadomi.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.

Last verified
2h ago
Latest check
3/3 endpoints passing
Maintenance
Monitored & self-healing
Will this API break when the source site changes?+
It's built not to. Every endpoint is health-checked on a schedule with automated test probes. When the source site changes and a check fails, the API is automatically queued for repair and re-verified — that's the self-healing layer. Each API page shows when its endpoints were last verified. And because marketplace APIs are shared, any fix reaches everyone using it.
Is this an official API from the source site?+
No — Parse APIs are independent, managed REST wrappers over publicly available data. That is the point: where a site has no official API (or only a limited one), Parse gives you a maintained, monitored endpoint for that data and keeps it working as the site changes — so you get a stable contract over a source that never promised one.
Can I fix or extend this API myself if I need a new endpoint or field?+
Yes — and you don't have to wait on us. This API was generated by the Parse agent, which stays attached. Describe the change in plain English ("add an endpoint that returns reviews", "fix the price field") in the revise box on the API page or via the revise_api MCP tool, and the agent rebuilds it against the live site in minutes. Contributing the change back to the public API is free.
What happens if I call an endpoint that has an issue?+
Errors are machine-readable: a bad call returns a clean status with the list of available endpoints and a repair hint, so an agent (or you) can recover or trigger a fix instead of failing silently. Confirmed failures feed the automatic repair queue.
Common use cases
  • Comparing Leadomi subscription tiers by setup fee and monthly price in GBP to build a pricing comparison tool
  • Monitoring changes to Leadomi's plan feature lists or CTA links over time
  • Building a content index of Leadomi's trade-focused resource guides by category and summary
  • Extracting full guide text by slug to feed into a knowledge base or chatbot for UK trade businesses
  • Aggregating small-business SaaS pricing data from UK-focused service providers
  • Pulling guide meta descriptions and titles for SEO research on missed-call and text-back marketing topics
Pricing & limitsSee full pricing →
TierPriceCredits/monthRate limit
Free$0/mo2005 req/min
Hobby$30/mo1,00020 req/min
Developer$100/mo5,000100 req/min
Team$300/mo20,000300 req/min
Company$1,000/mo100,000500 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.

Frequently asked questions
Does Leadomi offer an official developer API?+
Leadomi does not publish a public developer API. The Parse API is the only programmatic way to access their public pricing and resource guide data.
What does list_pricing_plans return beyond just a price number?+
Each plan object includes the plan name, an optional badge, a short description, the one-off setup fee in GBP plus a setup fee note, the monthly price as a parsed number alongside the original monthly label as displayed on the site, an array of feature bullet points, and the plan's call-to-action link. The top-level response also carries the page title and the ISO currency code GBP.
Does get_resource return images or embedded media from guide pages?+
No. The endpoint returns text content only: section headings, paragraphs, and list items in page order, plus the guide title and meta description. Images and embedded media are not included in the response. You can fork this API on Parse and revise it to add image URL extraction if that data is needed.
Is there an endpoint for blog posts or news updates separate from the resource guides?+
Not currently. The API covers the Resources guide library and the pricing page. If Leadomi publishes blog posts or news content under a different section, those are not exposed. You can fork the API on Parse and revise it to add an endpoint targeting that content.
Can I filter list_resources by category?+
list_resources returns all guides in a single call with no filter parameters. The category field is included in each guide object, so filtering by category can be done client-side on the returned array. The API does not currently support server-side filtering; you can fork it on Parse and revise it to add that capability if needed.
Page content last updated . Spec covers 3 endpoints from leadomi.com.
Related APIs in B2b DirectorySee all →