@omnibase/core-js 0.9.12 → 0.9.14

package/dist/esm/apis/V1AuthApi.d.ts

@@ -2,7 +2,7 @@
  * Omnibase REST API
  * Self-hostable Backend-as-a-Service providing database management, authentication, payments, storage, and email services.  ## Features - **Database**: PostgreSQL with RLS and migrations - **Authentication**: Ory Kratos integration with session management - **Payments**: Stripe integration with version-controlled billing configs - **Storage**: S3-compatible object storage with RLS - **Email**: Transactional email service - **Permissions**: Fine-grained access control via Ory Keto  ## Authentication Most endpoints require authentication via session cookies or JWT tokens. Use the appropriate security scheme based on the endpoint requirements.
  *
- * The version of the OpenAPI document: 0.9.12
+ * The version of the OpenAPI document: 0.9.14
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/esm/apis/V1AuthApi.js

@@ -4,7 +4,7 @@
  * Omnibase REST API
  * Self-hostable Backend-as-a-Service providing database management, authentication, payments, storage, and email services.  ## Features - **Database**: PostgreSQL with RLS and migrations - **Authentication**: Ory Kratos integration with session management - **Payments**: Stripe integration with version-controlled billing configs - **Storage**: S3-compatible object storage with RLS - **Email**: Transactional email service - **Permissions**: Fine-grained access control via Ory Keto  ## Authentication Most endpoints require authentication via session cookies or JWT tokens. Use the appropriate security scheme based on the endpoint requirements.
  *
- * The version of the OpenAPI document: 0.9.12
+ * The version of the OpenAPI document: 0.9.14
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/esm/apis/V1ConfigurationApi.d.ts

@@ -0,0 +1,167 @@
+/**
+ * Omnibase REST API
+ * Self-hostable Backend-as-a-Service providing database management, authentication, payments, storage, and email services.  ## Features - **Database**: PostgreSQL with RLS and migrations - **Authentication**: Ory Kratos integration with session management - **Payments**: Stripe integration with version-controlled billing configs - **Storage**: S3-compatible object storage with RLS - **Email**: Transactional email service - **Permissions**: Fine-grained access control via Ory Keto  ## Authentication Most endpoints require authentication via session cookies or JWT tokens. Use the appropriate security scheme based on the endpoint requirements.
+ *
+ * The version of the OpenAPI document: 0.9.14
+ * Contact: support@omnibase.dev
+ *
+ * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
+ * https://openapi-generator.tech
+ * Do not edit the class manually.
+ */
+import * as runtime from '../runtime';
+import type { ArchiveAllStripeConfig200Response, CreateOrUpdateEmailTemplate200Response, DeleteEmailTemplate200Response, DeployPermissionNamespaces200Response, GetEmailTemplateByType200Response, GetEmailTemplates200Response, GetStripeConfigHistory200Response, HandlersSuccessResponse, PullStripeConfig200Response, V1CreateEmailTemplateRequest, V1MigrationSuccessResponse } from '../models/index';
+export interface CreateOrUpdateEmailTemplateRequest {
+    body: V1CreateEmailTemplateRequest;
+}
+export interface DeleteEmailTemplateRequest {
+    type: string;
+}
+export interface DeployPermissionNamespacesRequest {
+    namespaces: Blob;
+}
+export interface GetEmailTemplateByTypeRequest {
+    type: string;
+}
+export interface GetStripeConfigHistoryRequest {
+    limit?: number;
+    offset?: number;
+}
+export interface UpdateStripeConfigRequest {
+    config: {
+        [key: string]: any;
+    };
+}
+export interface UploadDatabaseMigrationsRequest {
+    migrations: Blob;
+}
+export interface ValidateStripeConfigRequest {
+    config: {
+        [key: string]: any;
+    };
+}
+/**
+ *
+ */
+export declare class V1ConfigurationApi extends runtime.BaseAPI {
+    /**
+     * Archives all active products, prices, and meters in Stripe and clears the local configuration.  ## Authentication Requires admin JWT token.  ## Warning This is a destructive operation that will archive ALL active Stripe resources.  ## Use Cases - Clean slate for new configuration - Remove all test data - Reset Stripe account
+     * Archive all Stripe config
+     */
+    archiveAllStripeConfigRaw(initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<ArchiveAllStripeConfig200Response>>;
+    /**
+     * Archives all active products, prices, and meters in Stripe and clears the local configuration.  ## Authentication Requires admin JWT token.  ## Warning This is a destructive operation that will archive ALL active Stripe resources.  ## Use Cases - Clean slate for new configuration - Remove all test data - Reset Stripe account
+     * Archive all Stripe config
+     */
+    archiveAllStripeConfig(initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<ArchiveAllStripeConfig200Response>;
+    /**
+     * Creates a new email template or updates an existing one based on template type.  ## Template Management - If template type exists: updates subject and HTML body - If template type is new: creates new template entry  ## Template Types Template types are user-defined identifiers (e.g., \"welcome\", \"password-reset\", \"invoice\").  ## Use Cases - Store custom email templates for transactional emails - Update email content without code deployments - Maintain versioned email templates
+     * Create or update email template
+     */
+    createOrUpdateEmailTemplateRaw(requestParameters: CreateOrUpdateEmailTemplateRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<CreateOrUpdateEmailTemplate200Response>>;
+    /**
+     * Creates a new email template or updates an existing one based on template type.  ## Template Management - If template type exists: updates subject and HTML body - If template type is new: creates new template entry  ## Template Types Template types are user-defined identifiers (e.g., \"welcome\", \"password-reset\", \"invoice\").  ## Use Cases - Store custom email templates for transactional emails - Update email content without code deployments - Maintain versioned email templates
+     * Create or update email template
+     */
+    createOrUpdateEmailTemplate(requestParameters: CreateOrUpdateEmailTemplateRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<CreateOrUpdateEmailTemplate200Response>;
+    /**
+     * Deletes an email template by its type identifier.  ## Deletion Process - Searches for template by type - Removes template from database if found - Returns 404 if template doesn\'t exist  ## Use Cases - Remove deprecated email templates - Clean up test templates - Template lifecycle management
+     * Delete email template
+     */
+    deleteEmailTemplateRaw(requestParameters: DeleteEmailTemplateRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<DeleteEmailTemplate200Response>>;
+    /**
+     * Deletes an email template by its type identifier.  ## Deletion Process - Searches for template by type - Removes template from database if found - Returns 404 if template doesn\'t exist  ## Use Cases - Remove deprecated email templates - Clean up test templates - Template lifecycle management
+     * Delete email template
+     */
+    deleteEmailTemplate(requestParameters: DeleteEmailTemplateRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<DeleteEmailTemplate200Response>;
+    /**
+     * Uploads and deploys permission namespace configurations as a zip file.  ## Authentication Requires JWT token with appropriate permissions.  ## File Format Upload a zip file containing namespace definition files and optionally a roles.config.json file. The namespace files are stored in S3 and parsed to extract permission definitions.  ## Managed Mode If managed hosting is enabled, this endpoint will also trigger a restart of the Keto service.  ## Use Cases - CLI namespace deployment via `omnibase permissions push` - CI/CD pipeline integrations - Programmatic permission management
+     * Deploy Keto namespace configurations
+     */
+    deployPermissionNamespacesRaw(requestParameters: DeployPermissionNamespacesRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<DeployPermissionNamespaces200Response>>;
+    /**
+     * Uploads and deploys permission namespace configurations as a zip file.  ## Authentication Requires JWT token with appropriate permissions.  ## File Format Upload a zip file containing namespace definition files and optionally a roles.config.json file. The namespace files are stored in S3 and parsed to extract permission definitions.  ## Managed Mode If managed hosting is enabled, this endpoint will also trigger a restart of the Keto service.  ## Use Cases - CLI namespace deployment via `omnibase permissions push` - CI/CD pipeline integrations - Programmatic permission management
+     * Deploy Keto namespace configurations
+     */
+    deployPermissionNamespaces(requestParameters: DeployPermissionNamespacesRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<DeployPermissionNamespaces200Response>;
+    /**
+     * Retrieves a specific email template by its type identifier.  ## Template Lookup Searches for template matching the provided type parameter.  ## Use Cases - Fetch template for editing - Preview specific email template - Retrieve template before sending email
+     * Get email template by type
+     */
+    getEmailTemplateByTypeRaw(requestParameters: GetEmailTemplateByTypeRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<GetEmailTemplateByType200Response>>;
+    /**
+     * Retrieves a specific email template by its type identifier.  ## Template Lookup Searches for template matching the provided type parameter.  ## Use Cases - Fetch template for editing - Preview specific email template - Retrieve template before sending email
+     * Get email template by type
+     */
+    getEmailTemplateByType(requestParameters: GetEmailTemplateByTypeRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<GetEmailTemplateByType200Response>;
+    /**
+     * Retrieves all email templates stored in the database.  ## Response Returns array of all templates with their type, subject, and HTML body.  ## Use Cases - List available email templates - Display template management interface - Audit email template inventory
+     * Get all email templates
+     */
+    getEmailTemplatesRaw(initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<GetEmailTemplates200Response>>;
+    /**
+     * Retrieves all email templates stored in the database.  ## Response Returns array of all templates with their type, subject, and HTML body.  ## Use Cases - List available email templates - Display template management interface - Audit email template inventory
+     * Get all email templates
+     */
+    getEmailTemplates(initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<GetEmailTemplates200Response>;
+    /**
+     * Returns paginated history of all Stripe configurations.  ## Authentication Requires admin JWT token.  ## Query Parameters - limit: Items per page (default: 10, max: 100) - offset: Number of items to skip (default: 0)
+     * Get config history
+     */
+    getStripeConfigHistoryRaw(requestParameters: GetStripeConfigHistoryRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<GetStripeConfigHistory200Response>>;
+    /**
+     * Returns paginated history of all Stripe configurations.  ## Authentication Requires admin JWT token.  ## Query Parameters - limit: Items per page (default: 10, max: 100) - offset: Number of items to skip (default: 0)
+     * Get config history
+     */
+    getStripeConfigHistory(requestParameters?: GetStripeConfigHistoryRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<GetStripeConfigHistory200Response>;
+    /**
+     * Returns the JSON schema definition for validating Stripe configuration files.  ## Use Cases - Validate configuration before upload - IDE autocomplete support - Generate configuration templates
+     * Get Stripe config schema
+     */
+    getStripeConfigSchemaRaw(initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<object>>;
+    /**
+     * Returns the JSON schema definition for validating Stripe configuration files.  ## Use Cases - Validate configuration before upload - IDE autocomplete support - Generate configuration templates
+     * Get Stripe config schema
+     */
+    getStripeConfigSchema(initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<object>;
+    /**
+     * Fetches all active products, prices, and meters from Stripe API and converts them to the local configuration format.  ## Authentication Requires admin JWT token.  ## Use Cases - Sync remote Stripe config to local - Import existing Stripe setup - Configuration backup
+     * Pull config from Stripe
+     */
+    pullStripeConfigRaw(initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<PullStripeConfig200Response>>;
+    /**
+     * Fetches all active products, prices, and meters from Stripe API and converts them to the local configuration format.  ## Authentication Requires admin JWT token.  ## Use Cases - Sync remote Stripe config to local - Import existing Stripe setup - Configuration backup
+     * Pull config from Stripe
+     */
+    pullStripeConfig(initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<PullStripeConfig200Response>;
+    /**
+     * Updates the Stripe configuration and syncs with Stripe API to create/update products, prices, and meters.  ## Authentication Requires admin JWT token.  ## Use Cases - Deploy new pricing - Update product definitions - Modify metered billing settings
+     * Update Stripe config
+     */
+    updateStripeConfigRaw(requestParameters: UpdateStripeConfigRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<HandlersSuccessResponse>>;
+    /**
+     * Updates the Stripe configuration and syncs with Stripe API to create/update products, prices, and meters.  ## Authentication Requires admin JWT token.  ## Use Cases - Deploy new pricing - Update product definitions - Modify metered billing settings
+     * Update Stripe config
+     */
+    updateStripeConfig(requestParameters: UpdateStripeConfigRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<HandlersSuccessResponse>;
+    /**
+     * Uploads SQL migration files and applies them to the user\'s PostgreSQL database.  ## Authentication Requires JWT token (typically used by CLI tools, not browser sessions).  ## Migration Format Upload a zip file containing SQL files named like: `001-seed.sql`, `002-rls.sql`, etc. Files are automatically renamed to golang-migrate format: `001_seed.up.sql`, `002_rls.up.sql`.  ## Use Cases - CLI migration uploads via `omnibase db migration push` - CI/CD pipeline integrations - Programmatic schema management
+     * Upload database migrations
+     */
+    uploadDatabaseMigrationsRaw(requestParameters: UploadDatabaseMigrationsRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<V1MigrationSuccessResponse>>;
+    /**
+     * Uploads SQL migration files and applies them to the user\'s PostgreSQL database.  ## Authentication Requires JWT token (typically used by CLI tools, not browser sessions).  ## Migration Format Upload a zip file containing SQL files named like: `001-seed.sql`, `002-rls.sql`, etc. Files are automatically renamed to golang-migrate format: `001_seed.up.sql`, `002_rls.up.sql`.  ## Use Cases - CLI migration uploads via `omnibase db migration push` - CI/CD pipeline integrations - Programmatic schema management
+     * Upload database migrations
+     */
+    uploadDatabaseMigrations(requestParameters: UploadDatabaseMigrationsRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<V1MigrationSuccessResponse>;
+    /**
+     * Validates a Stripe configuration against the schema without saving or deploying it.  ## Authentication Requires admin JWT token.  ## Use Cases - Pre-deployment validation - Configuration testing - Schema compliance checking
+     * Validate Stripe config
+     */
+    validateStripeConfigRaw(requestParameters: ValidateStripeConfigRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<HandlersSuccessResponse>>;
+    /**
+     * Validates a Stripe configuration against the schema without saving or deploying it.  ## Authentication Requires admin JWT token.  ## Use Cases - Pre-deployment validation - Configuration testing - Schema compliance checking
+     * Validate Stripe config
+     */
+    validateStripeConfig(requestParameters: ValidateStripeConfigRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<HandlersSuccessResponse>;
+}