Argo Workflows WorkflowService API

The WorkflowService API from Argo Workflows — 15 operation(s) for workflowservice.

Operations 17

GET /api/v1/stream/events/{namespace} #
GET /api/v1/workflow-events/{namespace} #
GET /api/v1/workflows/{namespace} #
POST /api/v1/workflows/{namespace} #
POST /api/v1/workflows/{namespace}/lint #
POST /api/v1/workflows/{namespace}/submit #
GET /api/v1/workflows/{namespace}/{name} #
DELETE /api/v1/workflows/{namespace}/{name} #
GET /api/v1/workflows/{namespace}/{name}/log #
PUT /api/v1/workflows/{namespace}/{name}/resubmit #
PUT /api/v1/workflows/{namespace}/{name}/resume #
PUT /api/v1/workflows/{namespace}/{name}/retry #
PUT /api/v1/workflows/{namespace}/{name}/set #
PUT /api/v1/workflows/{namespace}/{name}/stop #
PUT /api/v1/workflows/{namespace}/{name}/suspend #
PUT /api/v1/workflows/{namespace}/{name}/terminate #
GET /api/v1/workflows/{namespace}/{name}/{podName}/log Argo Workflows DEPRECATED: Cannot Work via HTTP if PodName is an Empty String. Use WorkflowLogs. #

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/argo-workflows-workflowservice-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

argo-workflows-workflowservice-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  description: Argo Workflows is an open source container-native workflow engine for orchestrating parallel jobs on Kubernetes. For more information, please see https://argo-workflows.readthedocs.io/en/latest/
  title: Argo Workflows ArchivedWorkflowService Workflow Service API
  version: 3.6.0
servers:
- url: http://localhost:2746
- url: https://localhost:2746
security:
- BearerToken: []
tags:
- name: WorkflowService
paths:
  /api/v1/stream/events/{namespace}:
    get:
      tags:
      - WorkflowService
      operationId: WorkflowService_WatchEvents
      parameters:
      - name: namespace
        in: path
        required: true
        schema:
          type: string
      - description: 'A selector to restrict the list of returned objects by their labels.

          Defaults to everything.

          +optional.'
        name: listOptions.labelSelector
        in: query
        schema:
          type: string
      - description: 'A selector to restrict the list of returned objects by their fields.

          Defaults to everything.

          +optional.'
        name: listOptions.fieldSelector
        in: query
        schema:
          type: string
      - description: 'Watch for changes to the described resources and return them as a stream of

          add, update, and remove notifications. Specify resourceVersion.

          +optional.'
        name: listOptions.watch
        in: query
        schema:
          type: boolean
      - description: 'allowWatchBookmarks requests watch events with type "BOOKMARK".

          Servers that do not implement bookmarks may ignore this flag and

          bookmarks are sent at the server''s discretion. Clients should not

          assume bookmarks are returned at any specific interval, nor may they

          assume the server will send any BOOKMARK event during a session.

          If this is not a watch, this field is ignored.

          +optional.'
        name: listOptions.allowWatchBookmarks
        in: query
        schema:
          type: boolean
      - description: 'resourceVersion sets a constraint on what resource versions a request may be served from.

          See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for

          details.


          Defaults to unset

          +optional'
        name: listOptions.resourceVersion
        in: query
        schema:
          type: string
      - description: 'resourceVersionMatch determines how resourceVersion is applied to list calls.

          It is highly recommended that resourceVersionMatch be set for list calls where

          resourceVersion is set

          See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for

          details.


          Defaults to unset

          +optional'
        name: listOptions.resourceVersionMatch
        in: query
        schema:
          type: string
      - description: 'Timeout for the list/watch call.

          This limits the duration of the call, regardless of any activity or inactivity.

          +optional.'
        name: listOptions.timeoutSeconds
        in: query
        schema:
          type: string
          format: int64
      - description: 'limit is a maximum number of responses to return for a list call. If more items exist, the

          server will set the `continue` field on the list metadata to a value that can be used with the

          same initial query to retrieve the next set of results. Setting a limit may return fewer than

          the requested amount of items (up to zero items) in the event all requested objects are

          filtered out and clients should only use the presence of the continue field to determine whether

          more results are available. Servers may choose not to support the limit argument and will return

          all of the available results. If limit is specified and the continue field is empty, clients may

          assume that no more results are available. This field is not supported if watch is true.


          The server guarantees that the objects returned when using continue will be identical to issuing

          a single list call without a limit - that is, no objects created, modified, or deleted after the

          first request is issued will be included in any subsequent continued requests. This is sometimes

          referred to as a consistent snapshot, and ensures that a client that is using limit to receive

          smaller chunks of a very large result can ensure they see all possible objects. If objects are

          updated during a chunked list the version of the object that was present at the time the first list

          result was calculated is returned.'
        name: listOptions.limit
        in: query
        schema:
          type: string
          format: int64
      - description: 'The continue option should be set when retrieving more results from the server. Since this value is

          server defined, clients may only use the continue value from a previous query result with identical

          query parameters (except for the value of continue) and the server may reject a continue value it

          does not recognize. If the specified continue value is no longer valid whether due to expiration

          (generally five to fifteen minutes) or a configuration change on the server, the server will

          respond with a 410 ResourceExpired error together with a continue token. If the client needs a

          consistent list, it must restart their list without the continue field. Otherwise, the client may

          send another list request with the token received with the 410 error, the server will respond with

          a list starting from the next key, but from the latest snapshot, which is inconsistent from the

          previous list results - objects that are created, modified, or deleted after the first list request

          will be included in the response, as long as their keys are after the "next key".


          This field is not supported when watch is true. Clients may start a watch from the last

          resourceVersion value returned by the server and not miss any modifications.'
        name: listOptions.continue
        in: query
        schema:
          type: string
      - description: "`sendInitialEvents=true` may be set together with `watch=true`.\nIn that case, the watch stream will begin with synthetic events to\nproduce the current state of objects in the collection. Once all such\nevents have been sent, a synthetic \"Bookmark\" event  will be sent.\nThe bookmark will report the ResourceVersion (RV) corresponding to the\nset of objects, and be marked with `\"io.k8s.initial-events-end\": \"true\"` annotation.\nAfterwards, the watch stream will proceed as usual, sending watch events\ncorresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch`\noption to also be set. The semantic of the watch request is as following:\n- `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward\ncompatibility reasons) and to false otherwise.\n+optional"
        name: listOptions.sendInitialEvents
        in: query
        schema:
          type: boolean
      responses:
        '200':
          description: A successful response.(streaming responses)
          content:
            application/json:
              schema:
                type: object
                title: Stream result of io.k8s.api.core.v1.Event
                properties:
                  error:
                    $ref: '#/components/schemas/grpc.gateway.runtime.StreamError'
                  result:
                    $ref: '#/components/schemas/io.k8s.api.core.v1.Event'
        default:
          description: An unexpected error response.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/grpc.gateway.runtime.Error'
      x-microcks-operation:
        delay: 0
        dispatcher: FALLBACK
  /api/v1/workflow-events/{namespace}:
    get:
      tags:
      - WorkflowService
      operationId: WorkflowService_WatchWorkflows
      parameters:
      - name: namespace
        in: path
        required: true
        schema:
          type: string
      - description: 'A selector to restrict the list of returned objects by their labels.

          Defaults to everything.

          +optional.'
        name: listOptions.labelSelector
        in: query
        schema:
          type: string
      - description: 'A selector to restrict the list of returned objects by their fields.

          Defaults to everything.

          +optional.'
        name: listOptions.fieldSelector
        in: query
        schema:
          type: string
      - description: 'Watch for changes to the described resources and return them as a stream of

          add, update, and remove notifications. Specify resourceVersion.

          +optional.'
        name: listOptions.watch
        in: query
        schema:
          type: boolean
      - description: 'allowWatchBookmarks requests watch events with type "BOOKMARK".

          Servers that do not implement bookmarks may ignore this flag and

          bookmarks are sent at the server''s discretion. Clients should not

          assume bookmarks are returned at any specific interval, nor may they

          assume the server will send any BOOKMARK event during a session.

          If this is not a watch, this field is ignored.

          +optional.'
        name: listOptions.allowWatchBookmarks
        in: query
        schema:
          type: boolean
      - description: 'resourceVersion sets a constraint on what resource versions a request may be served from.

          See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for

          details.


          Defaults to unset

          +optional'
        name: listOptions.resourceVersion
        in: query
        schema:
          type: string
      - description: 'resourceVersionMatch determines how resourceVersion is applied to list calls.

          It is highly recommended that resourceVersionMatch be set for list calls where

          resourceVersion is set

          See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for

          details.


          Defaults to unset

          +optional'
        name: listOptions.resourceVersionMatch
        in: query
        schema:
          type: string
      - description: 'Timeout for the list/watch call.

          This limits the duration of the call, regardless of any activity or inactivity.

          +optional.'
        name: listOptions.timeoutSeconds
        in: query
        schema:
          type: string
          format: int64
      - description: 'limit is a maximum number of responses to return for a list call. If more items exist, the

          server will set the `continue` field on the list metadata to a value that can be used with the

          same initial query to retrieve the next set of results. Setting a limit may return fewer than

          the requested amount of items (up to zero items) in the event all requested objects are

          filtered out and clients should only use the presence of the continue field to determine whether

          more results are available. Servers may choose not to support the limit argument and will return

          all of the available results. If limit is specified and the continue field is empty, clients may

          assume that no more results are available. This field is not supported if watch is true.


          The server guarantees that the objects returned when using continue will be identical to issuing

          a single list call without a limit - that is, no objects created, modified, or deleted after the

          first request is issued will be included in any subsequent continued requests. This is sometimes

          referred to as a consistent snapshot, and ensures that a client that is using limit to receive

          smaller chunks of a very large result can ensure they see all possible objects. If objects are

          updated during a chunked list the version of the object that was present at the time the first list

          result was calculated is returned.'
        name: listOptions.limit
        in: query
        schema:
          type: string
          format: int64
      - description: 'The continue option should be set when retrieving more results from the server. Since this value is

          server defined, clients may only use the continue value from a previous query result with identical

          query parameters (except for the value of continue) and the server may reject a continue value it

          does not recognize. If the specified continue value is no longer valid whether due to expiration

          (generally five to fifteen minutes) or a configuration change on the server, the server will

          respond with a 410 ResourceExpired error together with a continue token. If the client needs a

          consistent list, it must restart their list without the continue field. Otherwise, the client may

          send another list request with the token received with the 410 error, the server will respond with

          a list starting from the next key, but from the latest snapshot, which is inconsistent from the

          previous list results - objects that are created, modified, or deleted after the first list request

          will be included in the response, as long as their keys are after the "next key".


          This field is not supported when watch is true. Clients may start a watch from the last

          resourceVersion value returned by the server and not miss any modifications.'
        name: listOptions.continue
        in: query
        schema:
          type: string
      - description: "`sendInitialEvents=true` may be set together with `watch=true`.\nIn that case, the watch stream will begin with synthetic events to\nproduce the current state of objects in the collection. Once all such\nevents have been sent, a synthetic \"Bookmark\" event  will be sent.\nThe bookmark will report the ResourceVersion (RV) corresponding to the\nset of objects, and be marked with `\"io.k8s.initial-events-end\": \"true\"` annotation.\nAfterwards, the watch stream will proceed as usual, sending watch events\ncorresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch`\noption to also be set. The semantic of the watch request is as following:\n- `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward\ncompatibility reasons) and to false otherwise.\n+optional"
        name: listOptions.sendInitialEvents
        in: query
        schema:
          type: boolean
      - name: fields
        in: query
        schema:
          type: string
      responses:
        '200':
          description: A successful response.(streaming responses)
          content:
            application/json:
              schema:
                type: object
                title: Stream result of io.argoproj.workflow.v1alpha1.WorkflowWatchEvent
                properties:
                  error:
                    $ref: '#/components/schemas/grpc.gateway.runtime.StreamError'
                  result:
                    $ref: '#/components/schemas/io.argoproj.workflow.v1alpha1.WorkflowWatchEvent'
        default:
          description: An unexpected error response.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/grpc.gateway.runtime.Error'
      x-microcks-operation:
        delay: 0
        dispatcher: FALLBACK
  /api/v1/workflows/{namespace}:
    get:
      tags:
      - WorkflowService
      operationId: WorkflowService_ListWorkflows
      parameters:
      - name: namespace
        in: path
        required: true
        schema:
          type: string
      - description: 'A selector to restrict the list of returned objects by their labels.

          Defaults to everything.

          +optional.'
        name: listOptions.labelSelector
        in: query
        schema:
          type: string
      - description: 'A selector to restrict the list of returned objects by their fields.

          Defaults to everything.

          +optional.'
        name: listOptions.fieldSelector
        in: query
        schema:
          type: string
      - description: 'Watch for changes to the described resources and return them as a stream of

          add, update, and remove notifications. Specify resourceVersion.

          +optional.'
        name: listOptions.watch
        in: query
        schema:
          type: boolean
      - description: 'allowWatchBookmarks requests watch events with type "BOOKMARK".

          Servers that do not implement bookmarks may ignore this flag and

          bookmarks are sent at the server''s discretion. Clients should not

          assume bookmarks are returned at any specific interval, nor may they

          assume the server will send any BOOKMARK event during a session.

          If this is not a watch, this field is ignored.

          +optional.'
        name: listOptions.allowWatchBookmarks
        in: query
        schema:
          type: boolean
      - description: 'resourceVersion sets a constraint on what resource versions a request may be served from.

          See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for

          details.


          Defaults to unset

          +optional'
        name: listOptions.resourceVersion
        in: query
        schema:
          type: string
      - description: 'resourceVersionMatch determines how resourceVersion is applied to list calls.

          It is highly recommended that resourceVersionMatch be set for list calls where

          resourceVersion is set

          See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for

          details.


          Defaults to unset

          +optional'
        name: listOptions.resourceVersionMatch
        in: query
        schema:
          type: string
      - description: 'Timeout for the list/watch call.

          This limits the duration of the call, regardless of any activity or inactivity.

          +optional.'
        name: listOptions.timeoutSeconds
        in: query
        schema:
          type: string
          format: int64
      - description: 'limit is a maximum number of responses to return for a list call. If more items exist, the

          server will set the `continue` field on the list metadata to a value that can be used with the

          same initial query to retrieve the next set of results. Setting a limit may return fewer than

          the requested amount of items (up to zero items) in the event all requested objects are

          filtered out and clients should only use the presence of the continue field to determine whether

          more results are available. Servers may choose not to support the limit argument and will return

          all of the available results. If limit is specified and the continue field is empty, clients may

          assume that no more results are available. This field is not supported if watch is true.


          The server guarantees that the objects returned when using continue will be identical to issuing

          a single list call without a limit - that is, no objects created, modified, or deleted after the

          first request is issued will be included in any subsequent continued requests. This is sometimes

          referred to as a consistent snapshot, and ensures that a client that is using limit to receive

          smaller chunks of a very large result can ensure they see all possible objects. If objects are

          updated during a chunked list the version of the object that was present at the time the first list

          result was calculated is returned.'
        name: listOptions.limit
        in: query
        schema:
          type: string
          format: int64
      - description: 'The continue option should be set when retrieving more results from the server. Since this value is

          server defined, clients may only use the continue value from a previous query result with identical

          query parameters (except for the value of continue) and the server may reject a continue value it

          does not recognize. If the specified continue value is no longer valid whether due to expiration

          (generally five to fifteen minutes) or a configuration change on the server, the server will

          respond with a 410 ResourceExpired error together with a continue token. If the client needs a

          consistent list, it must restart their list without the continue field. Otherwise, the client may

          send another list request with the token received with the 410 error, the server will respond with

          a list starting from the next key, but from the latest snapshot, which is inconsistent from the

          previous list results - objects that are created, modified, or deleted after the first list request

          will be included in the response, as long as their keys are after the "next key".


          This field is not supported when watch is true. Clients may start a watch from the last

          resourceVersion value returned by the server and not miss any modifications.'
        name: listOptions.continue
        in: query
        schema:
          type: string
      - description: "`sendInitialEvents=true` may be set together with `watch=true`.\nIn that case, the watch stream will begin with synthetic events to\nproduce the current state of objects in the collection. Once all such\nevents have been sent, a synthetic \"Bookmark\" event  will be sent.\nThe bookmark will report the ResourceVersion (RV) corresponding to the\nset of objects, and be marked with `\"io.k8s.initial-events-end\": \"true\"` annotation.\nAfterwards, the watch stream will proceed as usual, sending watch events\ncorresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch`\noption to also be set. The semantic of the watch request is as following:\n- `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward\ncompatibility reasons) and to false otherwise.\n+optional"
        name: listOptions.sendInitialEvents
        in: query
        schema:
          type: boolean
      - description: Fields to be included or excluded in the response. e.g. "items.spec,items.status.phase", "-items.status.nodes".
        name: fields
        in: query
        schema:
          type: string
      - description: Filter type used for name filtering. Exact | Contains | Prefix. Default to Exact.
        name: nameFilter
        in: query
        schema:
          type: string
      - name: createdAfter
        in: query
        schema:
          type: string
      - name: finishedBefore
        in: query
        schema:
          type: string
      responses:
        '200':
          description: A successful response.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/io.argoproj.workflow.v1alpha1.WorkflowList'
        default:
          description: An unexpected error response.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/grpc.gateway.runtime.Error'
      x-microcks-operation:
        delay: 0
        dispatcher: FALLBACK
    post:
      tags:
      - WorkflowService
      operationId: WorkflowService_CreateWorkflow
      parameters:
      - name: namespace
        in: path
        required: true
        schema:
          type: string
      responses:
        '200':
          description: A successful response.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/io.argoproj.workflow.v1alpha1.Workflow'
        default:
          description: An unexpected error response.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/grpc.gateway.runtime.Error'
      x-microcks-operation:
        delay: 0
        dispatcher: FALLBACK
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/io.argoproj.workflow.v1alpha1.WorkflowCreateRequest'
        required: true
  /api/v1/workflows/{namespace}/lint:
    post:
      tags:
      - WorkflowService
      operationId: WorkflowService_LintWorkflow
      parameters:
      - name: namespace
        in: path
        required: true
        schema:
          type: string
      responses:
        '200':
          description: A successful response.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/io.argoproj.workflow.v1alpha1.Workflow'
        default:
          description: An unexpected error response.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/grpc.gateway.runtime.Error'
      x-microcks-operation:
        delay: 0
        dispatcher: FALLBACK
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/io.argoproj.workflow.v1alpha1.WorkflowLintRequest'
        required: true
  /api/v1/workflows/{namespace}/submit:
    post:
      tags:
      - WorkflowService
      operationId: WorkflowService_SubmitWorkflow
      parameters:
      - name: namespace
        in: path
        required: true
        schema:
          type: string
      responses:
        '200':
          description: A successful response.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/io.argoproj.workflow.v1alpha1.Workflow'
        default:
          description: An unexpected error response.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/grpc.gateway.runtime.Error'
      x-microcks-operation:
        delay: 0
        dispatcher: FALLBACK
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/io.argoproj.workflow.v1alpha1.WorkflowSubmitRequest'
        required: true
  /api/v1/workflows/{namespace}/{name}:
    get:
      tags:
      - WorkflowService
      operationId: WorkflowService_GetWorkflow
      parameters:
      - name: namespace
        in: path
        required: true
        schema:
          type: string
      - name: name
        in: path
        required: true
        schema:
          type: string
      - description: 'resourceVersion sets a constraint on what resource versions a request may be served from.

          See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for

          details.


          Defaults to unset

          +optional'
        name: getOptions.resourceVersion
        in: query
        schema:
          type: string
      - description: Fields to be included or excluded in the response. e.g. "spec,status.phase", "-status.nodes".
        name: fields
        in: query
        schema:
          type: string
      - description: Optional UID to retrieve a specific workflow (useful for archived workflows with the same name).
        name: uid
        in: query
        schema:
          type: string
      responses:
        '200':
          description: A successful response.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/io.argoproj.workflow.v1alpha1.Workflow'
        default:
          description: An unexpected error response.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/grpc.gateway.runtime.Error'
      x-microcks-operation:
        delay: 0
        dispatcher: FALLBACK
    delete:
      tags:
      - WorkflowService
      operationId: WorkflowService_DeleteWorkflow
      parameters:
      - name: namespace
        in: path
        required: true
        schema:
          type: string
      - name: name
        in: path
        required: true
        schema:
          type: string
      - description: 'The duration in seconds before the object should be deleted. Value must be non-negative integer.

          The value zero indicates delete immediately. If this value is nil, the default grace period for the

          specified type will be used.

          Defaults to a per object value if not specified. zero means delete immediately.

          +optional.'
        name: deleteOptions.gracePeriodSeconds
        in: query
        schema:
          type: string
          format: int64
      - description: 'Specifies the target UID.

          +optional.'
        name: deleteOptions.preconditions.uid
        in: query
        schema:
          type: string
      - description: 'Specifies the target ResourceVersion

          +optional.'
        name: deleteOptions.preconditions.resourceVersion
        in: query
        schema:
          type: string
      - description: 'Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7.

          Should the dependent objects be orphaned. If true/false, the "orphan"

          finalizer will be added to/removed from the object''s finalizers list.

          Either this field or PropagationPolicy may be set, but not both.

          +optional.'
        name: deleteOptions.orphanDependents
        in: query
        schema:
          type: boolean
      - description: 'Whether and how garbage collection will be performed.

          Either this field or OrphanDependents may be set, but not both.

          The default policy is decided by the existing finalizer set in the

          metadata.finalizers and the resource-specific default policy.

          Acceptable values are: ''Orphan'' - orphan the dependents; ''Background'' -

          allow the garbage collector to delete the dependents in the background;

          ''Foreground'' - a cascading policy that deletes all dependents in the

          foreground.

          +optional.'
        name: deleteOptions.propagationPolicy
        in: query
        schema:
          type: string
      - description: 'When present, indicates that modifications should not be

          persisted. An invalid or unrecognized dryRun directive will

          result in an error response and no further processing of the

          request. Valid val

# --- truncated at 32 KB (396 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/argo-workflows/refs/heads/main/openapi/argo-workflows-workflowservice-api-openapi.yml