Skip to content
Kessel

KesselNotificationsIntegrationService_CreateNotificationsIntegration

POST
/api/inventory/v1beta1/resources/notifications-integrations

Request Body required

Section titled “Request Body required ”
object
integration

The NotificationsIntegration to create in Kessel Asset Inventory

object
metadata

Metadata about this resource

object
id

Kessel Asset Inventory generated identifier.

string
resource_type

The type of the Resource

string
created_at

Date and time when the inventory item was first reported.

string format: date-time
updated_at

Date and time when the inventory item was last updated.

string format: date-time
deleted_at

Date and time when the inventory item was deleted.

string format: date-time
org_id

The org id in which this resource is a member for access control. A resource can only be a member of one org.

string
workspace_id

The workspace id in which this resource is a member for access control. A resource can only be a member of one workspace.

string
labels
Array<object>
object
key
string
value
string
reporter_data

Write only reporter specific data

object
reporter_type
string format: enum
Allowed values: REPORTER_TYPE_UNSPECIFIED REPORTER_TYPE_OTHER ACM HBI OCM NOTIFICATIONS
reporter_instance_id

The ID of the instance of the reporter. This is derived from the authentication mechanism, i.e. authentication token.

string
console_href

The URL for this resource in the reporter’s management UI console. For example this would be the cluster URL in the HCC Console for an OCM reported cluster.

string
api_href

Reporter specific API link to the resource.

string
local_resource_id

The ID assigned to this resource by the reporter, for example OCM cluster ID, HBI’s host id, or ACM managed cluster name etc.

string
reporter_version

Version of the reporter

string

Responses

Section titled “ Responses ”

200

Section titled “200 ”

OK

object

default

Section titled “default ”

Default error response

The Status type defines a logical error model that is suitable for different programming environments, including REST APIs and RPC APIs. It is used by gRPC. Each Status message contains three pieces of data: error code, error message, and error details. You can find out more about this error model and how to work with it in the API Design Guide.

object
code

The status code, which should be an enum value of [google.rpc.Code][google.rpc.Code].

integer format: int32
message

A developer-facing error message, which should be in English. Any user-facing error message should be localized and sent in the [google.rpc.Status.details][google.rpc.Status.details] field, or localized by the client.

string
details

A list of messages that carry the error details. There is a common set of message types for APIs to use.

Array<object>

Contains an arbitrary serialized message along with a @type that describes the type of the serialized message.

object
@type

The type of the serialized message.

string
key
additional properties
any