Skip to content
API REFERENCEv2

MediaWiki table to R data.frame code API

Prepare R data.frame construction code from a wiki-maintained data table with the TableConvert conversion API. Replace wiki links, templates and display units with plain values before creating analytical columns.

REST APIv2 · Direct outputMediaWiki table → R data.frame code1 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-rdataframe

R data.frame code response

data.frame(
  category = c("Supplies", "Equipment"),
  amount = c("125", "480"),
  region = c("North", "South")
)

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

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

Original data types are not restored automatically; validate identifiers and convert vectors before analysis.

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 R data.frame code API · cURL

curl --fail-with-body --max-time 40 \
  'https://api.tableconvert.com/v2/convert/mediawiki-to-rdataframe' \
  --header "Authorization: Bearer $TABLECONVERT_API_KEY" \
  --form-string 'data={| class="wikitable"
! category !! amount !! region
|-
| Supplies || 125 || North
|-
| Equipment || 480 || South
|}' \
  --output 'mediawiki-to-rdataframe.R'

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 R source using data.frame and one c(...) vector per column. Values are emitted as strings and the API does not execute R.

This output format does not expose additional options.

Conversion rules

CaseBehavior
Mapping rule 1MediaWiki cell separators yield table rows while presentation attributes are discarded where recognized.
Mapping rule 2Columns are transposed into character vectors named from the header.
Mapping rule 3Replace wiki links, templates and display units with plain values before creating analytical columns.

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

  • Headers become argument names and columns become quoted vectors.
  • Convert numeric, factor and date columns explicitly in R when the analysis requires them.
  • Validate R identifiers and string quoting; the returned representation is code text regardless of the download extension.

When to use this API

This conversion in practice

Use a wiki-maintained data table as the starting dataset for an R analysis or package-test fixture. Simplify wiki templates, attributes and merged cells so the intended values are explicit.

R data.frame code

Prepare reproducible data.frame construction for a small R analysis fixture.

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.