Flyte Executions API

Workflow execution creation, listing, retrieval, and termination.

Operations 7

POST /api/v1/executions Create a workflow execution #
POST /api/v1/executions/relaunch Relaunch a workflow execution #
POST /api/v1/executions/recover Recover a workflow execution #
GET /api/v1/executions/{id.project}/{id.domain} List workflow executions #
GET /api/v1/executions/{id.project}/{id.domain}/{id.name} Retrieve a workflow execution #
DELETE /api/v1/executions/{id.project}/{id.domain}/{id.name} Terminate a workflow execution #
GET /api/v1/metrics/executions/{id.project}/{id.domain}/{id.name} Retrieve execution metrics #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/flyte-executions-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

flyte-executions-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Flyte Admin DataProxy Executions API
  description: The Flyte Admin API is the control-plane REST API exposed by the flyteadmin service. It is generated from the flyteidl protocol buffer definitions via gRPC-Gateway and provides JSON over HTTP access to the same operations exposed via gRPC. The API is used to register and manage projects, tasks, workflows, and launch plans, to create and inspect workflow, node, and task executions, to receive lifecycle events, to proxy data to and from upstream object stores, and to read and write matchable attribute overrides at the project, domain, and workflow levels. The same REST API powers the Flyte Console UI and is the primary programmatic interface for operating a Flyte cluster.
  version: v1
  contact:
    name: Flyte
    url: https://flyte.org
  license:
    name: Apache 2.0
    url: https://www.apache.org/licenses/LICENSE-2.0
servers:
- url: http://localhost:30080
  description: Default flyteadmin endpoint in a local sandbox cluster
tags:
- name: Executions
  description: Workflow execution creation, listing, retrieval, and termination.
paths:
  /api/v1/executions:
    post:
      tags:
      - Executions
      summary: Create a workflow execution
      operationId: CreateExecution
      responses:
        '200':
          description: Workflow execution created.
  /api/v1/executions/relaunch:
    post:
      tags:
      - Executions
      summary: Relaunch a workflow execution
      operationId: RelaunchExecution
      responses:
        '200':
          description: Workflow execution relaunched.
  /api/v1/executions/recover:
    post:
      tags:
      - Executions
      summary: Recover a workflow execution
      operationId: RecoverExecution
      responses:
        '200':
          description: Workflow execution recovered.
  /api/v1/executions/{id.project}/{id.domain}:
    get:
      tags:
      - Executions
      summary: List workflow executions
      operationId: ListExecutions
      parameters:
      - name: id.project
        in: path
        required: true
        schema:
          type: string
      - name: id.domain
        in: path
        required: true
        schema:
          type: string
      responses:
        '200':
          description: A list of workflow executions.
  /api/v1/executions/{id.project}/{id.domain}/{id.name}:
    get:
      tags:
      - Executions
      summary: Retrieve a workflow execution
      operationId: GetExecution
      parameters:
      - name: id.project
        in: path
        required: true
        schema:
          type: string
      - name: id.domain
        in: path
        required: true
        schema:
          type: string
      - name: id.name
        in: path
        required: true
        schema:
          type: string
      responses:
        '200':
          description: A workflow execution.
    delete:
      tags:
      - Executions
      summary: Terminate a workflow execution
      operationId: TerminateExecution
      parameters:
      - name: id.project
        in: path
        required: true
        schema:
          type: string
      - name: id.domain
        in: path
        required: true
        schema:
          type: string
      - name: id.name
        in: path
        required: true
        schema:
          type: string
      responses:
        '200':
          description: Workflow execution terminated.
  /api/v1/metrics/executions/{id.project}/{id.domain}/{id.name}:
    get:
      tags:
      - Executions
      summary: Retrieve execution metrics
      operationId: GetExecutionMetrics
      parameters:
      - name: id.project
        in: path
        required: true
        schema:
          type: string
      - name: id.domain
        in: path
        required: true
        schema:
          type: string
      - name: id.name
        in: path
        required: true
        schema:
          type: string
      responses:
        '200':
          description: Execution metrics.