@omnibase/core-js 0.9.18 → 0.10.1

package/src/apis/V1WebhooksApi.ts

@@ -0,0 +1,132 @@
+/* tslint:disable */
+/* eslint-disable */
+/**
+ * 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  ## 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.10.1
+ * 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 {
+  BadRequest,
+  ConfigureWebhooks200Response,
+  GetWebhookSecret200Response,
+  InternalServerError,
+  NotFound,
+  Unauthorized,
+  WebhooksConfigRequest,
+} from '../models/index';
+import {
+    BadRequestFromJSON,
+    BadRequestToJSON,
+    ConfigureWebhooks200ResponseFromJSON,
+    ConfigureWebhooks200ResponseToJSON,
+    GetWebhookSecret200ResponseFromJSON,
+    GetWebhookSecret200ResponseToJSON,
+    InternalServerErrorFromJSON,
+    InternalServerErrorToJSON,
+    NotFoundFromJSON,
+    NotFoundToJSON,
+    UnauthorizedFromJSON,
+    UnauthorizedToJSON,
+    WebhooksConfigRequestFromJSON,
+    WebhooksConfigRequestToJSON,
+} from '../models/index';
+
+export interface ConfigureWebhooksRequest {
+    webhooksConfigRequest: WebhooksConfigRequest;
+}
+
+/**
+ * 
+ */
+export class V1WebhooksApi extends runtime.BaseAPI {
+
+    /**
+     * Creates, updates, or removes multiple webhook endpoints to match the desired configuration. Webhooks not in the request will be deleted.  ## Authentication Requires service key authentication.  ## Connect Webhooks Each webhook can have `connect: true` to listen to events from connected accounts.  ## URL Interpolation URLs support `${VAR}` environment variable interpolation when using the CLI. The CLI resolves these before sending to the API.  ## Use Cases - Configure multiple webhooks for different environments - Set up both account and Connect webhooks - Declarative webhook configuration management 
+     * Configure multiple webhook endpoints
+     */
+    async configureWebhooksRaw(requestParameters: ConfigureWebhooksRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<ConfigureWebhooks200Response>> {
+        if (requestParameters['webhooksConfigRequest'] == null) {
+            throw new runtime.RequiredError(
+                'webhooksConfigRequest',
+                'Required parameter "webhooksConfigRequest" was null or undefined when calling configureWebhooks().'
+            );
+        }
+
+        const queryParameters: any = {};
+
+        const headerParameters: runtime.HTTPHeaders = {};
+
+        headerParameters['Content-Type'] = 'application/json';
+
+        if (this.configuration && this.configuration.apiKey) {
+            headerParameters["X-Service-Key"] = await this.configuration.apiKey("X-Service-Key"); // ServiceKeyAuth authentication
+        }
+
+
+        let urlPath = `/api/v1/stripe/config/webhooks`;
+
+        const response = await this.request({
+            path: urlPath,
+            method: 'POST',
+            headers: headerParameters,
+            query: queryParameters,
+            body: WebhooksConfigRequestToJSON(requestParameters['webhooksConfigRequest']),
+        }, initOverrides);
+
+        return new runtime.JSONApiResponse(response, (jsonValue) => ConfigureWebhooks200ResponseFromJSON(jsonValue));
+    }
+
+    /**
+     * Creates, updates, or removes multiple webhook endpoints to match the desired configuration. Webhooks not in the request will be deleted.  ## Authentication Requires service key authentication.  ## Connect Webhooks Each webhook can have `connect: true` to listen to events from connected accounts.  ## URL Interpolation URLs support `${VAR}` environment variable interpolation when using the CLI. The CLI resolves these before sending to the API.  ## Use Cases - Configure multiple webhooks for different environments - Set up both account and Connect webhooks - Declarative webhook configuration management 
+     * Configure multiple webhook endpoints
+     */
+    async configureWebhooks(requestParameters: ConfigureWebhooksRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<ConfigureWebhooks200Response> {
+        const response = await this.configureWebhooksRaw(requestParameters, initOverrides);
+        return await response.value();
+    }
+
+    /**
+     * Retrieves the webhook signing secret for the most recent webhook configuration.  ## Authentication Requires service key authentication.  ## Use Cases - Retrieve signing secret for webhook signature verification - Debug webhook configuration 
+     * Get webhook secret
+     */
+    async getWebhookSecretRaw(initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<GetWebhookSecret200Response>> {
+        const queryParameters: any = {};
+
+        const headerParameters: runtime.HTTPHeaders = {};
+
+        if (this.configuration && this.configuration.apiKey) {
+            headerParameters["X-Service-Key"] = await this.configuration.apiKey("X-Service-Key"); // ServiceKeyAuth authentication
+        }
+
+
+        let urlPath = `/api/v1/stripe/config/webhook`;
+
+        const response = await this.request({
+            path: urlPath,
+            method: 'GET',
+            headers: headerParameters,
+            query: queryParameters,
+        }, initOverrides);
+
+        return new runtime.JSONApiResponse(response, (jsonValue) => GetWebhookSecret200ResponseFromJSON(jsonValue));
+    }
+
+    /**
+     * Retrieves the webhook signing secret for the most recent webhook configuration.  ## Authentication Requires service key authentication.  ## Use Cases - Retrieve signing secret for webhook signature verification - Debug webhook configuration 
+     * Get webhook secret
+     */
+    async getWebhookSecret(initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<GetWebhookSecret200Response> {
+        const response = await this.getWebhookSecretRaw(initOverrides);
+        return await response.value();
+    }
+
+}

package/src/apis/index.ts

@@ -8,3 +8,4 @@ export * from './V1PermissionsApi';
 export * from './V1StorageApi';
 export * from './V1StripeApi';
 export * from './V1TenantsApi';
+export * from './V1WebhooksApi';

package/src/models/AcceptInvite200Response.ts

@@ -2,9 +2,9 @@
 /* eslint-disable */
 /**
  * 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. 
+ * 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  ## 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.18
+ * The version of the OpenAPI document: 0.10.1
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/src/models/AcceptInviteRequest.ts

@@ -2,9 +2,9 @@
 /* eslint-disable */
 /**
  * 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. 
+ * 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  ## 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.18
+ * The version of the OpenAPI document: 0.10.1
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/src/models/AcceptInviteResponse.ts

@@ -2,9 +2,9 @@
 /* eslint-disable */
 /**
  * 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. 
+ * 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  ## 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.18
+ * The version of the OpenAPI document: 0.10.1
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/src/models/ActiveTenantResponse.ts

@@ -2,9 +2,9 @@
 /* eslint-disable */
 /**
  * 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. 
+ * 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  ## 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.18
+ * The version of the OpenAPI document: 0.10.1
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/src/models/AddInvoiceLineItem200Response.ts

@@ -0,0 +1,82 @@
+/* tslint:disable */
+/* eslint-disable */
+/**
+ * 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  ## 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.10.1
+ * 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 { mapValues } from '../runtime';
+import type { InvoiceLineItemResponse } from './InvoiceLineItemResponse';
+import {
+    InvoiceLineItemResponseFromJSON,
+    InvoiceLineItemResponseFromJSONTyped,
+    InvoiceLineItemResponseToJSON,
+    InvoiceLineItemResponseToJSONTyped,
+} from './InvoiceLineItemResponse';
+
+/**
+ * 
+ * @export
+ * @interface AddInvoiceLineItem200Response
+ */
+export interface AddInvoiceLineItem200Response {
+    /**
+     * HTTP status code
+     * @type {number}
+     * @memberof AddInvoiceLineItem200Response
+     */
+    status: number;
+    /**
+     * 
+     * @type {InvoiceLineItemResponse}
+     * @memberof AddInvoiceLineItem200Response
+     */
+    data?: InvoiceLineItemResponse;
+}
+
+/**
+ * Check if a given object implements the AddInvoiceLineItem200Response interface.
+ */
+export function instanceOfAddInvoiceLineItem200Response(value: object): value is AddInvoiceLineItem200Response {
+    if (!('status' in value) || value['status'] === undefined) return false;
+    return true;
+}
+
+export function AddInvoiceLineItem200ResponseFromJSON(json: any): AddInvoiceLineItem200Response {
+    return AddInvoiceLineItem200ResponseFromJSONTyped(json, false);
+}
+
+export function AddInvoiceLineItem200ResponseFromJSONTyped(json: any, ignoreDiscriminator: boolean): AddInvoiceLineItem200Response {
+    if (json == null) {
+        return json;
+    }
+    return {
+        
+        'status': json['status'],
+        'data': json['data'] == null ? undefined : InvoiceLineItemResponseFromJSON(json['data']),
+    };
+}
+
+export function AddInvoiceLineItem200ResponseToJSON(json: any): AddInvoiceLineItem200Response {
+    return AddInvoiceLineItem200ResponseToJSONTyped(json, false);
+}
+
+export function AddInvoiceLineItem200ResponseToJSONTyped(value?: AddInvoiceLineItem200Response | null, ignoreDiscriminator: boolean = false): any {
+    if (value == null) {
+        return value;
+    }
+
+    return {
+        
+        'status': value['status'],
+        'data': InvoiceLineItemResponseToJSON(value['data']),
+    };
+}
+

package/src/models/AddInvoiceLineItemRequest.ts

@@ -0,0 +1,94 @@
+/* tslint:disable */
+/* eslint-disable */
+/**
+ * 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  ## 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.10.1
+ * 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 { mapValues } from '../runtime';
+import type { CurrencyCode } from './CurrencyCode';
+import {
+    CurrencyCodeFromJSON,
+    CurrencyCodeFromJSONTyped,
+    CurrencyCodeToJSON,
+    CurrencyCodeToJSONTyped,
+} from './CurrencyCode';
+
+/**
+ * 
+ * @export
+ * @interface AddInvoiceLineItemRequest
+ */
+export interface AddInvoiceLineItemRequest {
+    /**
+     * Amount in cents (required)
+     * @type {number}
+     * @memberof AddInvoiceLineItemRequest
+     */
+    amount: number;
+    /**
+     * Description for the line item (required)
+     * @type {string}
+     * @memberof AddInvoiceLineItemRequest
+     */
+    description: string;
+    /**
+     * 
+     * @type {CurrencyCode}
+     * @memberof AddInvoiceLineItemRequest
+     */
+    currency: CurrencyCode;
+}
+
+
+
+/**
+ * Check if a given object implements the AddInvoiceLineItemRequest interface.
+ */
+export function instanceOfAddInvoiceLineItemRequest(value: object): value is AddInvoiceLineItemRequest {
+    if (!('amount' in value) || value['amount'] === undefined) return false;
+    if (!('description' in value) || value['description'] === undefined) return false;
+    if (!('currency' in value) || value['currency'] === undefined) return false;
+    return true;
+}
+
+export function AddInvoiceLineItemRequestFromJSON(json: any): AddInvoiceLineItemRequest {
+    return AddInvoiceLineItemRequestFromJSONTyped(json, false);
+}
+
+export function AddInvoiceLineItemRequestFromJSONTyped(json: any, ignoreDiscriminator: boolean): AddInvoiceLineItemRequest {
+    if (json == null) {
+        return json;
+    }
+    return {
+        
+        'amount': json['amount'],
+        'description': json['description'],
+        'currency': CurrencyCodeFromJSON(json['currency']),
+    };
+}
+
+export function AddInvoiceLineItemRequestToJSON(json: any): AddInvoiceLineItemRequest {
+    return AddInvoiceLineItemRequestToJSONTyped(json, false);
+}
+
+export function AddInvoiceLineItemRequestToJSONTyped(value?: AddInvoiceLineItemRequest | null, ignoreDiscriminator: boolean = false): any {
+    if (value == null) {
+        return value;
+    }
+
+    return {
+        
+        'amount': value['amount'],
+        'description': value['description'],
+        'currency': CurrencyCodeToJSON(value['currency']),
+    };
+}
+

package/src/models/AddSubscription200Response.ts

@@ -2,9 +2,9 @@
 /* eslint-disable */
 /**
  * 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. 
+ * 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  ## 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.18
+ * The version of the OpenAPI document: 0.10.1
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/src/models/AddSubscriptionRequest.ts

@@ -2,9 +2,9 @@
 /* eslint-disable */
 /**
  * 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. 
+ * 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  ## 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.18
+ * The version of the OpenAPI document: 0.10.1
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/src/models/AddSubscriptionResponse.ts

@@ -2,9 +2,9 @@
 /* eslint-disable */
 /**
  * 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. 
+ * 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  ## 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.18
+ * The version of the OpenAPI document: 0.10.1
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/src/models/ArchiveAllResponse.ts

@@ -2,9 +2,9 @@
 /* eslint-disable */
 /**
  * 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. 
+ * 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  ## 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.18
+ * The version of the OpenAPI document: 0.10.1
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/src/models/ArchiveAllStripeConfig200Response.ts

@@ -2,9 +2,9 @@
 /* eslint-disable */
 /**
  * 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. 
+ * 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  ## 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.18
+ * The version of the OpenAPI document: 0.10.1
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/src/models/BadRequest.ts

@@ -2,9 +2,9 @@
 /* eslint-disable */
 /**
  * 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. 
+ * 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  ## 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.18
+ * The version of the OpenAPI document: 0.10.1
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/src/models/BadRequestResponse.ts

@@ -2,9 +2,9 @@
 /* eslint-disable */
 /**
  * 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. 
+ * 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  ## 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.18
+ * The version of the OpenAPI document: 0.10.1
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/src/models/BillingInterval.ts

@@ -2,9 +2,9 @@
 /* eslint-disable */
 /**
  * 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. 
+ * 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  ## 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.18
+ * The version of the OpenAPI document: 0.10.1
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/src/models/BillingStatusResponse.ts

@@ -2,9 +2,9 @@
 /* eslint-disable */
 /**
  * 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. 
+ * 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  ## 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.18
+ * The version of the OpenAPI document: 0.10.1
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/src/models/CheckPermission200Response.ts

@@ -2,9 +2,9 @@
 /* eslint-disable */
 /**
  * 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. 
+ * 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  ## 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.18
+ * The version of the OpenAPI document: 0.10.1
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/src/models/CheckPermissionRequest.ts

@@ -2,9 +2,9 @@
 /* eslint-disable */
 /**
  * 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. 
+ * 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  ## 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.18
+ * The version of the OpenAPI document: 0.10.1
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/src/models/CheckPermissionRequestWithSubjectId.ts

@@ -2,9 +2,9 @@
 /* eslint-disable */
 /**
  * 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. 
+ * 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  ## 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.18
+ * The version of the OpenAPI document: 0.10.1
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/src/models/CheckPermissionRequestWithSubjectSet.ts

@@ -2,9 +2,9 @@
 /* eslint-disable */
 /**
  * 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. 
+ * 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  ## 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.18
+ * The version of the OpenAPI document: 0.10.1
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/src/models/CheckPermissionResponse.ts

@@ -2,9 +2,9 @@
 /* eslint-disable */
 /**
  * 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. 
+ * 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  ## 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.18
+ * The version of the OpenAPI document: 0.10.1
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/src/models/ConfigHistoryItem.ts

@@ -2,9 +2,9 @@
 /* eslint-disable */
 /**
  * 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. 
+ * 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  ## 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.18
+ * The version of the OpenAPI document: 0.10.1
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/src/models/ConfigHistoryPagination.ts

@@ -2,9 +2,9 @@
 /* eslint-disable */
 /**
  * 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. 
+ * 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  ## 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.18
+ * The version of the OpenAPI document: 0.10.1
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/src/models/ConfigHistoryResponse.ts

@@ -2,9 +2,9 @@
 /* eslint-disable */
 /**
  * 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. 
+ * 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  ## 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.18
+ * The version of the OpenAPI document: 0.10.1
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).