Upsert Flow
Create or update a Flow.
Flows can also be identified by the ID or their path.
You can provide version_name and version_description to identify and describe your versions.
Version names must be unique within a Flow - attempting to create a version with a name
that already exists will result in a 409 Conflict error.
Headers
Request
A key-value object identifying the Flow Version.
Path of the Flow, including the name. This locates the Flow in the Humanloop filesystem and is used as as a unique identifier. For example: folder/name or just name.
ID for an existing Flow.
Unique name for the Flow version. Version names must be unique for a given Flow.
Description of the version, e.g., the changes made in this version.
Response
Successful Response
Path of the Flow, including the name, which is used as a unique identifier.
Unique identifier for the Flow.
A key-value object identifying the Flow Version.
Name of the Flow.
Unique identifier for the specific Flow Version. If no query params provided, the default deployed Flow Version is returned.
The number of logs that have been generated for this Flow Version
ID of the directory that the file is in on Humanloop.
Unique name for the Flow version. Version names must be unique for a given Flow.
Description of the Version.
Description of the Flow.
Long description of the file.
The list of environments the Flow Version is deployed to.
The user who created the Flow.
Aggregation of Evaluator results for the Flow Version.
The list of Monitoring Evaluators associated with the Flow Version.