Skip to content
API REFERENCEv2

XML to HTML table API

Prepare HTML table markup from a record-oriented XML export with the TableConvert conversion API. Present extracted element text as a table; XML namespace structure and attributes are not rendered as nested table structure.

REST APIv2 · Direct outputXML → HTML table1 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/xml-to-html

HTML table response

<table>
    <tr>
        <td>department</td>
        <td>owner</td>
        <td>status</td>
    </tr>
    <tr>
        <td>Support</td>
        <td>Alice</td>
        <td>Ready</td>
    </tr>
    <tr>
        <td>Sales</td>
        <td>Bob</td>
        <td>Review</td>
    </tr>
</table>

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

Move required attributes into explicit fields and flatten repeated nested groups before sending XML.

Before you integrate

Generated markup must be embedded and styled by your application; it is not a full rendered page.

Code examples

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

XML to HTML table API · cURL

curl --fail-with-body --max-time 40 \
  'https://api.tableconvert.com/v2/convert/xml-to-html' \
  --header "Authorization: Bearer $TABLECONVERT_API_KEY" \
  --form-string 'data=<?xml version="1.0" encoding="UTF-8" ?>
<dataset>
  <record><department>Support</department><owner>Alice</owner><status>Ready</status></record>
  <record><department>Sales</department><owner>Bob</owner><status>Review</status></record>
</dataset>' \
  --form-string 'output[colHeader]=false' \
  --form-string 'output[minify]=false' \
  --form-string 'output[thead]=false' \
  --form-string 'output[escape]=true' \
  --form-string 'output[div]=false' \
  --form-string 'output[tableCaption]=' \
  --output 'xml-to-html.html'

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

The importer treats each direct child of the document root as a record and its child elements as fields. It is a record extractor, not a general XML schema or XSLT transformation.

ParameterTypeDefaultDescription
datastring—Inline XML table content. Choose one of data, file or url.
filebinary—Upload a xml 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 HTML table markup from the table grid. Header, escaping, caption and div-style options affect markup, not an entire website.

ParameterTypeDefaultDescription
output[colHeader]booleanfalseMark the first column as header cells using the destination table notation.
output[minify]booleanfalseReduce generated layout whitespace; inspect any format-specific effects on cell content.
output[thead]booleanfalseGenerate explicit table-head/body sections in the destination markup.
output[escape]booleantrueEscape characters meaningful to the destination markup when cells should remain plain text.
output[div]booleanfalseUse div-based HTML table-like markup instead of semantic table elements.
output[tableCaption]stringEmpty stringAdd a caption to the generated HTML table.

Conversion rules

CaseBehavior
Mapping rule 1Root-level child records supply rows, and their child element names supply the union of columns.
Mapping rule 2The normalized cells are wrapped in table rows and cell elements.
Mapping rule 3Present extracted element text as a table; XML namespace structure and attributes are not rendered as nested table structure.

How the input is read

  • Use a root element containing repeated record elements with child-element fields.
  • Cell values use element textContent; attributes and deep tree structure are not emitted as separate columns.
  • Repeated field names within one record overwrite earlier values; normalize repeating groups first.
  • Review namespace-prefixed names before generating code identifiers or a new schema.

How the output is written

  • Cell text becomes th or td content, with optional thead handling.
  • Keep escaping enabled for untrusted plain text and review any intentional HTML.
  • Original source CSS, interactivity and merged-cell layout are not reconstructed.

When to use this API

This conversion in practice

Use a record-oriented XML export as the starting dataset for an application table view or report template. Move required attributes into explicit fields and flatten repeated nested groups before sending XML.

HTML table

Embed a generated data table into an application view or report template.

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.