Import transactions (multipart)
API Reference
Import transactions (multipart)
Upload transaction files with optional saved mapping or native parser — via the gu1 batch import API for high-volume data loading, with examples for import.
POST
Import transactions (multipart)
Endpoint
Overview
Content-Type:multipart/form-data.
If mappingId and columnMapping are omitted, the server uses the native CSV/Excel/JSON parser. batchUploadEnabled must be true for the organization.
Query (alternate route only): validateGap=true on /transactions/batch/upload enables time-gap validation between multiple files.
See Create batch transactions for limits and templates.
Authentication
Form fields
| Field | Required | Description |
|---|---|---|
file | Yes | One or more files (repeat field name file) |
mappingId | No | Saved transaction mapping UUID |
columnMapping | No | JSON string of column mapping (CSV only; alternative to mappingId) |
executeRules | No | true / false |
skipDuplicates | No | true / false |
validateExistingEntity | No | true (default) / false |
batchErrorHandling | No | stop_keep_success or continue_collect_errors |
Limits
| Value | |
|---|---|
| Files per request | Up to 5 (repeat form field file) |
| Max transactions per file | By plan — see Create batch transactions — Limits by plan (Freemium 4,000 → Enterprise 100,000); hard parser cap 100,000 rows/file |
| Formats | CSV, Excel (.xlsx, .xls), JSON |
| Feature flag | batchUploadEnabled must be true for the organization |
POST /transactions/batch/upload (alias behavior).
See also: Bulk imports overview.