Warning: This document is for an old version of Ververica Platform. The latest version is v2.1.

REST API & CI/CD

In this page we cover the general structure of the Deployment-related API resources. The API endpoints for these resources start with the /api prefix.

You can find more information on accessing Ververica Platform in the installation section.

Swagger

We ship a Swagger web client that covers all of the Ververica Platform APIs.

  • Swagger web client: /swagger

The API is split into two parts with separate OpenAPI specifications:

  • Ververica Platform: /swagger.json
  • Application Manager: /api/swagger.json

You can select which spec you want to operate against in the upper right corner of the Swagger web client.

Note

We only cover the Deployment-related APIs in this page. The APIs for administration have a different structure and are documented separately: Namespaces, API Tokens.

Resource Objects

All Deployment-related resource are scoped to a Namespace.

The following table shows which resources are available and how they are addressed.

Resource Name-Addressable
Deployment
DeploymentTarget
Event
Job
Savepoint
SecretValue

Each resource is identified by a unique ID. If a resource is not addressable by name, it has to be addressed by its ID.

Names

Resources that can be addressed by name require their names to be unique within a Namespace and immutable. A name is only allowed to include the following characters:

  • a-z, A-Z
  • 0-9
  • _, -

Examples:

  • resource-name-01
  • resource_name-02

Single Objects

Each managed resource object has the following structure:

kind: ResourceKind
apiVersion: v1
metadata:
  ...
spec:
  ...
status:
  ...

The metadata and spec parts of resources are managed by users whereas the status is fully managed by the system.

List Objects

List objects are returned via a List wrapper kind that holds objects in an items array, e.g. when listing Deployments you will receive a resource of kind DeploymentList with each Deployment being part of the items array.

kind: KindList
apiVersion: v1
items:
 - kind: Kind
   metadata:
    ...
   spec:
    ...

Content-Types

The API server expects requests to be made as JSON or YAML and responds as JSON or YAML, respectively. Please use the following media types for request content types (Content-Type header) and accepted responses (Accept header).

  • JSON: application/json
  • YAML: application/yaml

By default, the API will return JSON.

Resource Versions

The metadata.resourceVersion attribute of a Deployment resources specifies the current logical version of the resource. You can use this field to check whether a resource has been updated since your last request.

Note

Users must not make any assumptions about how resource versions are updated on resource modifications. If you specify a resource version on a modification, this is currently ignored by the API server. There is currently no way to use this field for concurrency control.

API Versioning

Each resource includes an apiVersion attribute that specifies the version of the object.

Any structural changes (such as renaming) to a resource require a major version upgrade. Therefore, you can assume that your API resources will not break as long as the version is not upgraded.

Minor changes to the API such as adding optional fields or deprecating fields may happen without a version upgrade. Such changes are treated as non-breaking by the API server and therefore do not require any intervention on your side.

Verbs

The Deployment-related APIs use traditional HTTP verbs for CRUD operations on resources. Currently, there is no support for PUT requests.

GET

List resources or request a single resource.

GET /api/v1/namespaces/<namespaceName>/<resourcePlural>

GET /api/v1/namespaces/<namespaceName>/<resourcePlural>/<resourceId>

GET /api/v1/namespaces/<namespaceName>/<resourcePlural>/<resourceName>

POST

Create a resource.

POST /api/v1/namespaces/<namespaceName>/<resourcePlural>

PATCH

Selectively modify an existing resource.

PATCH /api/v1/namespaces/<namespaceName>/<resourcePlural>/<resourceId>

PATCH /api/v1/namespaces/<namespaceName>/<resourcePlural>/<resourceName>

Patch requests follow RFC 7386 by default. Specified attributes in the patch request are merged with existing attributes. If you want to remove an attribute, set it to null.

Example: Remove entries from flinkConfiguration

spec:
  template:
    spec:
      flinkConfiguration:
        foo: null
        bar: baz

The above request will modify the flinkConfiguration of a Deployment resource as follows:

  • Remove entry with key foo.
  • Add entry bar: baz.

DELETE

Delete a resource.

DELETE /api/v1/namespaces/<namespaceName>/<resourcePlural>/<resourceId>

DELETE /api/v1/namespaces/<namespaceName>/<resourcePlural>/<resourceName>

Note that you can only delete resources that are managed by users.

Furthermore, certain resources will require the resource to be in a certain state before you can actually delete them (for instance a Deployment cannot be in state RUNNING when you try to delete it).

Responses

Validation Errors

Validation errors are wrapped in ApiValidationException resources.

kind: ApiValidationException
apiVersion: v1
message: <message>
statusCode: <statusCode>
errors:
  - attribute: <attribute>
    message: <message>

The errors array contains each validation error.

API Errors

Generic API errors such as a not found resource or a bad request are wrapped in ApiException resources.

kind: ApiException
apiVersion: v1
message: <message>
reason: <reason>
statusCode: <statusCode>
context:
  key1: value1

Reason is a short String describing the cause of the error. The context map provides optional context to the error.

Status Codes

  • 200: Successful GET request (get single resource or list).
  • 201: Successful POST request (resource created)
  • 400: Bad request (typically due to an ApiValidationException)
  • 401: Unauthorized (request needs authentication)
  • 403: Forbidden (request is not authorized)
  • 404: Resource not found (wrapped in ApiException)
  • 409: Conflict due to resource-specific constraints (wrapped in ApiException)
  • 500: Internal error (wrapped in ApiException)
  • 501: Not implemented due to configuration (wrapped in ApiException)