Purpose and position in a flow
“API input data” starts a branch by supplying the table from an accepted HTTP request. Add it from “API: receive and publish data” or the connections tab. Select a REST API connection with direction “Receive data in Data Bridge”. Within a flow, use one such block per inbound endpoint.
The block needs no input table. Connect its result to cleaning, validation, transformations and destinations. An accepted delivery executes Production, not the open draft. If the flow uses several sources, combine them using the relevant keys after obtaining their tables.
Data or files
In “Receive data”, choose automatic detection from Content-Type or JSON, JSON Lines, CSV/TSV or XML. For JSON, set a record path such as data.items when needed. For CSV, define delimiter and headers; for XML, the record path and ancestor attributes. Nested values become fields such as customer.id.
In “Receive files”, select accepted XLSX/XLSM, CSV, TXT, JSON and XML formats, file count and reading settings. For Excel, specify a sheet and explicit range such as A1:Z10000; for a JSON file, use a JSON Pointer such as /data/rows. Rows from all files in one request are combined. Optionally add a filename column whose name does not duplicate a data field.
Fields and error policy
Enter a mock, choose its own format and refresh fields. Check each field's format: text, integer, number, date, date/time or boolean; mark required fields. Validation does not convert values: normalize them in downstream blocks. Add up to 20 unique keys containing one or several fields; these check duplicates only within one request.
A missing declared field can cause rejection or an empty value. For invalid values, choose whole-request rejection with details, valid-row acceptance only, or whole-request rejection with a concise summary. Partial acceptance requires subsequent reconciliation of rejected rows; when no valid rows remain, the request is rejected.
Simulation and production execution
Mock data is used in preview, validation, simulation and reference examples. Its format is independent of the request format. Production never substitutes the mock. For a run without an API delivery, choose an empty table with declared fields or a stop; this prevents accidental use of test values.
Test a valid row, a missing required value and a duplicate key. After publication, submit a control delivery and reconcile the destination table. “Technical documentation” opens the endpoint contract; “API requests” in the context menu opens its journal. See API intake configuration for the complete connection, signing and tracking procedure.