Example APIexample.com ↗
Retrieve the title, paragraphs, and all hyperlinks from example.com in structured JSON. One endpoint, zero parameters, clean response fields.
What is the Example API?
The Example.com API exposes 1 endpoint — get_page_content — that returns the page's main heading, all paragraph text strings, and a full array of hyperlinks with their display text and href values. The response delivers 3 top-level fields covering the complete readable content of the page, ready for programmatic use without any client-side parsing.
No input parameters required.
curl -X GET 'https://api.parse.bot/scraper/5a9f9415-490d-4fe9-a7fd-720946ed2c27/get_page_content' \ -H 'X-API-Key: $PARSE_API_KEY'
Fetches the example.com page and returns its structured content in one request: the page title, all paragraph texts, and all links with their display text and href. No parameters required — the endpoint always fetches the current state of example.com. The title is taken from the page's main heading (h1) when present, otherwise from the document title; paragraphs and links are arrays and are empty when the page has none. Returns a single Page object containing the title, a list of paragraph strings, and a list of Link objects.
No input parameters required.
{
"type": "object",
"fields": {
"links": "array of objects each with text (display text) and href (URL) keys",
"title": "string - the page title (h1 heading when present, otherwise the document title)",
"paragraphs": "array of paragraph text strings extracted from all p elements"
},
"sample": {
"data": {
"links": [
{
"href": "https://iana.org/help/example-domains",
"text": "Learn more"
}
],
"title": "Example Domain",
"paragraphs": [
"This domain is for use in documentation examples without needing permission. This is not a service, avoid relying on it for testing and monitoring purposes."
]
},
"status": "success"
}
}About the Example API
What the API Returns
The get_page_content endpoint returns a structured JSON object with three fields: title (the main heading string), paragraphs (an ordered array of paragraph text strings), and links (an array of objects each containing a text key and an href key). No input parameters are required — calling the endpoint is sufficient to retrieve the full structured content.
Response Shape
The links array covers every anchor element on the page, giving you both the visible label (text) and the destination (href) for each one. The paragraphs array preserves document order, so the first element corresponds to the first paragraph in the page's content flow. The title field reflects the primary heading, not the HTML <title> tag, so it represents the human-visible page name.
Use and Scope
Because example.com is a minimal, well-known reference page maintained by IANA, the content it exposes is small and stable. The API is well suited for testing parsing pipelines, validating structured-data workflows, or demonstrating link and text extraction against a predictable, canonical source. The response structure is consistent across calls since the source page rarely changes.
The Example API is a managed, monitored endpoint for example.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when example.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 example.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?+
- Validate a link-extraction pipeline against the predictable
linksarray from a stable reference page. - Test downstream text-processing code using the
paragraphsarray without managing your own fixture data. - Verify that
hrefvalues in thelinksarray resolve correctly as part of a URL validation workflow. - Use the
titlefield as a known-good string in integration tests for heading-parsing logic. - Demonstrate structured data extraction to stakeholders using a publicly familiar, neutral domain.
- Seed a demo dataset with real hyperlink objects (each with
textandhref) from a live source.
| 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 example.com have an official developer API?+
What does the `links` array in the response actually contain?+
links is an object with exactly two keys: text (the visible anchor label) and href (the destination URL). The array covers every hyperlink present on the page.Does the API expose the HTML `<title>` tag or metadata like description and keywords?+
title field returns the main visible heading, and the API covers paragraphs and links as the other two fields. There is no separate field for the HTML <title> tag, meta description, or other head-element metadata. You can fork this API on Parse and revise it to add those fields.