All endpoints in estuary-rpc are described by a type that extends SimpleMeta, meaning at the very least that the method type and url must be defined for all of them

Hierarchy

Properties

authentication?: Authentication
description?: string

Detailed description text for the endpoint

example?: [reqBody: unknown, resBody: unknown]

Example (request) => response pair. estuary-rpc will use this both as the appropriate example fields within the OpenApi spec and will dynamically analyze the types to form a guess at what their description should be

method?: Method
reqSchema?: Schema

Schema definition for the Request object, overriding a guess formed in the example if provided. If the endpoint uses UrlFormTransport, this will be converted into the appropriate property list

resSchema?: Schema

Schema definition for the Request object, overriding a guess formed in the example if provided

summary?: string

Summary text for describing the endpoint

swagger?: Record<string, unknown>

Generic swagger JSON to extend the endpoint definition with, overriding everything else from this endpoint definition. Allowable fields defined here.

transport?: Transport<unknown, unknown>
url?: string

Generated using TypeDoc