REST API

The html-to-markdown converter produces accurate outputs. This allows the conversion of entire websites — useful for website migrations and other tasks.
Not convinced? Try the online demo.

The REST API can be used to automate the conversion of HTML to Markdown:

TL;DR

Base URL https://api.html-to-markdown.com
Method POST
Headers

Content-Type: application/json

and others (see below)

X-API-Key: YourApiKey

🔑 Get your API key
Request Body The HTML input
Response Body The converted Markdown output

Try it out in the terminal with cURL:

curl \
    -H 'X-API-Key: YourApiKey' \
    -H 'Content-Type: application/json' \
    -d '{ "html": "<strong>bold text</strong>" }' \
    -X POST \
    https://api.html-to-markdown.com/v1/convert

Authentication

An API key is needed to authenticate with the API.

🔑 Get your API key

When making a request, you need to pass the API key using the X-API-Key: YourApiKey header.

Note: Your API key is confidential and should be securely stored on your server. Avoid exposing it in client-side code...

Input

It is required to set the Content-Type header. This informs how the body should be decoded. 

# Request Body for Content-Type: application/json
{ "html": "<strong>bold text</strong>" }

  • Content-Type: application/json (prefered) with the input inside the "html" value.
    This is the prefered way because you can pass other keys to configure the converter.

  • Content-Type: text/html send the HTML input directly in the body.

Output

By default, the output is JSON: 

# Response Body
{ "markdown": "**bold text**" }

Note: Once you convert this markdown back to HTML you need to be careful of malicious content. Use an HTML sanitizer before displaying the HTML in the browser.

If you wish to get a different output, you can also configure the Accept header.

  • Accept: application/json (default) will return the output as json with the "markdown" key.
    This is the prefered way because it leaves the possibility of returning other information (e.g. frontmatter).

  • Accept: text/markdown will return the output directly in the response.

Rate Limits

Respectful usage of our API is encouraged. If your app creates an excessive load on the API, the API key might be revoked. Please discuss heavier usage with us beforehand.

Contact

If you have any questions, please don't hesitate to write an email.

Errors

{
  "error": {
    "code": "HEADER_XAPIKEY_MISSING",
    "title": "the header 'X-API-Key' is required",
    "detail": "did you accidentally use the 'Authorization' header?"
  }
}

Here is a list of common errors:

  • DECODE_BODY_INVALID

    there is an error parsing the body

  • DECODE_BODY_TOO_LARGE

    request body too big

  • DECODE_HTML_CONTENT_MISSING

    no content found while parsing the body as html

  • DECODE_JSON_BODY_INVALID

    error while parsing the body as json

  • DECODE_JSON_CONTENT_MISSING

    no content found while parsing the body as json

  • DECODE_MULTIPART_BODY_INVALID

    error while parsing the body as multipart form

  • DECODE_MULTIPART_CONTENT_MISSING

    no content found while parsing the body as multipart form

  • FILETYPE_UNSUPPORTED

    this file type is not supported

  • HEADER_ACCEPT_MEDIATYPE_UNSUPPORTED

    the 'Accept' header defines an unsupported value

  • HEADER_CONTENTTYPE_CHARSET_UNSUPPORTED

    the 'Content-Type' header defines an unsupported charset

  • HEADER_CONTENTTYPE_INVALID

    could not parse the 'Content-Type' header

  • HEADER_CONTENTTYPE_MEDIATYPE_UNSUPPORTED

    the 'Content-Type' header defines an unsupported mediatype

  • HEADER_CONTENTTYPE_MISSING

    the header 'Content-Type' is required

  • HEADER_XAPIKEY_INVALID

    the api key is invalid

  • HEADER_XAPIKEY_MISSING

    the header 'X-API-Key' is required

  • METHOD_NOT_ALLOWED

    this http method is not allowed

  • PATH_NOT_FOUND

    this http path is not found

  • TOO_MANY_REQUESTS

    received too many requests in the timeframe