How CSVJetty works

The import workflow

• The user chooses a CSV file inside your application.
• CSVJetty parses the file and reads its headers.
• Uploaded headers are matched to the fields configured on your importer.
• The user reviews or changes those matches.
• CSVJetty validates each mapped value and shows corrections inline.
• The user fixes errors or follows your configured invalid-row behavior.
• Validated records are delivered by callback or webhook.
• Your application performs final server-side validation and saves the data.

The result is a predictable record shape even when customers upload files with different header names or inconsistent values. See how matching works in Column mapping.

What happens in the browser

File parsing, column mapping, built-in validation, inline corrections, and custom synchronous validators run in the importer experience in the user's browser.

What CSVJetty manages

• The upload and review interface.
• Your reusable importer configuration.
• Header matching and aliases.
• Built-in field validation and type conversion.
• Inline correction of invalid values.
• Optional filtering or blocking of invalid rows.
• Callback or signed webhook delivery.
• Import metadata and usage needed to operate the importer.

What your application manages

CSVJetty is not your database layer. Your application should authenticate the receiving request, validate imported records against current server-side rules, enforce permissions and uniqueness, and persist accepted records.

For callback delivery, that usually means sending the callback payload to an authenticated API route in your own application. For webhook delivery, CSVJetty sends the records directly to your HTTPS endpoint.

Where to go next