Skip to content
API REFERENCEv2

MediaWiki table to YAML records API

Prepare a YAML sequence of record mappings from a wiki-maintained data table with the TableConvert conversion API. Map simplified wiki headings to record keys and confirm repeated/multiline cells after table extraction.

REST APIv2 · Direct outputMediaWiki table → YAML records1 credits per successful conversion

Try this conversion

Inspect a real sample, preview locally, or send a live request with your own key.

Verified sample
POSThttps://api.tableconvert.com/v2/convert/mediawiki-to-yaml

YAML records response

-
  name: frontend
  region: eu
  enabled: true
-
  name: worker
  region: us
  enabled: false

Local previews use no credits and process the first imported table or worksheet.

Conversion options
A successful live request uses 1 credits.

Your key is sent only to the conversion API and is never saved by this page.

Things to check before integrating

Before you integrate

Simplify wiki templates, attributes and merged cells so the intended values are explicit.

Before you integrate

Unquoted true-like strings, embedded quotes and multiline values can change parsing; validate with the intended YAML parser.

Code examples

These examples send the sample as multipart/form-data and save the returned bytes unchanged. Set TABLECONVERT_API_KEY in your environment.

MediaWiki table to YAML records API · cURL

curl --fail-with-body --max-time 40 \
  'https://api.tableconvert.com/v2/convert/mediawiki-to-yaml' \
  --header "Authorization: Bearer $TABLECONVERT_API_KEY" \
  --form-string 'data={| class="wikitable"
! name !! region !! enabled
|-
| frontend || eu || true
|-
| worker || us || false
|}' \
  --form-string 'output[indentSize]=2' \
  --form-string 'output[arrayStyle]=block' \
  --form-string 'output[quotationStyle]=none' \
  --output 'mediawiki-to-yaml.yaml'

Requires cURL. Download the sample input first when this example uploads a file.

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

MediaWiki table cell syntax is reduced to plain rows for conversion. Wiki page expansion and template execution are outside this importer.

ParameterTypeDefaultDescription
datastring—Inline MediaWiki table content. Choose one of data, file or url.
filebinary—Upload a wiki file using multipart/form-data.
urlstring—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 a YAML sequence of row mappings with block or flow layout. Quoting and scalar interpretation require review in the consuming parser.

ParameterTypeDefaultDescription
output[indentSize]string2Set generated text indentation; it controls formatting rather than data types.
output[arrayStyle]stringblockUse block or flow style for the YAML sequence and mappings.
output[quotationStyle]stringnoneChoose YAML scalar quotation style; validate embedded quotes and multiline values separately.

Conversion rules

CaseBehavior
Mapping rule 1MediaWiki cell separators yield table rows while presentation attributes are discarded where recognized.
Mapping rule 2Header names become mapping keys and each data row becomes one sequence entry.
Mapping rule 3Map simplified wiki headings to record keys and confirm repeated/multiline cells after table extraction.

How the input is read

  • Supply a {| … |} table with clear cell and row boundaries.
  • Simplify table attributes and merged cells before conversion; wiki layout metadata is not a portable data model.
  • Wiki links, templates and inline markup are not expanded into rendered page content.
  • Confirm the extracted header and cell text before creating named records or code.

How the output is written

  • Header names become mapping keys and data rows become sequence entries.
  • Choose indentation, arrayStyle and quotationStyle for your destination workflow.
  • The generator is not a complete YAML quoting engine; validate colons, quotes, multiline values and boolean-like strings.

When to use this API

This conversion in practice

Use a wiki-maintained data table as the starting dataset for a YAML configuration or data fixture. Simplify wiki templates, attributes and merged cells so the intended values are explicit.

YAML records

Draft a small configuration or data fixture for a YAML-consuming tool.

Responses and errors

HTTP statusDescription
200text/plain; charset=utf-8
400Invalid input or conversion parameters.
402Insufficient credits for this request.
403Missing or invalid API key.
413The input exceeds the configured request limit.
415Unsupported input media type.
429Rate limit exceeded.
500The conversion could not be completed.
503The 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 credits

Using 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 overview

References and format specifications

Format references explain the underlying syntax. The conversion rules and samples above describe TableConvert’s implementation.