@omnibase/core-js 0.9.12 → 0.9.14

package/src/apis/V1TenantsApi.ts

@@ -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).
@@ -19,6 +19,7 @@ import type {
   AssignRole200Response,
   CreateInvite200Response,
   CreateRole200Response,
+  CreateSubscription200Response,
   CreateTenant200Response,
   DeleteRole200Response,
   DeleteTenant200Response,
@@ -34,13 +35,16 @@ import type {
   ListRoles200Response,
   ListTenantSubscriptions200Response,
   ListTenantUsers200Response,
+  RemoveSubscription200Response,
   SwitchActiveTenant200Response,
   TenantsAcceptInviteRequest,
   TenantsAssignRoleRequest,
   TenantsCreateRoleRequest,
+  TenantsCreateSubscriptionRequest,
   TenantsCreateTenantRequest,
   TenantsCreateTenantUserInviteRequest,
   TenantsDeleteTenantUserRequest,
+  TenantsRemoveSubscriptionRequest,
   TenantsSwitchTenantRequest,
   TenantsUpdateRoleRequest,
   TenantsUpdateTenantUserRoleRequest,
@@ -55,6 +59,8 @@ import {
     CreateInvite200ResponseToJSON,
     CreateRole200ResponseFromJSON,
     CreateRole200ResponseToJSON,
+    CreateSubscription200ResponseFromJSON,
+    CreateSubscription200ResponseToJSON,
     CreateTenant200ResponseFromJSON,
     CreateTenant200ResponseToJSON,
     DeleteRole200ResponseFromJSON,
@@ -85,6 +91,8 @@ import {
     ListTenantSubscriptions200ResponseToJSON,
     ListTenantUsers200ResponseFromJSON,
     ListTenantUsers200ResponseToJSON,
+    RemoveSubscription200ResponseFromJSON,
+    RemoveSubscription200ResponseToJSON,
     SwitchActiveTenant200ResponseFromJSON,
     SwitchActiveTenant200ResponseToJSON,
     TenantsAcceptInviteRequestFromJSON,
@@ -93,12 +101,16 @@ import {
     TenantsAssignRoleRequestToJSON,
     TenantsCreateRoleRequestFromJSON,
     TenantsCreateRoleRequestToJSON,
+    TenantsCreateSubscriptionRequestFromJSON,
+    TenantsCreateSubscriptionRequestToJSON,
     TenantsCreateTenantRequestFromJSON,
     TenantsCreateTenantRequestToJSON,
     TenantsCreateTenantUserInviteRequestFromJSON,
     TenantsCreateTenantUserInviteRequestToJSON,
     TenantsDeleteTenantUserRequestFromJSON,
     TenantsDeleteTenantUserRequestToJSON,
+    TenantsRemoveSubscriptionRequestFromJSON,
+    TenantsRemoveSubscriptionRequestToJSON,
     TenantsSwitchTenantRequestFromJSON,
     TenantsSwitchTenantRequestToJSON,
     TenantsUpdateRoleRequestFromJSON,
@@ -126,6 +138,10 @@ export interface CreateRoleRequest {
     request: TenantsCreateRoleRequest;
 }
 
+export interface CreateSubscriptionRequest {
+    request: TenantsCreateSubscriptionRequest;
+}
+
 export interface CreateTenantRequest {
     request: TenantsCreateTenantRequest;
 }
@@ -134,6 +150,10 @@ export interface DeleteRoleRequest {
     roleId: string;
 }
 
+export interface RemoveSubscriptionRequest {
+    request: TenantsRemoveSubscriptionRequest;
+}
+
 export interface RemoveTenantUserRequest {
     request: TenantsDeleteTenantUserRequest;
 }
@@ -344,6 +364,51 @@ export class V1TenantsApi extends runtime.BaseAPI {
         return await response.value();
     }
 
+    /**
+     * Creates a Stripe subscription for the authenticated tenant using the provided plan ID.  ## Authentication Requires JWT token with tenant context.  ## Request Parameters - **plan_id** (required): The configuration item ID (e.g., \"neon_compute_starter\") that maps to a Stripe price - **stripe_customer_id** (optional): Override tenant\'s Stripe customer ID if needed  ## Process Flow 1. Validates the plan_id and maps it to a Stripe price_id via the stripe_id_mappings table 2. Resolves the Stripe customer ID from the authenticated tenant (or uses provided stripe_customer_id) 3. Creates the subscription in Stripe with the specified price 4. Returns the subscription ID and status  ## Use Cases - Subscribe tenant to metered pricing plans (compute, storage, workers) - Enable usage-based billing for resources - Add additional services to tenant\'s billing
+     * Create subscription
+     */
+    async createSubscriptionRaw(requestParameters: CreateSubscriptionRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<CreateSubscription200Response>> {
+        if (requestParameters['request'] == null) {
+            throw new runtime.RequiredError(
+                'request',
+                'Required parameter "request" was null or undefined when calling createSubscription().'
+            );
+        }
+
+        const queryParameters: any = {};
+
+        const headerParameters: runtime.HTTPHeaders = {};
+
+        headerParameters['Content-Type'] = 'application/json';
+
+        if (this.configuration && this.configuration.apiKey) {
+            headerParameters["Authorization"] = await this.configuration.apiKey("Authorization"); // BearerAuth authentication
+        }
+
+
+        let urlPath = `/api/v1/payments/subscription`;
+
+        const response = await this.request({
+            path: urlPath,
+            method: 'POST',
+            headers: headerParameters,
+            query: queryParameters,
+            body: TenantsCreateSubscriptionRequestToJSON(requestParameters['request']),
+        }, initOverrides);
+
+        return new runtime.JSONApiResponse(response, (jsonValue) => CreateSubscription200ResponseFromJSON(jsonValue));
+    }
+
+    /**
+     * Creates a Stripe subscription for the authenticated tenant using the provided plan ID.  ## Authentication Requires JWT token with tenant context.  ## Request Parameters - **plan_id** (required): The configuration item ID (e.g., \"neon_compute_starter\") that maps to a Stripe price - **stripe_customer_id** (optional): Override tenant\'s Stripe customer ID if needed  ## Process Flow 1. Validates the plan_id and maps it to a Stripe price_id via the stripe_id_mappings table 2. Resolves the Stripe customer ID from the authenticated tenant (or uses provided stripe_customer_id) 3. Creates the subscription in Stripe with the specified price 4. Returns the subscription ID and status  ## Use Cases - Subscribe tenant to metered pricing plans (compute, storage, workers) - Enable usage-based billing for resources - Add additional services to tenant\'s billing
+     * Create subscription
+     */
+    async createSubscription(requestParameters: CreateSubscriptionRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<CreateSubscription200Response> {
+        const response = await this.createSubscriptionRaw(requestParameters, initOverrides);
+        return await response.value();
+    }
+
     /**
      * Creates a new tenant organization with Stripe customer, sets up owner role, and makes it the active tenant for the creator.  ## Authentication Requires JWT token.  ## Process 1. Creates Stripe customer (if billing_email provided) 2. Creates tenant in database 3. Sets up default tenant settings 4. Adds creator as owner 5. Assigns owner role with all permissions 6. Sets as active tenant and returns JWT token
      * Create tenant
@@ -677,6 +742,51 @@ export class V1TenantsApi extends runtime.BaseAPI {
         return await response.value();
     }
 
+    /**
+     * Cancels a Stripe subscription immediately for the authenticated tenant based on the plan ID.  ## Authentication Requires JWT token with tenant context.  ## Request Parameters - **plan_id** (required): The configuration item ID (e.g., \"neon_compute_starter\") to identify which subscription to cancel - **stripe_customer_id** (optional): Override tenant\'s Stripe customer ID if needed  ## Process Flow 1. Validates the plan_id and maps it to a Stripe price_id via the stripe_id_mappings table 2. Resolves the Stripe customer ID from the authenticated tenant (or uses provided stripe_customer_id) 3. Finds the active subscription matching the price_id for the customer 4. Cancels the subscription immediately in Stripe 5. Returns the cancellation confirmation  ## Notes - The subscription is canceled immediately, not at the end of the billing period - If no matching subscription is found, returns a 404 error - Only active, trialing, or past_due subscriptions can be canceled  ## Use Cases - Remove specific service subscriptions from tenant - Downgrade by removing premium features - Stop billing for unused resources
+     * Remove subscription
+     */
+    async removeSubscriptionRaw(requestParameters: RemoveSubscriptionRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<RemoveSubscription200Response>> {
+        if (requestParameters['request'] == null) {
+            throw new runtime.RequiredError(
+                'request',
+                'Required parameter "request" was null or undefined when calling removeSubscription().'
+            );
+        }
+
+        const queryParameters: any = {};
+
+        const headerParameters: runtime.HTTPHeaders = {};
+
+        headerParameters['Content-Type'] = 'application/json';
+
+        if (this.configuration && this.configuration.apiKey) {
+            headerParameters["Authorization"] = await this.configuration.apiKey("Authorization"); // BearerAuth authentication
+        }
+
+
+        let urlPath = `/api/v1/payments/subscription`;
+
+        const response = await this.request({
+            path: urlPath,
+            method: 'DELETE',
+            headers: headerParameters,
+            query: queryParameters,
+            body: TenantsRemoveSubscriptionRequestToJSON(requestParameters['request']),
+        }, initOverrides);
+
+        return new runtime.JSONApiResponse(response, (jsonValue) => RemoveSubscription200ResponseFromJSON(jsonValue));
+    }
+
+    /**
+     * Cancels a Stripe subscription immediately for the authenticated tenant based on the plan ID.  ## Authentication Requires JWT token with tenant context.  ## Request Parameters - **plan_id** (required): The configuration item ID (e.g., \"neon_compute_starter\") to identify which subscription to cancel - **stripe_customer_id** (optional): Override tenant\'s Stripe customer ID if needed  ## Process Flow 1. Validates the plan_id and maps it to a Stripe price_id via the stripe_id_mappings table 2. Resolves the Stripe customer ID from the authenticated tenant (or uses provided stripe_customer_id) 3. Finds the active subscription matching the price_id for the customer 4. Cancels the subscription immediately in Stripe 5. Returns the cancellation confirmation  ## Notes - The subscription is canceled immediately, not at the end of the billing period - If no matching subscription is found, returns a 404 error - Only active, trialing, or past_due subscriptions can be canceled  ## Use Cases - Remove specific service subscriptions from tenant - Downgrade by removing premium features - Stop billing for unused resources
+     * Remove subscription
+     */
+    async removeSubscription(requestParameters: RemoveSubscriptionRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<RemoveSubscription200Response> {
+        const response = await this.removeSubscriptionRaw(requestParameters, initOverrides);
+        return await response.value();
+    }
+
     /**
      * Removes a user from the tenant and cleans up all associated permissions and Keto relationships.  ## Authentication Requires JWT token with `remove_user` permission.  ## Restrictions - Cannot remove the last owner (must have at least one owner) - Removing an owner requires `remove_owner_role` permission  ## Process 1. Verifies permissions 2. Removes from role\'s user list 3. Deletes all Keto relationships 4. Removes from database 5. Cleans up user\'s tenant state
      * Remove tenant user

package/src/apis/index.ts

@@ -1,7 +1,7 @@
 /* tslint:disable */
 /* eslint-disable */
 export * from './V1AuthApi';
-export * from './V1DatabaseApi';
+export * from './V1ConfigurationApi';
 export * from './V1PaymentsApi';
 export * from './V1PermissionsApi';
 export * from './V1StorageApi';

package/src/models/AcceptInvite200Response.ts

@@ -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/src/models/ApiV1StorageDownloadPost200Response.ts

@@ -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/src/models/ApiV1StorageObjectDelete200Response.ts

@@ -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/src/models/ApiV1StorageUploadPost200Response.ts

@@ -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/src/models/ArchiveAllStripeConfig200Response.ts

@@ -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/src/models/AssignRole200Response.ts

@@ -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/src/models/CheckPermission200Response.ts

@@ -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/src/models/ClientAuthenticatorAssuranceLevel.ts

@@ -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/src/models/ClientIdentity.ts

@@ -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/src/models/ClientIdentityCredentials.ts

@@ -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/src/models/ClientRecoveryIdentityAddress.ts

@@ -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/src/models/ClientRelationship.ts

@@ -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/src/models/ClientSession.ts

@@ -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/src/models/ClientSessionAuthenticationMethod.ts

@@ -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/src/models/ClientSessionDevice.ts

@@ -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/src/models/ClientSubjectSet.ts

@@ -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/src/models/ClientVerifiableIdentityAddress.ts

@@ -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/src/models/ConvertStripeIDToConfigID200Response.ts

@@ -0,0 +1,81 @@
+/* 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 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 { mapValues } from '../runtime';
+import type { V1StripeIDConversionResponse } from './V1StripeIDConversionResponse';
+import {
+    V1StripeIDConversionResponseFromJSON,
+    V1StripeIDConversionResponseFromJSONTyped,
+    V1StripeIDConversionResponseToJSON,
+    V1StripeIDConversionResponseToJSONTyped,
+} from './V1StripeIDConversionResponse';
+
+/**
+ * 
+ * @export
+ * @interface ConvertStripeIDToConfigID200Response
+ */
+export interface ConvertStripeIDToConfigID200Response {
+    /**
+     * 
+     * @type {V1StripeIDConversionResponse}
+     * @memberof ConvertStripeIDToConfigID200Response
+     */
+    data?: V1StripeIDConversionResponse;
+    /**
+     * HTTP status code
+     * @type {number}
+     * @memberof ConvertStripeIDToConfigID200Response
+     */
+    status?: number;
+}
+
+/**
+ * Check if a given object implements the ConvertStripeIDToConfigID200Response interface.
+ */
+export function instanceOfConvertStripeIDToConfigID200Response(value: object): value is ConvertStripeIDToConfigID200Response {
+    return true;
+}
+
+export function ConvertStripeIDToConfigID200ResponseFromJSON(json: any): ConvertStripeIDToConfigID200Response {
+    return ConvertStripeIDToConfigID200ResponseFromJSONTyped(json, false);
+}
+
+export function ConvertStripeIDToConfigID200ResponseFromJSONTyped(json: any, ignoreDiscriminator: boolean): ConvertStripeIDToConfigID200Response {
+    if (json == null) {
+        return json;
+    }
+    return {
+        
+        'data': json['data'] == null ? undefined : V1StripeIDConversionResponseFromJSON(json['data']),
+        'status': json['status'] == null ? undefined : json['status'],
+    };
+}
+
+export function ConvertStripeIDToConfigID200ResponseToJSON(json: any): ConvertStripeIDToConfigID200Response {
+    return ConvertStripeIDToConfigID200ResponseToJSONTyped(json, false);
+}
+
+export function ConvertStripeIDToConfigID200ResponseToJSONTyped(value?: ConvertStripeIDToConfigID200Response | null, ignoreDiscriminator: boolean = false): any {
+    if (value == null) {
+        return value;
+    }
+
+    return {
+        
+        'data': V1StripeIDConversionResponseToJSON(value['data']),
+        'status': value['status'],
+    };
+}
+

package/src/models/CreateCheckout200Response.ts

@@ -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/src/models/CreateCustomerPortal200Response.ts

@@ -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/src/models/CreateInvite200Response.ts

@@ -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/src/models/CreateOrUpdateEmailTemplate200Response.ts

@@ -0,0 +1,81 @@
+/* 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 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 { mapValues } from '../runtime';
+import type { CreateOrUpdateEmailTemplate200ResponseAllOfData } from './CreateOrUpdateEmailTemplate200ResponseAllOfData';
+import {
+    CreateOrUpdateEmailTemplate200ResponseAllOfDataFromJSON,
+    CreateOrUpdateEmailTemplate200ResponseAllOfDataFromJSONTyped,
+    CreateOrUpdateEmailTemplate200ResponseAllOfDataToJSON,
+    CreateOrUpdateEmailTemplate200ResponseAllOfDataToJSONTyped,
+} from './CreateOrUpdateEmailTemplate200ResponseAllOfData';
+
+/**
+ * 
+ * @export
+ * @interface CreateOrUpdateEmailTemplate200Response
+ */
+export interface CreateOrUpdateEmailTemplate200Response {
+    /**
+     * 
+     * @type {CreateOrUpdateEmailTemplate200ResponseAllOfData}
+     * @memberof CreateOrUpdateEmailTemplate200Response
+     */
+    data?: CreateOrUpdateEmailTemplate200ResponseAllOfData;
+    /**
+     * HTTP status code
+     * @type {number}
+     * @memberof CreateOrUpdateEmailTemplate200Response
+     */
+    status?: number;
+}
+
+/**
+ * Check if a given object implements the CreateOrUpdateEmailTemplate200Response interface.
+ */
+export function instanceOfCreateOrUpdateEmailTemplate200Response(value: object): value is CreateOrUpdateEmailTemplate200Response {
+    return true;
+}
+
+export function CreateOrUpdateEmailTemplate200ResponseFromJSON(json: any): CreateOrUpdateEmailTemplate200Response {
+    return CreateOrUpdateEmailTemplate200ResponseFromJSONTyped(json, false);
+}
+
+export function CreateOrUpdateEmailTemplate200ResponseFromJSONTyped(json: any, ignoreDiscriminator: boolean): CreateOrUpdateEmailTemplate200Response {
+    if (json == null) {
+        return json;
+    }
+    return {
+        
+        'data': json['data'] == null ? undefined : CreateOrUpdateEmailTemplate200ResponseAllOfDataFromJSON(json['data']),
+        'status': json['status'] == null ? undefined : json['status'],
+    };
+}
+
+export function CreateOrUpdateEmailTemplate200ResponseToJSON(json: any): CreateOrUpdateEmailTemplate200Response {
+    return CreateOrUpdateEmailTemplate200ResponseToJSONTyped(json, false);
+}
+
+export function CreateOrUpdateEmailTemplate200ResponseToJSONTyped(value?: CreateOrUpdateEmailTemplate200Response | null, ignoreDiscriminator: boolean = false): any {
+    if (value == null) {
+        return value;
+    }
+
+    return {
+        
+        'data': CreateOrUpdateEmailTemplate200ResponseAllOfDataToJSON(value['data']),
+        'status': value['status'],
+    };
+}
+