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
X-API-KEY
Request
This endpoint expects an object.
attributes
A key-value object identifying the Flow Version.
path
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
ID for an existing Flow.
version_name
Unique name for the Flow version. Version names must be unique for a given Flow.
version_description
Description of the version, e.g., the changes made in this version.
Response
Successful Response
path
Path of the Flow, including the name, which is used as a unique identifier.
id
Unique identifier for the Flow.
attributes
A key-value object identifying the Flow Version.
name
Name of the Flow.
version_id
Unique identifier for the specific Flow Version. If no query params provided, the default deployed Flow Version is returned.
created_at
updated_at
last_used_at
version_logs_count
The number of logs that have been generated for this Flow Version
directory_id
ID of the directory that the file is in on Humanloop.
version_name
Unique name for the Flow version. Version names must be unique for a given Flow.
version_description
Description of the Version.
description
Description of the Flow.
schema
The JSON schema for the File.
readme
Long description of the file.
type
environments
The list of environments the Flow Version is deployed to.
created_by
The user who created the Flow.
evaluator_aggregates
Aggregation of Evaluator results for the Flow Version.
evaluators
The list of Monitoring Evaluators associated with the Flow Version.