XML to SQL INSERT script API

Code examples

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

curl --fail-with-body --max-time 40 \
  'https://api.tableconvert.com/v2/convert/xml-to-sql' \
  --header "Authorization: Bearer $TABLECONVERT_API_KEY" \
  --form-string 'data=<?xml version="1.0" encoding="UTF-8" ?>
<dataset>
  <record><id>101</id><name>Alice</name><email>alice@example.com</email></record>
  <record><id>102</id><name>Bob</name><email>bob@example.com</email></record>
</dataset>' \
  --form-string 'output[create]=true' \
  --form-string 'output[oneInsert]=false' \
  --form-string 'output[drop]=false' \
  --form-string 'output[table]=tableName' \
  --form-string 'output[primaryKey]=' \
  --form-string 'output[dialect]=MySQL' \
  --output 'xml-to-sql.sql'

import os
from pathlib import Path
import requests

endpoint = "https://api.tableconvert.com/v2/convert/xml-to-sql"
headers = {"Authorization": "Bearer " + os.environ["TABLECONVERT_API_KEY"]}
fields = {
    "data": (None, "<?xml version=\"1.0\" encoding=\"UTF-8\" ?>\n<dataset>\n  <record><id>101</id><name>Alice</name><email>alice@example.com</email></record>\n  <record><id>102</id><name>Bob</name><email>bob@example.com</email></record>\n</dataset>"),
    "output[create]": (None, "true"),
    "output[oneInsert]": (None, "false"),
    "output[drop]": (None, "false"),
    "output[table]": (None, "tableName"),
    "output[primaryKey]": (None, ""),
    "output[dialect]": (None, "MySQL"),
}

response = requests.post(endpoint, headers=headers, files=fields, timeout=40)
response.raise_for_status()
Path("xml-to-sql.sql").write_bytes(response.content)

import { writeFile } from "node:fs/promises";

const form = new FormData();
form.set("data", "<?xml version=\"1.0\" encoding=\"UTF-8\" ?>\n<dataset>\n  <record><id>101</id><name>Alice</name><email>alice@example.com</email></record>\n  <record><id>102</id><name>Bob</name><email>bob@example.com</email></record>\n</dataset>");
form.set("output[create]", "true");
form.set("output[oneInsert]", "false");
form.set("output[drop]", "false");
form.set("output[table]", "tableName");
form.set("output[primaryKey]", "");
form.set("output[dialect]", "MySQL");

const response = await fetch("https://api.tableconvert.com/v2/convert/xml-to-sql", {
  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("xml-to-sql.sql", Buffer.from(await response.arrayBuffer()));

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.

Send one source: data, file, or url. The examples below use the source mode appropriate for this format.

Output options

Generate SQL INSERT statements and optional table-creation text for a chosen dialect. The API returns a script and does not execute it against a database.

Conversion rules

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

• Header names become column identifiers and each record becomes a VALUES tuple.
• Optional CREATE TABLE types are heuristic; review null handling, identifier quoting and dialect rules.
• The optional drop setting emits destructive SQL text; review it before any separate database execution.

When to use this API

Responses and errors

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.

References and format specifications

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

• www.w3.org
• www.postgresql.org