List Workflows
const url = 'https://example.com/api/workflows';const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url https://example.com/api/workflows \ --header 'Authorization: Bearer <token>'Every workflow an agent can request, without their params.
A list, and it stays a list — Studio’s own workflows sidebar reads this route, so
the shape it returns does not move. Each entry carries what choosing between
workflows needs: what it makes, what it needs to run, how long it took here, one
thing it produced, and a details link. Follow details for the workflow you
chose — that response has its params and every remaining call.
Pass ?view=full to get every workflow’s params in this response instead of
fetching them one at a time.
run_time holds measured run times per node from this install’s recent completed
jobs, or null if the workflow has never finished here. Times reflect the params
those jobs used; longer videos and bigger sizes take longer.
source is shipped for the workflows FlixML ships and documents, or local for
one the operator dropped into workflows/local/ on their own install. Nothing in
the docs or on flixml.com describes a local workflow: read its params rather
than assuming it behaves like the shipped one whose name it resembles.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Query Parameters
Section titled “Query Parameters”Responses
Section titled “Responses”Successful Response
object
Examplegenerated
[ {}]Validation Error
object
object
Examplegenerated
{ "detail": [ { "loc": [ "example" ], "msg": "example", "type": "example" } ]}