Things to check before integrating
Before you integrate
Reduce the input to supported INSERT rows and check quoted identifiers and literal values.
Before you integrate
The complete output is not one JSON array; consumers must parse records line by line.
Code examples
These examples send the sample as multipart/form-data and save the returned bytes unchanged. Set TABLECONVERT_API_KEY in your environment.
SQL INSERT to JSON Lines API · cURL
curl --fail-with-body --max-time 40 \
'https://api.tableconvert.com/v2/convert/sql-to-jsonlines' \
--header "Authorization: Bearer $TABLECONVERT_API_KEY" \
--form-string 'data=CREATE TABLE records (event TEXT, user TEXT, timestamp TEXT);
INSERT INTO records VALUES ('\''signup'\'', '\''alice'\'', '\''2026-10-30'\'');
INSERT INTO records VALUES ('\''purchase'\'', '\''bob'\'', '\''2026-10-31'\'');' \
--form-string 'output[parsingJSON]=false' \
--form-string 'output[format]=object' \
--output 'sql-to-jsonlines.jsonl'Requires cURL. Download the sample input first when this example uploads a file.
SQL INSERT to JSON Lines API · Python
import os
from pathlib import Path
import requests
endpoint = "https://api.tableconvert.com/v2/convert/sql-to-jsonlines"
headers = {"Authorization": "Bearer " + os.environ["TABLECONVERT_API_KEY"]}
fields = {
"data": (None, "CREATE TABLE records (event TEXT, user TEXT, timestamp TEXT);\nINSERT INTO records VALUES ('signup', 'alice', '2026-10-30');\nINSERT INTO records VALUES ('purchase', 'bob', '2026-10-31');"),
"output[parsingJSON]": (None, "false"),
"output[format]": (None, "object"),
}
response = requests.post(endpoint, headers=headers, files=fields, timeout=40)
response.raise_for_status()
Path("sql-to-jsonlines.jsonl").write_bytes(response.content)Requires Python 3 and requests. Install it with pip install requests.
SQL INSERT to JSON Lines API · Node.js
import { writeFile } from "node:fs/promises";
const form = new FormData();
form.set("data", "CREATE TABLE records (event TEXT, user TEXT, timestamp TEXT);\nINSERT INTO records VALUES ('signup', 'alice', '2026-10-30');\nINSERT INTO records VALUES ('purchase', 'bob', '2026-10-31');");
form.set("output[parsingJSON]", "false");
form.set("output[format]", "object");
const response = await fetch("https://api.tableconvert.com/v2/convert/sql-to-jsonlines", {
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("sql-to-jsonlines.jsonl", 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
Supported INSERT statements and their column lists are parsed as table text. The API does not execute SQL against a database.
| Parameter | Type | Default | Description |
|---|---|---|---|
data | string | — | Inline SQL table content. Choose one of data, file or url. |
file | binary | — | Upload a sql 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 newline-delimited JSON with one record or array per line. The output is JSONL text, not a single enclosing JSON array.
| Parameter | Type | Default | Description |
|---|---|---|---|
output[parsingJSON] | boolean | false | Try JSON parsing for each cell; disable it to retain text such as identifiers with significant zeros. |
output[format] | string | object | Choose one object per data row or one array per grid row; array mode can include the header. |
Conversion rules
| Case | Behavior |
|---|---|
| Mapping rule 1 | Supported INSERT column names and value tuples become a header and data rows without SQL execution. |
| Mapping rule 2 | Object mode maps header names to one JSON object on each output line. |
| Mapping rule 3 | INSERT column lists become record keys and tuples become rows; the result represents parsed values, not a database query result or schema migration. |
How the input is read
- Use explicit INSERT column lists and supported value tuples for predictable column mapping.
- This is text parsing, not arbitrary SQL query evaluation, schema migration or database access.
- Prepare computed expressions, dialect-specific literals and complex dumps before importing.
- Quoted identifier text and source literal semantics may need cleanup after extraction; verify nulls and escaping.
How the output is written
- Object mode uses the first row as property names and emits one object for each remaining row.
- Array mode includes table rows as JSON arrays; confirm whether the header belongs in your consumer.
- Use a line-oriented parser and review per-cell parsingJSON when preserving IDs and blanks.
When to use this API
This conversion in practice
Use a supported SQL INSERT export as the starting dataset for a line-oriented ingestion fixture. Reduce the input to supported INSERT rows and check quoted identifiers and literal values.
JSON Lines
Prepare line-oriented records for a log, ingestion job or dataset fixture.
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.