Discover/MEDVi API
live

MEDVi APIhome.medvi.org

Access MEDVi's full telehealth product catalog via API. Retrieve GLP-1 weight loss medications, men's health, and peptide products with pricing and category filters.

This API takes change requests — .
Endpoint health
verified 2h ago
list_products
1/1 passing latest checkself-healing
Endpoints
1
Updated
2h ago

What is the MEDVi API?

The MEDVi API exposes 1 endpoint — list_products — that returns the complete MEDVi telehealth product catalog, including 6 response fields per product: name, category, type, pricing, pricing_model, and description. Products span GLP-1 weight loss medications, men's health (QUAD), and peptide/longevity treatments such as NAD+ and Sermorelin, with an optional category filter to narrow results.

This call costs5 credits / call— charged only on success
Try it
Filter products by category. Omitting returns all products across all categories.
api.parse.bot/scraper/0239c2c4-8e12-49fc-a4a5-dd14af2eb7bc/<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/0239c2c4-8e12-49fc-a4a5-dd14af2eb7bc/list_products?category=weight_loss' \
  -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 home-medvi-org-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: MEDVi Products API — browse the telehealth catalog."""
from parse_apis.home_medvi_org_api import Medvi, Category, ParseError

client = Medvi()

# List all products across every category
for product in client.products.list(limit=10):
    print(f"{product.name} ({product.category}) — {product.pricing or 'price unavailable'}")

# Filter to weight-loss medications only
try:
    wl_product = client.products.list(category=Category.WEIGHT_LOSS, limit=1).first()
except ParseError as e:
    print(f"Extraction failed ({e.code}): {e}")
    wl_product = None

if wl_product is not None:
    print(f"\nFeatured: {wl_product.name}")
    print(f"  Type: {wl_product.type}")
    print(f"  Pricing: {wl_product.pricing}")
    print(f"  Description: {wl_product.description}")

print("\nexercised: products.list / products.list(category=)")
All endpoints · 1 totalmissing one? ·

Lists all MEDVi telehealth products with their pricing, product type (injection, tablet, pill, sublingual liquid), pricing model, and category. Products span weight loss (GLP-1 medications), men's health (QUAD), and peptides/longevity (NAD+, Sermorelin). Optionally filter by category. Pricing is dynamically resolved from the site's Framer shared module for products with template-based pricing.

Input
ParamTypeDescription
categorystringFilter products by category. Omitting returns all products across all categories.
Response
{
  "type": "object",
  "fields": {
    "total": "integer count of products returned",
    "products": "array of product objects with name, category, type, pricing, pricing_model, and description"
  },
  "sample": {
    "data": {
      "total": 9,
      "products": [
        {
          "name": "Semaglutide Injection",
          "type": "injection",
          "pricing": "$116/mo",
          "category": "weight_loss",
          "description": "Compounded semaglutide injection, one shot per week",
          "pricing_model": "price_locked_monthly"
        },
        {
          "name": "GLP-1 Tablets",
          "type": "tablet",
          "pricing": "$249",
          "category": "weight_loss",
          "description": "Dissolvable GLP-1 tablet, one per day",
          "pricing_model": "starting_price"
        },
        {
          "name": "QUAD",
          "type": "sublingual_liquid",
          "pricing": "$114",
          "category": "mens_health",
          "description": "4-in-1 rapid-absorb sublingual formula with PT-141, Tadalafil, Sildenafil, and L-Citrulline for men's performance",
          "pricing_model": "starting_price"
        }
      ]
    },
    "status": "success"
  }
}

About the MEDVi API

What the API Returns

The list_products endpoint returns an array of product objects from MEDVi's telehealth catalog. Each object includes a name, a category (weight loss, men's health, or peptides/longevity), a type field indicating the delivery form (injection, tablet, pill, or sublingual liquid), a pricing value, a pricing_model describing how charges are structured, and a description summarizing the treatment. The response also includes a total integer reflecting the count of products returned.

Filtering by Category

The category parameter is optional. Omitting it returns all products across every category. Supplying a category string — for example, filtering to weight loss — narrows results to the matching segment. This makes it straightforward to build category-specific views or comparison tables without client-side filtering.

Product Coverage

The catalog covers three main treatment areas. Weight loss products include GLP-1 receptor agonist medications commonly used for metabolic health. Men's health products include the QUAD formulation. Peptide and longevity products include NAD+ and Sermorelin, which are often used in anti-aging and performance contexts. Product types vary across these categories, spanning injectables, oral tablets, pills, and sublingual liquids.

Reliability & maintenanceVerified

The MEDVi API is a managed, monitored endpoint for home.medvi.org — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when home.medvi.org 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 home.medvi.org 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
1/1 endpoint 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
  • Build a telehealth product comparison table showing pricing and delivery type across GLP-1 weight loss medications.
  • Populate a men's health treatment page with live pricing and descriptions from the MEDVi catalog.
  • Filter peptide and longevity products by category to display NAD+ and Sermorelin options with their pricing models.
  • Track changes in MEDVi product pricing over time by polling list_products and logging the pricing field.
  • Integrate MEDVi product data into a health app that surfaces treatment options by category and administration type.
  • Generate structured product feeds for affiliate or referral platforms that list telehealth medication options.
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 MEDVi have an official developer API?+
MEDVi does not publish a documented public developer API. This Parse API provides programmatic access to the product catalog data available on home.medvi.org.
What does the `list_products` endpoint return for each product?+
Each product object includes six fields: name, category, type (the delivery form such as injection, tablet, pill, or sublingual liquid), pricing, pricing_model, and description. The response also includes a total count of products returned.
Can I filter products by delivery type, such as injectables only?+
The API currently supports filtering by category only. Filtering by type (injection, tablet, etc.) is not supported as a direct parameter. You can fork this API on Parse and revise it to add a type-based filter endpoint.
Does the API expose individual product pages, clinical details, or dosing information?+
Not currently. The API covers catalog-level data: name, category, type, pricing, pricing_model, and description. Clinical details, dosing schedules, or provider notes are not included in the current response shape. You can fork it on Parse and revise to add the missing endpoint.
How fresh is the product and pricing data?+
The catalog reflects what is currently listed on home.medvi.org. MEDVi may update product availability or pricing on their site without notice, so the data freshness depends on when the API was last called against the live source.
Page content last updated . Spec covers 1 endpoint from home.medvi.org.
Related APIs in HealthcareSee all →