Skip to content
qibdo qibdo
v1
API version
  • v1
Theme
Book a demo

Get Offered Schema Kinds

GET
/registry/v1/schemas
curl --request GET \
--url https://example.com/registry/v1/schemas

Returns the schema kinds this service offers. Each kind is served under /registry/v1/schemas/{kind}; a kind not listed answers NOT_FOUND.

OK

Media type application/json

RegistryOfferedSchemaKinds

The schema kinds the Registry schema service offers.

object
kinds

Kinds

Every kind this service serves.

Array<string>Output only
Allowed values: REGISTRY_SCHEMA_KIND_UNSPECIFIED REGISTRY_SCHEMA_KIND_FILTER
Example
{
"kinds": [
"REGISTRY_SCHEMA_KIND_UNSPECIFIED"
]
}

Default error response

Media type application/json

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
Example generated
{
"code": 1,
"message": "example",
"details": [
{
"@type": "example"
}
]
}