Things to check before integrating
Before you integrate
Send only the pipe table and check escaped pipes and inline formatting in values.
Before you integrate
Source inline markup is not translated into safe wiki syntax automatically; inspect pipes and templates.
Code examples
These examples send the sample as multipart/form-data and save the returned bytes unchanged. Set TABLECONVERT_API_KEY in your environment.
Markdown table to MediaWiki table API · cURL
curl --fail-with-body --max-time 40 \
'https://api.tableconvert.com/v2/convert/markdown-to-mediawiki' \
--header "Authorization: Bearer $TABLECONVERT_API_KEY" \
--form-string 'data=| country | capital | population |
|---------|---------|------------|
| France | Paris | 68000000 |
| Japan | Tokyo | 124000000 |
' \
--form-string 'output[minify]=true' \
--form-string 'output[sort]=false' \
--form-string 'output[header]=true' \
--output 'markdown-to-mediawiki.wiki'Requires cURL. Download the sample input first when this example uploads a file.
Markdown table to MediaWiki table API · Python
import os
from pathlib import Path
import requests
endpoint = "https://api.tableconvert.com/v2/convert/markdown-to-mediawiki"
headers = {"Authorization": "Bearer " + os.environ["TABLECONVERT_API_KEY"]}
fields = {
"data": (None, "| country | capital | population |\n|---------|---------|------------|\n| France | Paris | 68000000 |\n| Japan | Tokyo | 124000000 |\n"),
"output[minify]": (None, "true"),
"output[sort]": (None, "false"),
"output[header]": (None, "true"),
}
response = requests.post(endpoint, headers=headers, files=fields, timeout=40)
response.raise_for_status()
Path("markdown-to-mediawiki.wiki").write_bytes(response.content)Requires Python 3 and requests. Install it with pip install requests.
Markdown table to MediaWiki table API · Node.js
import { writeFile } from "node:fs/promises";
const form = new FormData();
form.set("data", "| country | capital | population |\n|---------|---------|------------|\n| France | Paris | 68000000 |\n| Japan | Tokyo | 124000000 |\n");
form.set("output[minify]", "true");
form.set("output[sort]", "false");
form.set("output[header]", "true");
const response = await fetch("https://api.tableconvert.com/v2/convert/markdown-to-mediawiki", {
method: "POST",
headers: { Authorization: "Bearer " + process.env.TABLECONVERT_API_KEY },
body: form,
signal: AbortSignal.timeout(40_000),
});
if (!response.ok) {
throw new Error("HTTP " + response.status + ": " + await response.text());
}
await writeFile("markdown-to-mediawiki.wiki", Buffer.from(await response.arrayBuffer()));Requires Node.js 20 or later with built-in fetch, FormData and Blob.
Authentication
Send Authorization: Bearer YOUR_API_KEY. Let the HTTP client set the multipart boundary; do not set Content-Type manually.
Keep production API keys in server-side environment variables.
Request parameters
Pipe-delimited Markdown table rows become a rectangular dataset. The alignment separator row is removed rather than treated as data.
| Parameter | Type | Default | Description |
|---|---|---|---|
data | string | — | Inline Markdown table content. Choose one of data, file or url. |
file | binary | — | Upload a md file using multipart/form-data. |
url | string | — | A supported publicly accessible HTTP or HTTPS file URL. |
Send one source: data, file, or url. The examples below use the source mode appropriate for this format.
Output options
Generate wikitable markup with optional header and sortable-table settings. It prepares table text for a wiki editor and does not publish a page.
| Parameter | Type | Default | Description |
|---|---|---|---|
output[minify] | boolean | true | Reduce generated layout whitespace; inspect any format-specific effects on cell content. |
output[sort] | boolean | false | Add MediaWiki’s sortable table class; actual sorting depends on the wiki. |
output[header] | boolean | true | Use MediaWiki header-cell notation for the first table row. |
Conversion rules
| Case | Behavior |
|---|---|
| Mapping rule 1 | The Markdown header and body rows remain data; the alignment-only separator is discarded. |
| Mapping rule 2 | Cells become wiki table rows, with header notation and optional sortable class. |
| Mapping rule 3 | Translate the parsed grid rather than the entire Markdown document; source alignment syntax is replaced by the destination’s table rules. |
How the input is read
- Supply the table itself; prose, fenced examples and unrelated document lines should be removed first.
- The parser removes a recognized second-row alignment separator and trims cell edges.
- Escaped pipes are distinguished from cell separators, but inline Markdown is not rendered to rich text.
- Use one physical row per record; prepare multiline cell content deliberately.
How the output is written
- The first row may be emitted as MediaWiki header cells.
- Line breaks in values become br markup, while wiki syntax inside values still needs review.
- Sortable output requests a wiki class; sorting depends on the destination MediaWiki installation.
When to use this API
This conversion in practice
Use a README or documentation table as the starting dataset for a maintained MediaWiki reference table. Send only the pipe table and check escaped pipes and inline formatting in values.
MediaWiki table
Maintain a generated table on a MediaWiki documentation or reference page.
Responses and errors
| HTTP status | Description |
|---|---|
200 | text/plain; charset=utf-8 |
400 | Invalid input or conversion parameters. |
402 | Insufficient credits for this request. |
403 | Missing or invalid API key. |
413 | The input exceeds the configured request limit. |
415 | Unsupported input media type. |
429 | Rate limit exceeded. |
500 | The conversion could not be completed. |
503 | The renderer is unavailable or the request timed out. |
Check the response before retrying. A new HTTP request is a new conversion and may use credits again.
Limits, billing and versions
Local previews accept up to 200 KB. The current API implementation allows one uploaded file up to 50 MiB, limits each multipart text field to 1 MiB, and gives v2 conversion tasks a 30-second deadline. Deployment limits may be stricter. Read the returned error before retrying; some parser or renderer failures return HTTP 500.
Live calls follow the API credit policy. Failed conversions are refunded; a completed conversion is not undone if the download connection later fails.
View API pricing and creditsUsing API v1?
This page documents v2, which returns the output directly. API v1 wraps the result in a JSON envelope. Check the overview before changing an existing integration.
API overviewReferences and format specifications
Format references explain the underlying syntax. The conversion rules and samples above describe TableConvert’s implementation.