API Spec Type
stringThe type of specification being stored. This allows us to render the specification correctly.
Allowed values:oas2oas3asyncapi
RawApiSpecProvider
objectAllowed values:raw
UrlApiSpecProvider
objectAllowed values:url
Show Child Parameters
IntegrationApiSpecProviderPayload
objectAPI spec provider registered by a catalog integration.
Integrations can function as API spec providers where they register a globally unique
type and config schema which defines the shape of config.
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.
>= 1 characters<= 120 characters
Example:swaggerhub_api_version
JSON object containing values as defined by integration provider’s config schema.
Example:{"owner":"petco","api":"pet_store","version":"v3"}
The integration instance id or name
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