Loading page…
Loading page…
Turn file selection into a guided path to the data your product expects. Users map fields, review errors and correct rejected records. Your application receives the accepted batches.
React integration · CSV, TSV, JSON, NDJSON, XML and XLSX
Match incoming fields to the records your product expects.
The record your application receives
{
"email": "ada@example.com",
"fullName": "Ada",
"age": 36
}A clear path through onboarding
Select a file and preview its contents before importing.
Map columns to the fields, types and rules your product expects.
Review invalid records and correct what needs attention.
Accepted batches reach your application. Unresolved records remain visible.
Delivery that follows your application
Understand the data flow
File → browser → your handler
Mapping and validation run on-device. Your application chooses whether to send the accepted records onward.
File → browser → relay → your endpoint
Accepted batches transit the Cloud relay. It stores configuration and operational metadata, rather than imported row payloads.
Before you integrate
The importer demo and browser use cases run locally with the bundled preview runtime. Public installation availability is shown in each integration guide.
SDK use in personal and commercial applications has no per-user or per-record license fee. Optional hosted operations have separate terms; hosted pricing and activation are still being prepared.
The importer accepts CSV, TSV, JSON, NDJSON, XML and XLSX. Supported structure and limits depend on the processing path. The streaming SDK has its own format matrix.
Records that fail your configured rules are reported separately. Users can review and correct retained rejections. Earlier accepted batches may already have been delivered.
Your receiver controls persistence. It must acknowledge at the appropriate point and handle repeated batch identifiers safely.
Try the workflow from file selection to accepted records, then see how it fits your application.