Create a data feed
Creates a data feed in the project with one transformation per event type.
Mangrove drafts a transformation script for each event type in the background (script_status is generating until then). The new feed has no schema and no sources, so not_ready_message is set until you define a schema with PATCH /projects/{project_id}/data_feeds/{data_feed_id}/update_schema. To upload files through this API, attach an endpoint source with POST /data_feeds/{data_feed_friendly_id}/sources. The header row is set with the schema, through headers_row_number on update_schema. Requires the read:project and write:data_feed token scopes.
Authorizations
Path Parameters
The project's friendly ID (e.g. prj_aBcD1234eFgH5678).
Body
Response
Data feed created
A data feed. List rows omit each transformation's script_content and each source's config; single-feed responses include them.
The data feed's friendly ID.
"datafd_aBcD1234eFgH5678"
"Daily Production Data"
"Imports daily production metrics"
Row number (1-based) containing column headers. Rows above are ignored during ingestion. 1 until a schema sets another value.
1
Why automatic setup could not build the schema (for example an unreadable sample file), or null.
Why the feed cannot accept data yet, or null when it is ready. A new feed reports "Transformation scripts are still being generated" until its scripts are drafted, and "Schema not defined" until a schema exists.
null
The columns of the current schema. Empty until a schema is defined.
The event types the feed's active transformations create.
Active (unarchived) transformations, one per event type.
Link to the data feed's page in the app.
"https://app.gomangrove.com/nexus/prj_aBcD1234eFgH5678/data-inputs/data-feeds/datafd_aBcD1234eFgH5678"