URL to Markdown

Overview

This website to markdown API converts a webpage to Markdown in one call: send any public URL and get back the page title, the Markdown text and a word count, ready for LLM, RAG and docs pipelines. URL to Markdown works by fetching the webpage content and parsing the HTML structure. It intelligently converts HTML elements to their Markdown equivalents while preserving formatting. Images are not loaded during fetch for performance, but image links are reconstructed in the output Markdown.

Live Test URL to Markdown API →

Endpoint

One host, one path per API. The block below shows this call in four languages; every one of them is the same HTTP request. Making requests covers the timeouts, retries and parameter rules that apply to all of them. The SDKs wrap the same call in a typed client.

1
2
3
4
5
6
7
8

curl -X POST https://api.apiverve.com/v1/urltomarkdown \
  -H "x-api-key: your_api_key_here" \
  -H "Content-Type: application/json" \
  -d '{
  "url": "https://example.com/",
  "includeImages": true,
  "includeLinks": true
}'

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17

const res = await fetch('https://api.apiverve.com/v1/urltomarkdown', {
  method: 'POST',
  headers: {
    'x-api-key': 'your_api_key_here',
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
  "url": "https://example.com/",
  "includeImages": true,
  "includeLinks": true
}),
});

if (!res.ok) throw new Error(`${res.status} ${await res.text()}`);

const { data } = await res.json();
console.log(data);

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15

import requests

res = requests.post(
    "https://api.apiverve.com/v1/urltomarkdown",
    headers={"x-api-key": "your_api_key_here"},
    json={
    "url": "https://example.com/",
    "includeImages": True,
    "includeLinks": True
},
    timeout=15,
)
res.raise_for_status()

print(res.json()["data"])

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28

package main

import (
	"fmt"
	"io"
	"net/http"
	"strings"
)

func main() {
	body := strings.NewReader(`{
  "url": "https://example.com/",
  "includeImages": true,
  "includeLinks": true
}`)
	req, _ := http.NewRequest("POST", "https://api.apiverve.com/v1/urltomarkdown", body)
	req.Header.Set("Content-Type", "application/json")
	req.Header.Set("x-api-key", "your_api_key_here")

	res, err := http.DefaultClient.Do(req)
	if err != nil {
		panic(err)
	}
	defer res.Body.Close()

	out, _ := io.ReadAll(res.Body)
	fmt.Println(string(out))
}

Replace your_api_key_here with the key from your dashboard. When the inputs arrive as a list rather than one at a time, batch requests run up to 200 of them through this same API in a single call.

Authentication

Send your key in the x-api-key header. That is the only auth step — there is no token exchange and no per-endpoint scope to configure. Authentication covers creating, rotating and revoking keys.

Parameters

Sent as JSON in the request body. Premium parameters are accepted on every plan but only take effect on plans that include them.

Response

Every API returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape. Response format covers the envelope, the other output formats and how premium fields are withheld.

1
2
3
4
5
6
7
8
9
10
11
12

{
  "status": "ok",
  "error": null,
  "data": {
    "url": "https://example.com/",
    "title": "Example Domain",
    "markdown": "# Example Domain\n\n\nThis domain is for use in documentation examples without needing permission. Avoid use in operations.\n\n\n[Learn more](https://iana.org/domains/example)",
    "wordCount": 20,
    "imageCount": 0,
    "linkCount": 1
  }
}

Response fields

Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.

Errors

Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change. Error handling covers the full status list and which of them are worth retrying.

Use cases

Static Site Migration

Developers moving legacy blogs to static site generators extract page titles and converted text to generate clean Markdown source files automatically.

Offline Documentation Readers

Technical writers turn public product docs into offline Markdown manuals, tracking extracted word counts across pages to structure revision bundles.

Knowledge Base Ingestion

Feed live help center URLs to internal knowledge bases, stripping unnecessary HTML markup while preserving document headings and lists for local search.

Web Page Archiving

Before third-party guides go offline, research teams store target articles as version-controlled Markdown text plus recorded image and link counts.

Other ways to use URL to Markdown

Set up URL to Markdown on APIVerve, or reach the same source a different way. Your APIVerve account and credits work on all of them — one key, one balance.

Related

More in Data Conversion: