ResourceBoundIntegrationApiSpecProviderPayload
objectAPI spec provider registered by a catalog integration.
These providers differ from IntegrationApiSpecProvider in that they
denote a binding relationship between a resource type and the API spec.
This means that the API Spec will automatically be created/deleted for/from a service
as resources of the given type are mapped/unmapped.
Consult integration documentation to learn more about available API spec providers.
The globally unique API spec provider type that is registered by a given catalog integration.
Resource-bound providers create a 1-to-1 mapping between a resource type and the API Spec.
>= 1 characters<= 120 characters
Show Child Parameters
CreatedAt
stringAn ISO-8601 timestamp representation of entity creation date.
UpdatedAt
stringAn ISO-8601 timestamp representation of entity update date.
Labels
objectLabels store metadata of an entity that can be used for filtering an entity list or for searching across entity types.
Keys must be of length 1-63 characters, and cannot start with “kong”, “konnect”, “mesh”, “kic”, or “_”.
Error
objectstandard error
The HTTP status code of the error. Useful when passing the response
body to child properties in a frontend UI. Must be returned as an integer.
A short, human-readable summary of the problem. It should not
change between occurences of a problem, except for localization.
Should be provided as “Sentence case” for direct use in the UI.
The error type.
Used to return the correlation ID back to the user, in the format
kong:trace:<correlation_id>. This helps us find the relevant logs
when a customer reports an issue.
A human readable explanation specific to this occurence of the problem.
This field may contain request/entity data to help the user understand
what went wrong. Enclose variable values in square brackets. Should be
provided as “Sentence case” for direct use in the UI.