CSV to JSON for APIs: Headers, Types, Nulls, and Encoding

Confirm encoding and delimiter first

A comma is not always the separator, and UTF-8 is not the only encoding found in exported files. Misidentification can collapse a row into one column or corrupt accented characters before conversion starts.

Use Encoding & Delimiter Detector, then open Header Inspector to catch blank, duplicate, or risky column names.

Treat headers as API property names

The first row becomes object keys. Normalize headers deliberately before conversion because spaces, duplicate names, and accidental capitalization can create an incompatible payload.

customer_id,active,total
42,true,19.50

[
  {
    "customer_id": 42,
    "active": true,
    "total": 19.5
  }
]

Review inferred types and empty cells

Conservative inference can recognize unambiguous numbers and booleans, but identifiers with leading zeros often belong as strings. Empty cells may mean an empty string, null, or an omitted property depending on the receiving API.

UtilityDock preserves empty cells as strings in its focused Version 1 flow. If an API requires null or omission, review the JSON and use an explicit modification tool after conversion.

Validate the result before sending

Pretty-preview several records, confirm the row count, and validate the output against the API's JSON Schema when one is available. For one-record-per-line ingestion, convert the resulting array with JSON Lines Converter.

1. Detect encoding and delimiter.
2. Inspect and normalize headers.
3. Convert CSV rows to JSON.
4. Review identifiers, booleans, numbers, and empty values.
5. Validate against the receiving contract.

Common questions

FAQ