K2K Apps
The bearer token can be obtained by creating a ServiceAccount.
Includes metrics in the response, if available.
Happy response.
Defines a K2KApp (Kafka-to-Kafka application).
Error object.
The bearer token can be obtained by creating a ServiceAccount.
Contains common fields shared by HQ manifests.
Happy response.
Contains common fields shared by HQ manifests.
Error object.
The bearer token can be obtained by creating a ServiceAccount.
Deletes the K2KApp instantly and skips waiting for deletion of any corresponding K8s resources.
Happy response.
Contains common fields shared by HQ manifests.
Error object.
The bearer token can be obtained by creating a ServiceAccount.
Contains common fields shared by HQ manifests.
Happy response.
Contains common fields shared by HQ manifests.
Error object.
The bearer token can be obtained by creating a ServiceAccount.
Includes metrics summaries in the response, if available.
Happy response.
Contains K2KApps (Kafka-to-Kafka applications).
Error object.
The bearer token can be obtained by creating a ServiceAccount.
Contains common fields shared by HQ manifests.
Happy response.
Contains common fields shared by HQ manifests.
Error object.
The bearer token can be obtained by creating a ServiceAccount.
The unique name for the K2K application.
my-app-prodDefines the request body for updating K2K offsets, containing an array of topic-partition-offset tuples.
Offsets successfully updated.
my-app-prodError object.
The bearer token can be obtained by creating a ServiceAccount.
The unique name for the K2K application.
my-app-prodDefines the request body for updating K2K offsets based on a timestamp for multiple topics.
RFC3339 timestamp to seek offsets to.
2025-01-14T10:03:00ZList of Kafka topic names to update offsets for.
["user-login-events","orders","payments"]Offsets successfully updated.
my-app-prodError object.
The bearer token can be obtained by creating a ServiceAccount.
Error object.
Implements the RFC7807 "Problem Details", see https://www.rfc-editor.org/rfc/rfc7807.
Enumerates possible error types.
Describes the problem in a human readable fashion.
Is a copy of the http status code.
Contains in case of an "unauthorised" type of error, the url of the SSO provider, if any.
Is set to the id of this request. Can be used to correlate backend logs.
Error object.
Last updated
Was this helpful?

