Aerolase APIaerolase.com ↗
Access structured data from aerolase.com: device specs, treatment info, clinical articles, success stories, events, and more via 2 REST endpoints.
What is the Aerolase API?
The Aerolase API provides structured access to content across aerolase.com through 2 endpoints, covering device technical specifications, practitioner success stories, clinical articles, treatment pages, specialty content, and events. The discover_pages endpoint maps the full site into typed categories, and get_page_content returns structured fields tailored to each page type — including device indications, practitioner quotes, and publication dates.
No input parameters required.
curl -X GET 'https://api.parse.bot/scraper/7e183cd8-5f8c-47a2-b48d-b6c4913bf144/discover_pages' \ -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 aerolase-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: aerolase_com_api SDK — bounded, re-runnable; every call capped."""
from parse_apis.aerolase_com_api import Aerolase, PageNotFound
client = Aerolase()
# Discover all pages on the site, categorized by type
site_map = client.site_maps.discover()
print(site_map.total_pages, "total pages discovered")
# Get structured content from a device page
page = client.page_contents.get(url_path="/neo")
print(page.title, page.page_type)
# Get a success story page
try:
story = client.page_contents.get(url_path="/success-stories/a-case-study-with-smita-ohri")
print(story.title, story.page_type)
except PageNotFound as e:
print("page gone:", e.url_path)
print("exercised: site_maps.discover, page_contents.get")
Discovers all English-language page URLs on aerolase.com from the sitemap, categorized by content type (device, success_story, blog, article, specialty, event, webinar, treatment, info, other). Each entry includes the full URL and path. Use the returned paths as input to get_page_content.
No input parameters required.
{
"type": "object",
"fields": {
"categories": "object keyed by page type, each containing an array of page entries with url and path",
"total_pages": "total number of discovered English pages"
},
"sample": {
"data": {
"categories": {
"blog": [
{
"url": "https://www.aerolase.com/blogs/3-ways-aerolase-has-improved-medical-laser-technology",
"path": "/blogs/3-ways-aerolase-has-improved-medical-laser-technology"
}
],
"device": [
{
"url": "https://www.aerolase.com/neo",
"path": "/neo"
}
],
"success_story": [
{
"url": "https://www.aerolase.com/success-stories/a-case-study-with-smita-ohri",
"path": "/success-stories/a-case-study-with-smita-ohri"
}
]
},
"total_pages": 457
},
"status": "success"
}
}About the Aerolase API
Endpoints
The API exposes two endpoints. discover_pages reads the aerolase.com sitemap and returns all English-language URLs organized into categories: device, success_story, blog, article, specialty, event, webinar, treatment, info, and other. Each entry includes a url and path. The total_pages field gives a count of all discovered pages. You use the returned path values as direct input to the second endpoint.
Page Content Extraction
get_page_content accepts a url_path string — for example /neo or /success-stories/a-case-study-with-smita-ohri — and returns structured data shaped by the detected page_type. Device pages expose technical specifications and indications for use. Success story pages yield practitioner information, direct quotes, and the devices referenced. Blog and article pages return the title, publication date, section headings, and body content. The source_url field is always present so downstream consumers can trace content back to its origin.
Data Coverage
Content types span the full aerolase.com content taxonomy: laser device product pages, peer-reviewed and clinical article summaries, dermatology and aesthetics specialty pages, scheduled events and webinars, and patient treatment descriptions. Because discover_pages provides the complete typed URL inventory first, you can selectively fetch only the page types relevant to your use case rather than crawling the entire site.
The Aerolase API is a managed, monitored endpoint for aerolase.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when aerolase.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 aerolase.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?+
- Build a competitive device comparison table using technical specs and indications from device-type pages
- Aggregate practitioner success stories and quotes for medical marketing research
- Monitor aerolase.com for new clinical articles or blog posts by diffing
discover_pagesresults over time - Populate a treatment reference tool with structured data from treatment and specialty pages
- Track upcoming events and webinars by filtering the
eventandwebinarcategories fromdiscover_pages - Index aerolase.com content for a dermatology or medical aesthetics knowledge base
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does Aerolase offer an official public developer API?+
What does `discover_pages` return and how does it help me use `get_page_content`?+
discover_pages returns a categories object keyed by page type (device, success_story, blog, article, specialty, event, webinar, treatment, info, other), each containing an array of entries with url and path. The path field from any entry is exactly what you pass as url_path to get_page_content, so the two endpoints are designed to be used sequentially.Does `get_page_content` return the same fields for every page type?+
title, page_type, and source_url, but the additional structured fields vary by type. Device pages include technical specs and indications; success story pages include practitioner details and quotes; blog and article pages include publication date and headings. Pages outside recognized types return a best-effort extraction.Does the API return image URLs, pricing, or purchase information from device pages?+
Does the API cover non-English pages on aerolase.com?+
discover_pages filters to English-language URLs only. Any localized or alternate-language variants of aerolase.com pages are not included in the sitemap output. You can fork this API on Parse and revise the sitemap filtering logic to include additional language paths if they exist on the site.