Skip to content
API REFERENCEv2

JSON to DAX DATATABLE API

Prepare a DAX DATATABLE expression from an application JSON response with the TableConvert conversion API. JSON scalar types pass through text cells before code generation; explicitly cast analytical columns and prepare nested arrays first.

REST APIv2 · Direct outputJSON → DAX DATATABLE1 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-dax

DAX DATATABLE response

DATATABLE (
    "product", STRING,
    "units", INTEGER,
    "revenue", INTEGER,
    {
        { "Notebook", "12", "48" },
        { "Marker", "8", "24" }
    }
)

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

Heuristic type declarations and quoted values may need adjustment before the DAX expression is valid.

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 DAX DATATABLE API · cURL

curl --fail-with-body --max-time 40 \
  'https://api.tableconvert.com/v2/convert/json-to-dax' \
  --header "Authorization: Bearer $TABLECONVERT_API_KEY" \
  --form-string 'data=[
  {
    "product": "Notebook",
    "units": "12",
    "revenue": "48"
  },
  {
    "product": "Marker",
    "units": "8",
    "revenue": "24"
  }
]' \
  --form-string 'output[delimiter]=,' \
  --output 'json-to-dax.dax'

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 a DAX DATATABLE expression from column names and record values. It is expression text for model authoring, not a Power BI import or model deployment.

ParameterTypeDefaultDescription
output[delimiter]string,Set the separator between values in the generated analytics expression or inline data.

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 2The header creates column declarations while records become static value tuples.
Mapping rule 3JSON scalar types pass through text cells before code generation; explicitly cast analytical columns and prepare nested arrays first.

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

  • Header names become column declarations and row values become DATATABLE tuples.
  • Column types are inferred by a simple value heuristic; review numbers, booleans and blanks.
  • Generated values are quoted; validate the expression in your DAX editor before using typed columns.

When to use this API

This conversion in practice

Use an application JSON response as the starting dataset for a Power BI static lookup-table draft. Select and flatten the required record fields before sending nested JSON.

DAX DATATABLE

Draft a small static lookup table for a Power BI semantic model.

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.