Data Format Convert API
JSON / CSV / YAML
XML / XLSX
Formula Safe

Structured data. Any common format.

Convert JSON, CSV, YAML, XML, NDJSON, and XLSX with nested-value policies and spreadsheet formula escaping by default.

7 formats · including xlsxescape · formula policyflatten · nested JSONmetadata · columns + types

Convert JSON to CSV, instantly.

This calls POST /convert on the live Data Format Convert API. Edit a tiny JSON array and pick json, csv, or yaml.

Request builder
JSON records in, formatted text out.
POST /convert
Output preview
Live response from the API, plus the exact request to reproduce it.

Converting records...

Why Data Format Convert API

ETL glue without a warehouse.

Seven structured formats

JSON, CSV, TSV, NDJSON, XML, YAML, and XLSX in a single convert contract.

Nested values under control

Flatten nested objects into columns, or JSON-stringify them when a single cell is enough.

Formula-safe spreadsheets

Values that look like formulas are escaped by default. Reject or preserve when your pipeline needs it.

XLSX as base64

Workbook input and output travel as base64 inside JSON. Sheet name or index is selectable.

Conversion metadata

Columns, observed types, null counts, record count, and output size come back with every result.

No remote files

XML entity expansion is disabled. YAML uses a JSON-compatible safe schema. Nothing is stored.

/api/v1/data-format-convert

Endpoints, at a glance.

One POST convert endpoint for seven structured formats, with formula escaping on tabular output.
POST/api/v1/data-format-convert/convert

Convert records

Transform JSON, CSV, TSV, NDJSON, XML, YAML, or XLSX with nested-value and formula options.

PRIMARY
ParameterTypeRequiredDescription
inputFormatstringyesjson, csv, tsv, ndjson, xml, yaml, or xlsx.
outputFormatstringyesjson, csv, tsv, ndjson, xml, yaml, or xlsx.
datastring/object/arrayyesSource payload. XLSX uses base64.
options.formulaPolicystringnoescape (default), reject, or preserve.
options.nestedValuesstringnoflatten (default) or json-stringify.
options.includeHeadersbooleannoInclude delimited headers. Defaults to true.

Error reference

Failures you can plan for.

Every response includes a success flag and a correlationId for tracing.
400Validation Error

Invalid format, data type, or option.

401Authentication Error

Missing or invalid gateway API key. Send x-api-key or api_key with every request.

413Payload Too Large

Body exceeds the transport limit.

422Conversion Error

Malformed source or conversion failure.

429Rate Limit Error

More than 120 requests in a 15-minute window.

Example error response

{
  "success": false,
  "error": { "code": "CONVERSION_ERROR", "message": "Unable to parse input" },
  "correlationId": "1784849006651-df01"
}

FAQ

API questions developers ask first.

Which formats can I convert between?

json, csv, tsv, ndjson, xml, yaml, and xlsx. POST /convert with inputFormat, outputFormat, and data.

How are spreadsheet formulas handled?

Tabular output escapes values that begin with formula characters by default. Set options.formulaPolicy to reject or preserve when you need a different policy.

Can nested JSON become CSV columns?

Yes. options.nestedValues=flatten (default) expands nested objects. json-stringify keeps nested values as JSON strings in a single cell.

Is XLSX sent as binary?

XLSX uses base64 transport in JSON. Text formats return a string. The response always includes recordCount and conversionMetadata.

How do I authenticate requests?

Send your Datpaq API key as an x-api-key header or an api_key query parameter. Keys are created in the Datpaq dashboard and a free tier is included.

Convert structured data in one request.

JSON, CSV, and YAML with option flags for headers, pretty printing, and key sorting.