Skip to content
API REFERENCEv2

JSON to JSON Lines API

Prepare newline-delimited JSON records from an application JSON response with the TableConvert conversion API. This is a flat-record remapping, not a lossless JSON-tree conversion; missing keys, literal null text and optional scalar parsing affect the result.

REST APIv2 · Direct outputJSON → JSON Lines1 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/json-to-jsonlines

JSON Lines response

{"event":"signup","user":"alice","timestamp":"2026-10-30"}
{"event":"purchase","user":"bob","timestamp":"2026-10-31"}

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

Select and flatten the required record fields before sending nested JSON.

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.

JSON to JSON Lines API · cURL

curl --fail-with-body --max-time 40 \
  'https://api.tableconvert.com/v2/convert/json-to-jsonlines' \
  --header "Authorization: Bearer $TABLECONVERT_API_KEY" \
  --form-string 'data=[
  {
    "event": "signup",
    "user": "alice",
    "timestamp": "2026-10-30"
  },
  {
    "event": "purchase",
    "user": "bob",
    "timestamp": "2026-10-31"
  }
]' \
  --form-string 'output[parsingJSON]=false' \
  --form-string 'output[format]=object' \
  --output 'json-to-jsonlines.jsonl'

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

A nonempty array of flat objects is the clearest record input. Object keys form a union of columns; nested structures are not automatically flattened.

ParameterTypeDefaultDescription
datastring—Inline JSON table content. Choose one of data, file or url.
filebinary—Upload a json 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 newline-delimited JSON with one record or array per line. The output is JSONL text, not a single enclosing JSON array.

ParameterTypeDefaultDescription
output[parsingJSON]booleanfalseTry JSON parsing for each cell; disable it to retain text such as identifiers with significant zeros.
output[format]stringobjectChoose one object per data row or one array per grid row; array mode can include the header.

Conversion rules

CaseBehavior
Mapping rule 1The union of object keys forms the header, and each flat object supplies one row of text cells.
Mapping rule 2Object mode maps header names to one JSON object on each output line.
Mapping rule 3This is a flat-record remapping, not a lossless JSON-tree conversion; missing keys, literal null text and optional scalar parsing affect the result.

How the input is read

  • For object arrays, columns follow keys in first-seen order; missing keys yield empty cells.
  • null becomes the literal text null, while numbers and booleans become text during table normalization.
  • A nested object becomes [object Object]; an array inside a field becomes comma-joined text rather than additional rows.
  • Prepare explicit flat fields before conversion; the endpoint has no generic flatten parameter.

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 an application JSON response as the starting dataset for a line-oriented ingestion fixture. Select and flatten the required record fields before sending nested JSON.

JSON Lines

Prepare line-oriented records for a log, ingestion job or dataset fixture.

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.