Given a pair of comma-separated ISO 8601 datetime strings,
filter results to only those runs which completed execution
within the specified range.
If one of the dates is omitted, it forms an open range.
For example, if the filter has a datetime followed by a comma (`"DT,"`),
all records with a date greater then or equal to `DT` will be returned.
Similarly, if the filter has a comma followed by a datetime (`",DT"`),
all records with dates less than `DT` will be returned.
If there is no comma, it is treated in the same way as `"DT,"`, above.
Results will contain runs which completed between the first datetime
onwards, up to (but not including) the second datetime.
Note that runs which are still executing will not have a completion time
and will be automatically excluded if this filter is applied.
Example
2021-03-09T21:52:14,2021-03-09T21:53
filter_start_time: string
Description
Given a pair of comma separated ISO 8601 date/time strings,
filter results to only those runs which started execution
within the specified range.
If one of the dates is omitted, it forms an open range.
For example, if the filter has a datetime followed by a comma (`"DT,"`),
all records with a date greater then or equal to `DT` will be returned.
Similarly, if the filter has a comma followed by a datetime (`",DT"`),
all records with dates less than `DT` will be returned.
If there is no comma, it is treated in the same way as `"DT,"`, above.
Results will contain runs which began between the first datetime
onwards, up to (but not including) the second datetime.
Example
2021-03-09T21:52:14,2021-03-09T21:53
flow_id: string
Description
The flow ID
list_flows_orderby: string[]
Description
Ordering criteria to apply to the list of flows.
This field is a comma-separated list of sort criteria,
and follows this syntax:
```
CRITERION1[,CRITERION2[,...]]
```
and each individual `CRITERION` follows this syntax:
```
FIELD ORDERING
```
The first value, `FIELD`, indicates the field to sort by;
the second value, `ORDERING`, indicates the sorting order.
When additional comma-separated criteria are added,
the first criterion will be used to sort the data;
subsequent criteria will be applied for ties.
Supported fields are:
- `id`
- `scope_string`
- `flow_owner`
- `flow_administrators`
- `title`
- `created_at`
- `updated_at`
Supported orderings are:
- `ASC`
- `DESC`
Example
[ "title ASC", "id DESC" ]
list_registered_apis_orderby: string[]
Description
Ordering criteria to apply to the list of Registered APIs.
This field is a comma-separated list of sort criteria,
and follows this syntax:
```
CRITERION1[,CRITERION2[,...]]
```
and each individual `CRITERION` follows this syntax:
```
FIELD ORDERING
```
The first value, `FIELD`, indicates the field to sort by;
the second value, `ORDERING`, indicates the sorting order.
When additional comma-separated criteria are added,
the first criterion will be used to sort the data;
subsequent criteria will be applied for ties.
Supported fields are:
- `id`
- `name`
- `created_timestamp`
- `updated_timestamp`
Supported orderings are:
- `ASC`
- `DESC`
Example
[ "name ASC", "id DESC" ]
list_runs_orderby: string[]
Description
Ordering criteria to apply to the list of runs.
This field is a comma-separated list of sort criteria,
and follows this syntax:
```
CRITERION1[,CRITERION2[,...]]
```
and each individual `CRITERION` follows this syntax:
```
FIELD ORDERING
```
The first value, `FIELD`, indicates the field to sort by;
the second value, `ORDERING`, indicates the sorting order.
When additional comma-separated criteria are added,
the first criterion will be used to sort the data;
subsequent criteria will be applied for ties.
Supported fields are:
- `id`
- `start_time`
- `completion_time`
- `status`
- `label`
Supported orderings are:
- `ASC`
- `DESC`
The operation may have been completed, or may be completed at a later time.
A follow-up API request may be needed to confirm the status of the operation.
If this parameter is used when updating a flow,
runs that are currently executing will continue to use the definition
that they were initially started with.
The flow definition. This is null for High Assurance flows when listing flows.
Optionaldescription?: string
Description
A detailed description of the Flow for end user display.
Optionalflow_administrators?: string[]
Description
The set of Principal URN values of users who may perform
administrative operations, including updating the
description itself. Only calling users with the
"administrator" role will be provided this
list. Otherwise, the value will always be an empty list.
Optionalflow_owner?: string
Optionalflow_starters?: string[]
Description
A set of Principal URN values, or the value
"all_authenticated_users" indicating the identity of users
who can initiate a run of the Flow. Only calling users
with the "administrator" role will be provided this
list. Otherwise, the value will always be an empty list.
The web-addressable location at which this Flow can be referenced
and run from.
Optionalflow_viewers?: string[]
Description
A set of Principal URN values, or the value "public"
indicating the identity of users who can view the Flow
definition. Only calling users with the "administrator"
role will be provided this list. Otherwise, the value
will always be an empty list.
A JSON Schema compliant definition of the format of the body field
when requesting a Flow be run. This is null for High Assurance flows when listing flows.
Optionalis_high_assurance?: boolean
Description
Indicates whether this flow is High Assurance. High Assurance flows have
sensitive fields (definition, input_schema) omitted from list responses
for security purposes.
Optionalkeywords?: string[]
Description
A set of terms used to categorize the Flow which may be used in
query and discovery operations.
Optionallog_supported?: boolean
Description
True if the Flow supports the /log operation providing detailed
information on the intermediate states of a Flow invocation.
Optionalprincipal_urn?: string
Optionalsubscription_id?: string
Format: uuid
Description
A subscription_id associated with this Flow. If no
subscription_id is present, the Flow may be
accepted, but may have limits on how long or how
much it can be used.
Optionalsubtitle?: string
Description
A concise summary of the Flow's purpose.
Optionalsynchronous?: boolean
Optionaltitle?: string
Description
A non-unique, human-friendly name used for displaying the Flow
to end users.
Optionaltypes?: ("Action"|"Event")[]
Optionalupdated_at?: string
Format: date-time
Description
A timezone-aware ISO8601 format string that represents the time at
which the Flow was last updated.
The definition of the Flow at the time the Run was started.
flow_id: string
Description
The Flow used to start the Run.
input_schema: Record<string,unknown>
Description
The input schema of the Flow at the time the Run was started.
InputBody: {[key:string]:unknown}
Input body
Description
The input body that will be passed into the flow when it starts.
If the flow defines an input schema, the input body will be validated against the input schema.
If there is no input schema, no validation will be performed.
A timezone-aware ISO8601 format string that represents the time at
which the Registered API was created.
description: string
Description
A detailed description of the Registered API.
id: string
Format: uuid
Description
The unique identifier for the Registered API.
name: string
Description
A non-unique, human-friendly name used for displaying the
Registered API to end users.
updated_timestamp: string
Format: date-time
Description
A timezone-aware ISO8601 format string that represents the time at
which the Registered API was last updated.
ResultPath: {ResultPath?:string}
RunManagers: string[]
Run managers
Description
A list of Globus Auth identity and group URNs that may manage runs of the flow.
"Managing" operations include updating, canceling, and deleting the run.
Only users with the "run_manager" role will be able to view this list.
Users with only the "run_monitor" role will see an empty list.
RunMonitors: string[]
Run monitors
Description
A list of Globus Auth identity and group URNs that may monitor runs of the flow.
"Monitoring" operations include checking the run status and its logs.
Only users with the "run_manager" role will be able to view this list.
Users with only the "run_monitor" role will see an empty list.
Tags are normalized by stripping leading and trailing whitespace,
and by replacing all whitespace with a single space.
When updating a run, existing tags will be overwritten.
This means that an empty array will delete all existing tags.
Description
Given a pair of comma-separated ISO 8601 datetime strings, filter results to only those runs which completed execution within the specified range.
Example