Skip to content
API REFERENCEv2

MySQL query result to XML records API

Prepare record-oriented XML text from a copied MySQL CLI query result with the TableConvert conversion API. The printed header supplies record keys, while NULL remains display text unless deliberately remapped; no database connection occurs.

REST APIv2 · Direct outputMySQL query result → XML 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/mysql-to-xml

XML records response

<?xml version="1.0" encoding="UTF-8" ?>
<dataset>
  <record><id>101</id><title>Notebook</title><available>true</available></record>
  <record><id>102</id><title>Marker</title><available>false</available></record>
</dataset>

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

Remove terminal prompts, row counts and wrapped lines; keep the printed column header.

Before you integrate

Invalid header names, raw ampersands and CDATA terminators require review before XML validation.

Code examples

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

MySQL query result to XML records API · cURL

curl --fail-with-body --max-time 40 \
  'https://api.tableconvert.com/v2/convert/mysql-to-xml' \
  --header "Authorization: Bearer $TABLECONVERT_API_KEY" \
  --form-string 'data=+-----+----------+-----------+
| id  | title    | available |
+-----+----------+-----------+
| 101 | Notebook | true      |
| 102 | Marker   | false     |
+-----+----------+-----------+
' \
  --form-string 'output[minify]=false' \
  --form-string 'output[escape]=true' \
  --form-string 'output[rootElement]=dataset' \
  --form-string 'output[rowElement]=record' \
  --form-string 'output[declaration]=true' \
  --form-string 'output[attributes]=false' \
  --form-string 'output[cdata]=false' \
  --form-string 'output[encoding]=UTF-8' \
  --form-string 'output[indentSize]=2' \
  --output 'mysql-to-xml.xml'

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

This source means copied MySQL terminal table output, not a live database connection. Border lines are removed and visible cell text is parsed.

ParameterTypeDefaultDescription
datastring—Inline MySQL table content. Choose one of data, file or url.
filebinary—Upload a txt 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 root element containing row elements with either child-field elements or attributes. This is a tabular XML representation rather than arbitrary source-tree reconstruction.

ParameterTypeDefaultDescription
output[minify]booleanfalseReduce generated layout whitespace; inspect any format-specific effects on cell content.
output[escape]booleantrueEscape characters meaningful to the destination markup when cells should remain plain text.
output[rootElement]stringdatasetName the root XML element containing all generated records.
output[rowElement]stringrecordName each record element inside the XML root.
output[declaration]booleantrueInclude an XML declaration before the generated root element.
output[attributes]booleanfalseRepresent XML row fields as attributes rather than child elements.
output[cdata]booleanfalsePlace element text in CDATA sections; inspect values containing the CDATA terminator.
output[encoding]stringUTF-8Set the XML declaration’s encoding label; verify it matches how you save the response bytes.
output[indentSize]string2Set generated text indentation; it controls formatting rather than data types.

Conversion rules

CaseBehavior
Mapping rule 1The MySQL CLI border is stripped and its printed header and rows become plain cells.
Mapping rule 2Header names become child-element or attribute names under each generated row element.
Mapping rule 3The printed header supplies record keys, while NULL remains display text unless deliberately remapped; no database connection occurs.

How the input is read

  • Paste the bordered text table returned by the MySQL command-line client.
  • No database host, password, query execution or connection is required or performed.
  • Remove row-count messages, prompts and wrapped terminal output before conversion.
  • Printed NULL values and numeric-looking cells are text; database column types are not available from the terminal rendering.

How the output is written

  • Header values become field names, while rootElement and rowElement name the surrounding nodes.
  • Choose attributes or child elements deliberately, and keep XML escaping enabled for plain text.
  • Validate element names and CDATA terminators; naming an encoding does not recreate original XML metadata.

When to use this API

This conversion in practice

Use a copied MySQL CLI query result as the starting dataset for an XML import payload. Remove terminal prompts, row counts and wrapped lines; keep the printed column header.

XML records

Prepare a simple record-oriented payload for an XML import interface.

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.