Update a data feed transformation
When script_content differs from the current script, creates a new transformation version; an identical script changes nothing. Also accepts PUT. Parameters are sent at the top level of the JSON body. Requires an API token associated with a user. Requires the read:project and write:project token scopes.
Authorizations
Path Parameters
The project's friendly ID (e.g. prj_aBcD1234eFgH5678).
The data feed's friendly ID (e.g. datafd_aBcD1234eFgH5678).
The transformation's friendly ID (e.g. tfn_aBcD1234eFgH5678), transformations[].id on the data feed.
"tfn_aBcD1234eFgH5678"
Body
Response
Success — returns the data feed, including its transformations
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"