import { ClientSDK, RequestOptions } from "../lib/sdks.js"; import * as components from "../models/components/index.js"; import * as operations from "../models/operations/index.js"; export declare class CatalogTypes extends ClientSDK { /** * ListTypes Catalog V2 * * @remarks * List all catalog types for an organisation, including those synced from external resources. */ list(options?: RequestOptions): Promise; /** * CreateType Catalog V2 * * @remarks * Create a catalog type. The schema must be updated using the UpdateTypeSchema endpoint. */ create(request: components.CreateTypeRequestBody, options?: RequestOptions): Promise; /** * DestroyType Catalog V2 * * @remarks * Archives a catalog type and associated entries. */ delete(request: operations.CatalogV2NumberDestroyTypeRequest, options?: RequestOptions): Promise; /** * ShowType Catalog V2 * * @remarks * Show a single catalog type. */ show(request: operations.CatalogV2NumberShowTypeRequest, options?: RequestOptions): Promise; /** * UpdateType Catalog V2 * * @remarks * Updates an existing catalog type. The schema must be updated using the UpdateTypeSchema endpoint. */ update(request: operations.CatalogV2NumberUpdateTypeRequest, options?: RequestOptions): Promise; /** * UpdateTypeSchema Catalog V2 * * @remarks * Update an existing catalog types schema, adding or removing attributes. * * Updating the schema is handled separately from creating and updating types, so that you don't * have to worry about dependencies between types. For example, if type A has an attribute that * relies on type B, you would have to create type B first. * * By allowing the creation of types without a schema, they can be created in any order, but it * means that you need to make a separate call to this endpoint to update the schema. */ updateSchema(request: operations.CatalogV2NumberUpdateTypeSchemaRequest, options?: RequestOptions): Promise; } //# sourceMappingURL=catalogtypes.d.ts.map