POST /api/database/tables/{table_id}/import/async/

Import data in the specified table if the authorized user has access to the related database's workspace. This endpoint is asynchronous and return the created job to track the progress of the task.

Servers

/

Path parameters

Name	Type	Required	Description
`table_id`	Integer	Yes	Import data into the table related to the provided value.

Request headers

Name	Type	Required	Description
`Content-Type`	String	Yes	The media type of the request body. Default value: "application/json"

Request body fields

Name	Type	Required	Description
`data[]`	Array	Yes	A list of rows you want to add to the specified table. Each row is a list of values, one for each writable field. The field values must be ordered according to the field order in the table, or according to `configuration.import_fields` when provided. All values must be compatible with the corresponding field type. Ex: `[ ["row1_field1_value", "row1_field2_value"], ["row2_field1_value", "row2_field2_value"], ]` for adding two rows to a table with two writable fields.
`importer_type`	String	No	The frontend importer identifier used to parse the file.
`configuration`	Object	No	Additional table import configuration.
`configuration.upsert_values[]`	Array	No	A list of values that are identifying rows in imported data. The number of rows in `upsert_values` should be equal to the number of rows in imported data. Each row in `upsert_values` should contain a list of values that match the number and field types of fields selected in `upsert_fields`. Based on `upsert_fields`, a similar upsert values will be calculated for each row in the table. There's no guarantee of uniqueness of row identification calculated from `upsert_values` nor from the table. Repeated upsert values are compared in order with matching values in the table. The imported data must be in the same order as the table rows for correct matching.
`configuration.skipped_fields[]`	Array	No	A list of field IDs that should not be overwritten during upsert operations.
`configuration.import_fields[]`	Array	No	The ordered field IDs corresponding to the values in each imported row. This snapshots the import schema so field reordering or permission changes cannot reinterpret positional values while the job is queued.
`configuration.upsert_fields[]`	Array	No	<function TableImportConfiguration. at 0x7fc4dcefa350>
`original_file_name`	String	No	The original name of the uploaded file.

How to start integrating

Add HTTP Task to your workflow definition.
Search for the API you want to integrate with and click on the name.
- This loads the API reference documentation and prepares the Http request settings.
Click Test request to test run your request to the API and see the API's response.