ForHosting KIT · Data & Files

CSV to JSON

A CSV file only looks simple until you have to parse one someone else exported — inconsistent quoting, a stray BOM, numbers stored as text with leading zeros that matter. This endpoint turns a CSV into structured JSON, inferring whether each column is a number, boolean, date or string, and letting you remap messy headers into the field names your application actually expects.

● StableFree · in your browser

Run — free How it works & API

Use it from WebAPIEmailApp soonTelegram soon

The problem with treating CSV as 'just text'

CSV looks like the simplest data format there is, and that reputation is exactly what causes trouble. The specification never strictly defines how to quote a comma inside a field or what encoding to assume, so every exporter — a spreadsheet tool, an old ERP, a bank statement generator — does it slightly differently. A parser naive enough to just split on commas breaks on the first real-world file it meets. Teams that build integrations around vendor exports end up maintaining brittle regex-based parsers that fail silently the moment a field contains an unescaped quote.

What type inference actually buys you

Call POST /data/csv-to-json with your file and the task reads the header row, samples the column values, and decides per column whether it represents an integer, a decimal, a boolean, a date, or plain text — so a column of "42", "17", "3" arrives as numbers you can sum immediately, not strings you have to cast first. Values that look numeric but carry meaning as text, like a postal code with a leading zero, are left as strings rather than silently coerced, because inference is only useful when it is also careful.

Header mapping for files you do not control

Real-world CSVs rarely use the field names your database expects. A payment processor's export might label a column "Txn Date" while your schema wants transaction_date. Instead of post-processing every response, you pass a header mapping alongside the file and the endpoint renames columns during conversion, so what comes back already matches the shape your application consumes — one less transformation step to write and maintain.

A little history, briefly

CSV predates the web itself, tracing back to early business mainframe software in the 1970s, and it never went away because nothing simpler has replaced it for tabular exchange between systems that share nothing else. JSON, by contrast, grew out of JavaScript object literals in the early 2000s specifically to be easy for programs to consume directly. Converting one into the other is a bridge between two eras of data interchange, and doing it well means respecting the quirks CSV accumulated along the way.

Where it fits in an automated pipeline

Because the conversion runs asynchronously, it drops cleanly into ETL jobs, scheduled imports from partner systems, or a form-upload flow where a user drags in a spreadsheet and your app needs structured records within seconds. You get a task_id back immediately and the JSON payload arrives by webhook, ready to be inserted, validated or forwarded without your pipeline blocking on the conversion.

What you can do with it

Partner data ingestion

Convert daily CSV exports from a supplier or payment processor into JSON that maps directly onto your internal schema, without writing a custom parser per partner.

Spreadsheet upload in a SaaS app

Let end users drag in a CSV of contacts or inventory and turn it into validated JSON records your API can insert in one step.

Legacy system migration

Pull table exports from an old system that only speaks CSV and convert them into JSON documents for a modern, document-oriented database.

Scheduled ETL job

Run a nightly conversion of accumulated CSV log files into JSON before loading them into an analytics pipeline.

FAQ

Does this CSV to JSON API infer data types automatically?

Yes, each column is sampled and typed as a number, boolean, date or string automatically, so you do not need to cast values after conversion.

Can I rename columns during conversion?

Yes, pass a header mapping with your request and the output JSON will use your field names instead of the original CSV headers.

Is there a free tier to try the CSV to JSON endpoint?

The tool above runs free in your browser. The API is paid — each call draws from your prepaid ForHosting KIT balance: top up from $10.00 (it never expires), pay each request's published price, and a call with no balance returns HTTP 402. No subscription, no tokens, and a failed task is never charged.

What CSV quirks does it handle, like quoted commas or different delimiters?

The parser handles standard quoting rules for embedded commas and newlines and detects common delimiters, so exports from spreadsheet tools and business systems convert reliably.

Can I convert large CSV files or bulk batches?

Yes, submit files as separate async requests; each returns its own task_id so large batches can be tracked and processed independently.

What happens if a CSV file is malformed?

The task retries automatically up to three times; if it still cannot parse the file, you receive a clear error describing the issue and are not charged.

How do I receive the converted JSON?

Through a signed webhook, recommended for automated pipelines, or a signed link valid for 24 hours for manual retrieval.

How much does the CSV to JSON API cost?

$0.002 per request, charged only when the conversion completes successfully.

For developers — API access

Everything on this page is available programmatically. This section is for teams who want to wire it into their own systems; everyone else can just use the tool above.

API endpoint

POSThttps://api.kit.forhosting.com/data/csv-to-json

Prefer to automate it? One authenticated POST creates the task; the result comes back by webhook or a signed link. The same capability also runs here on the web, and soon from our app, email and Telegram.

Call it from your stack

curl -X POST https://api.kit.forhosting.com/data/csv-to-json \
  -H "Authorization: Bearer $KIT_KEY" \
  -H "Content-Type: application/json" \
  -d &#39;{"csv":"nombre,edad\\nAna,30\\nLuis,25"}'

const res = await fetch("https://api.kit.forhosting.com/data/csv-to-json", {
  method: "POST",
  headers: {
    "Authorization": `Bearer ${process.env.KIT_KEY}`,
    "Content-Type": "application/json"
  },
  body: JSON.stringify({
    "csv": "nombre,edad\\nAna,30\\nLuis,25"
  })
});
const { task_id } = await res.json();

import os, requests

res = requests.post(
    "https://api.kit.forhosting.com/data/csv-to-json",
    headers={"Authorization": f"Bearer {os.environ[&#39;KIT_KEY']}"},
    json={
    "csv": "nombre,edad\\nAna,30\\nLuis,25"
},
)
task_id = res.json()["task_id"]

<?php
$res = file_get_contents("https://api.kit.forhosting.com/data/csv-to-json", false, stream_context_create([
  "http" => [
    "method"  => "POST",
    "header"  => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
    "content" => &#39;{"csv":"nombre,edad\\nAna,30\\nLuis,25"}',
  ],
]));
$task = json_decode($res, true);

body := bytes.NewBufferString(`{"csv":"nombre,edad\\nAna,30\\nLuis,25"}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/data/csv-to-json", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)

Example request

{
  "csv": "nombre,edad\\nAna,30\\nLuis,25"
}

Example response

{
  "task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
  "type": "data.csv_to_json",
  "status": "queued",
  "_links": {
    "result": "/tasks/tsk_…/result"
  }
}

The API is asynchronous: the call returns a task_id immediately and the result arrives by webhook. Polling is capped at 1 req/s per task.

Pricing

Per request$0.002

Published price — no tokens, no invented credits. A failed task is never charged.

Limits

max_mb 25

Errors

HTTP	Code	Meaning
`401`	`unauthorized`	Missing or invalid API key.
`402`	`insufficient_balance`	Your balance doesn't cover the task price.
`404`	`unknown_type`	That task type doesn't exist.
`429`	`rate_limited`	Too many requests. Use the webhook instead of polling.

Read the full KIT documentation →

Run — free