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
A .qvw-like label does not create a Qlik application; load and validate this text in your Qlik environment.
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 Qlik inline load script API · cURL
curl --fail-with-body --max-time 40 \
'https://api.tableconvert.com/v2/convert/xml-to-qlik' \
--header "Authorization: Bearer $TABLECONVERT_API_KEY" \
--form-string 'data=<?xml version="1.0" encoding="UTF-8" ?>
<dataset>
<record><id>101</id><product>Notebook</product><sales>1250</sales></record>
<record><id>102</id><product>Marker</product><sales>1480</sales></record>
</dataset>' \
--form-string 'output[delimiter]=,' \
--form-string 'output[table]=tableName' \
--output 'xml-to-qlik.qvs'Requires cURL. Download the sample input first when this example uploads a file.
XML to Qlik inline load script API · Python
import os
from pathlib import Path
import requests
endpoint = "https://api.tableconvert.com/v2/convert/xml-to-qlik"
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><product>Notebook</product><sales>1250</sales></record>\n <record><id>102</id><product>Marker</product><sales>1480</sales></record>\n</dataset>"),
"output[delimiter]": (None, ","),
"output[table]": (None, "tableName"),
}
response = requests.post(endpoint, headers=headers, files=fields, timeout=40)
response.raise_for_status()
Path("xml-to-qlik.qvs").write_bytes(response.content)Requires Python 3 and requests. Install it with pip install requests.
XML to Qlik inline load script API · Node.js
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><product>Notebook</product><sales>1250</sales></record>\n <record><id>102</id><product>Marker</product><sales>1480</sales></record>\n</dataset>");
form.set("output[delimiter]", ",");
form.set("output[table]", "tableName");
const response = await fetch("https://api.tableconvert.com/v2/convert/xml-to-qlik", {
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-qlik.qvs", Buffer.from(await response.arrayBuffer()));Requires Node.js 20 or later with built-in fetch, FormData and Blob.
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.
| Parameter | Type | Default | Description |
|---|---|---|---|
data | string | — | Inline XML table content. Choose one of data, file or url. |
file | binary | — | Upload a xml file using multipart/form-data. |
url | string | — | 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 Qlik LOAD INLINE script fragment containing table values. It is text for a load script, not a Qlik application file or a live analytics session.
| Parameter | Type | Default | Description |
|---|---|---|---|
output[delimiter] | string | , | Set the separator between values in the generated analytics expression or inline data. |
output[table] | string | tableName | Set the generated table identifier or label; conversion does not create a live database or analytics object. |
Conversion rules
| Case | Behavior |
|---|---|
| Mapping rule 1 | Root-level child records supply rows, and their child element names supply the union of columns. |
| Mapping rule 2 | The grid becomes an inline block under the chosen script table label. |
| Mapping rule 3 | Choose explicit XML record children and parse extracted numeric/date text after code generation; attributes are not separate analytical columns. |
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
- The table option supplies the script table label and delimiter controls inline field separation.
- The first grid row supplies inline field names; remaining rows supply records.
- Review quote characters, delimiter collisions and type interpretation in the Qlik load editor.
When to use this API
This conversion in practice
Use a record-oriented XML export as the starting dataset for a Qlik inline lookup-data draft. Move required attributes into explicit fields and flatten repeated nested groups before sending XML.
Qlik inline load script
Prepare a small inline lookup table for a Qlik load script.
Responses and errors
| HTTP status | Description |
|---|---|
200 | text/plain; charset=utf-8 |
400 | Invalid input or conversion parameters. |
402 | Insufficient credits for this request. |
403 | Missing or invalid API key. |
413 | The input exceeds the configured request limit. |
415 | Unsupported input media type. |
429 | Rate limit exceeded. |
500 | The conversion could not be completed. |
503 | The 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 creditsUsing 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 overviewReferences and format specifications
Format references explain the underlying syntax. The conversion rules and samples above describe TableConvert’s implementation.