Skip to main content
Data is sent with POST /uploading/:upload_uuid/:entity_name. The body is JSON with two fields:
  • columns — column names (order matters)
  • data — array of rows; values in each row follow the same order as columns

​
Example

Success response:

​
Data requirements

  • All required columns must appear in columns — otherwise 422
  • Types are validated (string, number, date, bool) — otherwise 422
  • Multiple sequential requests per entity are allowed — data accumulates in the session
  • Upload is allowed only in UPLOADING state
  • Maximum package size — 32 MB

​
Date formats

Naive datetime (no timezone suffix).

​
Validation and preparation

Validation is synchronous within the request. After a successful response, the package is collected in the session and prepared in the background. Before start-upload, ensure upload_tasks_finished = true in GET /status.

​
Supported entities

The list of entities enabled for your client is configured by support. Full field definitions (required fields marked with a red *): Entity schema Unknown entity_name → 400 Unknown entity.

​
Entity dependencies

Some entities require their parent to be uploaded in the same session first (e.g. receipt before receiptitem). Receipts must be uploaded with line items. See Entity dependencies.

​
Data sources

Entities loaded via API do not run on scheduled loads. Coordinate with support which steps use API vs other sources. See Data sources.