Apache Flink

Apache Flink JARs API

JAR upload, listing, run, and delete.

GitHub OpenAPI

Operations 5

GET /jars List uploaded JARs #
POST /jars/upload Upload a JAR #
DELETE /jars/{jarid} Delete a JAR #
GET /jars/{jarid}/plan Plan for a JAR #
POST /jars/{jarid}/run Run a job from a JAR #

Documentation

📖
Documentation
https://nightlies.apache.org/flink/flink-docs-stable/docs/ops/rest_api/

Specifications

⚙
OpenAPI
https://raw.githubusercontent.com/api-evangelist/flink/refs/heads/main/openapi/flink-jars-api-openapi.yml

SDKs

📦
GitHubRepository
https://github.com/apache/flink

Other Resources

🔗
Website
https://flink.apache.org/

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/flink-jars-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.

GitHub Google LinkedIn

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

OpenAPI Specification

flink-jars-api-openapi.yml Raw ↑ 
openapi: 3.2.0
info:
  title: Apache Flink REST Checkpoints JA Rs API
  description: The Flink REST API is exposed by the JobManager Dispatcher and provides monitoring and management capabilities for a Flink cluster. It covers cluster configuration, JobManager environment and metrics, job lifecycle (submit, list, cancel, stop), checkpoint and savepoint management, JAR upload and execution, dataset operations, and TaskManager inspection.
  version: v1
  contact:
    name: Apache Flink
    url: https://flink.apache.org/community/
  license:
    name: Apache 2.0
    url: https://www.apache.org/licenses/LICENSE-2.0
servers:
- url: http://localhost:8081
  description: Default JobManager Dispatcher endpoint
tags:
- name: JARs
  description: JAR upload, listing, run, and delete.
paths:
  /jars:
    get:
      tags:
      - JARs
      summary: List uploaded JARs
      operationId: listJars
      responses:
        '200':
          description: Uploaded JARs available for execution.
  /jars/upload:
    post:
      tags:
      - JARs
      summary: Upload a JAR
      operationId: uploadJar
      requestBody:
        required: true
        content:
          multipart/form-data:
            schema:
              type: object
              properties:
                jarfile:
                  type: string
                  format: binary
      responses:
        '200':
          description: JAR uploaded successfully.
  /jars/{jarid}:
    delete:
      tags:
      - JARs
      summary: Delete a JAR
      operationId: deleteJar
      parameters:
      - in: path
        name: jarid
        required: true
        schema:
          type: string
      responses:
        '200':
          description: JAR deleted.
  /jars/{jarid}/plan:
    get:
      tags:
      - JARs
      summary: Plan for a JAR
      operationId: getJarPlan
      parameters:
      - in: path
        name: jarid
        required: true
        schema:
          type: string
      responses:
        '200':
          description: Dataflow plan for the JAR.
  /jars/{jarid}/run:
    post:
      tags:
      - JARs
      summary: Run a job from a JAR
      operationId: runJar
      parameters:
      - in: path
        name: jarid
        required: true
        schema:
          type: string
      responses:
        '200':
          description: Job submitted from the JAR.