CSV format

Requirements and best practices for CSV files.

products.csv
namecategorypricestock
Wireless Headphoneselectronics79.99142
USB-C Hubelectronics34.9989
Laptop Standoffice49.00201
+ 844 more rows
GET/v1/apis/products
200 OK
{
"data": [{ "name": "Wireless Headphones" … }],
"total": 847,
"page": 1,
"limit": 25
}

Header row

First row = column names. These become the keys in the API response. Use unique, meaningful names.

       id,name,email,created_at 1,Alice,[email protected],2024-01-15 2,Bob,[email protected],2024-01-16 
    

Encoding

Use UTF-8. Other encodings (e.g. Windows-1252) can break accented or non-ASCII characters. Export or save as UTF-8.

File expectations

One header row + data rows. Empty rows are ignored. Large files may take longer; check plan limits on the pricing page.

CSV best practices

  • Comma-separated only. Semicolons or tabs are not supported; convert to commas first.
  • Quote cells that contain commas: "Smith, John".
  • Keep column count consistent across rows.

Common mistakes

  • No header — First row is used as headers; wrong or duplicate keys result.
  • Commas in values unquoted — Breaks parsing. Wrap in double quotes.
  • Wrong delimiter — We expect commas. Convert semicolon/tab files.
  • Inconsistent columns — Missing columns become empty; extra columns can cause issues.