Things to check before integrating
Before you integrate
Remove presentation macros and simplify merged columns before exporting plain cell values.
Before you integrate
Raw multiline or comment-like values may change meaning in the INI parser; validate the generated text.
Code examples
These examples send the sample as multipart/form-data and save the returned bytes unchanged. Set TABLECONVERT_API_KEY in your environment.
LaTeX table to INI configuration API · cURL
curl --fail-with-body --max-time 40 \
'https://api.tableconvert.com/v2/convert/latex-to-ini' \
--header "Authorization: Bearer $TABLECONVERT_API_KEY" \
--form-string 'data=\begin{table}[!ht]
\centering
\begin{tabular}{|l|l|l|}
\hline
host & port & enabled \\ \hline
app.example.com & 443 & true \\ \hline
api.example.com & 8443 & false \\ \hline
\end{tabular}
\end{table}' \
--output 'latex-to-ini.ini'Requires cURL. Download the sample input first when this example uploads a file.
LaTeX table to INI configuration API · Python
import os
from pathlib import Path
import requests
endpoint = "https://api.tableconvert.com/v2/convert/latex-to-ini"
headers = {"Authorization": "Bearer " + os.environ["TABLECONVERT_API_KEY"]}
fields = {
"data": (None, "\\begin{table}[!ht]\r\n \\centering\r\n \\begin{tabular}{|l|l|l|}\r\n \\hline\r\n host & port & enabled \\\\ \\hline\n app.example.com & 443 & true \\\\ \\hline\n api.example.com & 8443 & false \\\\ \\hline\n \\end{tabular}\r\n\\end{table}"),
}
response = requests.post(endpoint, headers=headers, files=fields, timeout=40)
response.raise_for_status()
Path("latex-to-ini.ini").write_bytes(response.content)Requires Python 3 and requests. Install it with pip install requests.
LaTeX table to INI configuration API · Node.js
import { writeFile } from "node:fs/promises";
const form = new FormData();
form.set("data", "\\begin{table}[!ht]\r\n \\centering\r\n \\begin{tabular}{|l|l|l|}\r\n \\hline\r\n host & port & enabled \\\\ \\hline\n app.example.com & 443 & true \\\\ \\hline\n api.example.com & 8443 & false \\\\ \\hline\n \\end{tabular}\r\n\\end{table}");
const response = await fetch("https://api.tableconvert.com/v2/convert/latex-to-ini", {
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("latex-to-ini.ini", 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
This input extracts rows containing ampersand-separated table cells. It does not compile TeX or render an entire LaTeX document.
| Parameter | Type | Default | Description |
|---|---|---|---|
data | string | — | Inline LaTeX table content. Choose one of data, file or url. |
file | binary | — | Upload a tex 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 one numbered INI section per data row. Column names become keys and cell values become raw text assignments.
This output format does not expose additional options.
Conversion rules
| Case | Behavior |
|---|---|
| Mapping rule 1 | Ampersand-separated LaTeX cell text becomes a row; TeX commands are not evaluated. |
| Mapping rule 2 | Each data row becomes its own numbered section and headers become assignment keys. |
| Mapping rule 3 | Use plain identifiers instead of mathematical or formatted TeX headings when creating configuration assignments. |
How the input is read
- Provide the tabular rows needed for conversion, with ampersands between cells and row terminators.
- The importer splits table text; it does not evaluate macros, packages, math or custom column definitions.
- Simplify multicolumn/multirow constructs and literal ampersands before extraction.
- Formatting commands can remain text in extracted cells; clean them when the destination expects plain values.
How the output is written
- The header defines keys and each subsequent row creates section1, section2 and so on.
- Values are emitted without a universal INI escaping layer.
- INI dialects differ; validate comments, equals signs and multiline values with the intended parser.
When to use this API
This conversion in practice
Use a LaTeX tabular dataset as the starting dataset for a repeated-section configuration draft. Remove presentation macros and simplify merged columns before exporting plain cell values.
INI configuration
Draft repeated configuration sections from a maintained settings table.
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.