@omnibase/core-js 0.9.0 → 0.9.2

package/dist/models/GetRoleDefinitions200Response.js

@@ -5,7 +5,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.0
+ * The version of the OpenAPI document: 0.9.2
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/{esm/models/StripeConfigGet200Response.d.ts → models/GetStripeConfig200Response.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.0
+ * The version of the OpenAPI document: 0.9.2
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
@@ -13,27 +13,27 @@ import type { V1StripeConfigResponse } from './V1StripeConfigResponse';
 /**
  *
  * @export
- * @interface StripeConfigGet200Response
+ * @interface GetStripeConfig200Response
  */
-export interface StripeConfigGet200Response {
+export interface GetStripeConfig200Response {
     /**
      *
      * @type {V1StripeConfigResponse}
-     * @memberof StripeConfigGet200Response
+     * @memberof GetStripeConfig200Response
      */
     data?: V1StripeConfigResponse;
     /**
      * HTTP status code
      * @type {number}
-     * @memberof StripeConfigGet200Response
+     * @memberof GetStripeConfig200Response
      */
     status?: number;
 }
 /**
- * Check if a given object implements the StripeConfigGet200Response interface.
+ * Check if a given object implements the GetStripeConfig200Response interface.
  */
-export declare function instanceOfStripeConfigGet200Response(value: object): value is StripeConfigGet200Response;
-export declare function StripeConfigGet200ResponseFromJSON(json: any): StripeConfigGet200Response;
-export declare function StripeConfigGet200ResponseFromJSONTyped(json: any, ignoreDiscriminator: boolean): StripeConfigGet200Response;
-export declare function StripeConfigGet200ResponseToJSON(json: any): StripeConfigGet200Response;
-export declare function StripeConfigGet200ResponseToJSONTyped(value?: StripeConfigGet200Response | null, ignoreDiscriminator?: boolean): any;
+export declare function instanceOfGetStripeConfig200Response(value: object): value is GetStripeConfig200Response;
+export declare function GetStripeConfig200ResponseFromJSON(json: any): GetStripeConfig200Response;
+export declare function GetStripeConfig200ResponseFromJSONTyped(json: any, ignoreDiscriminator: boolean): GetStripeConfig200Response;
+export declare function GetStripeConfig200ResponseToJSON(json: any): GetStripeConfig200Response;
+export declare function GetStripeConfig200ResponseToJSONTyped(value?: GetStripeConfig200Response | null, ignoreDiscriminator?: boolean): any;

package/dist/models/{StripeConfigGet200Response.js → GetStripeConfig200Response.js}

@@ -5,7 +5,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.0
+ * The version of the OpenAPI document: 0.9.2
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
@@ -13,22 +13,22 @@
  * Do not edit the class manually.
  */
 Object.defineProperty(exports, "__esModule", { value: true });
-exports.instanceOfStripeConfigGet200Response = instanceOfStripeConfigGet200Response;
-exports.StripeConfigGet200ResponseFromJSON = StripeConfigGet200ResponseFromJSON;
-exports.StripeConfigGet200ResponseFromJSONTyped = StripeConfigGet200ResponseFromJSONTyped;
-exports.StripeConfigGet200ResponseToJSON = StripeConfigGet200ResponseToJSON;
-exports.StripeConfigGet200ResponseToJSONTyped = StripeConfigGet200ResponseToJSONTyped;
+exports.instanceOfGetStripeConfig200Response = instanceOfGetStripeConfig200Response;
+exports.GetStripeConfig200ResponseFromJSON = GetStripeConfig200ResponseFromJSON;
+exports.GetStripeConfig200ResponseFromJSONTyped = GetStripeConfig200ResponseFromJSONTyped;
+exports.GetStripeConfig200ResponseToJSON = GetStripeConfig200ResponseToJSON;
+exports.GetStripeConfig200ResponseToJSONTyped = GetStripeConfig200ResponseToJSONTyped;
 const V1StripeConfigResponse_1 = require("./V1StripeConfigResponse");
 /**
- * Check if a given object implements the StripeConfigGet200Response interface.
+ * Check if a given object implements the GetStripeConfig200Response interface.
  */
-function instanceOfStripeConfigGet200Response(value) {
+function instanceOfGetStripeConfig200Response(value) {
     return true;
 }
-function StripeConfigGet200ResponseFromJSON(json) {
-    return StripeConfigGet200ResponseFromJSONTyped(json, false);
+function GetStripeConfig200ResponseFromJSON(json) {
+    return GetStripeConfig200ResponseFromJSONTyped(json, false);
 }
-function StripeConfigGet200ResponseFromJSONTyped(json, ignoreDiscriminator) {
+function GetStripeConfig200ResponseFromJSONTyped(json, ignoreDiscriminator) {
     if (json == null) {
         return json;
     }
@@ -37,10 +37,10 @@ function StripeConfigGet200ResponseFromJSONTyped(json, ignoreDiscriminator) {
         'status': json['status'] == null ? undefined : json['status'],
     };
 }
-function StripeConfigGet200ResponseToJSON(json) {
-    return StripeConfigGet200ResponseToJSONTyped(json, false);
+function GetStripeConfig200ResponseToJSON(json) {
+    return GetStripeConfig200ResponseToJSONTyped(json, false);
 }
-function StripeConfigGet200ResponseToJSONTyped(value, ignoreDiscriminator = false) {
+function GetStripeConfig200ResponseToJSONTyped(value, ignoreDiscriminator = false) {
     if (value == null) {
         return value;
     }

package/dist/{esm/models/StripeConfigHistoryGet200Response.d.ts → models/GetStripeConfigHistory200Response.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.0
+ * The version of the OpenAPI document: 0.9.2
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
@@ -13,27 +13,27 @@ import type { V1ConfigHistoryResponse } from './V1ConfigHistoryResponse';
 /**
  *
  * @export
- * @interface StripeConfigHistoryGet200Response
+ * @interface GetStripeConfigHistory200Response
  */
-export interface StripeConfigHistoryGet200Response {
+export interface GetStripeConfigHistory200Response {
     /**
      *
      * @type {V1ConfigHistoryResponse}
-     * @memberof StripeConfigHistoryGet200Response
+     * @memberof GetStripeConfigHistory200Response
      */
     data?: V1ConfigHistoryResponse;
     /**
      * HTTP status code
      * @type {number}
-     * @memberof StripeConfigHistoryGet200Response
+     * @memberof GetStripeConfigHistory200Response
      */
     status?: number;
 }
 /**
- * Check if a given object implements the StripeConfigHistoryGet200Response interface.
+ * Check if a given object implements the GetStripeConfigHistory200Response interface.
  */
-export declare function instanceOfStripeConfigHistoryGet200Response(value: object): value is StripeConfigHistoryGet200Response;
-export declare function StripeConfigHistoryGet200ResponseFromJSON(json: any): StripeConfigHistoryGet200Response;
-export declare function StripeConfigHistoryGet200ResponseFromJSONTyped(json: any, ignoreDiscriminator: boolean): StripeConfigHistoryGet200Response;
-export declare function StripeConfigHistoryGet200ResponseToJSON(json: any): StripeConfigHistoryGet200Response;
-export declare function StripeConfigHistoryGet200ResponseToJSONTyped(value?: StripeConfigHistoryGet200Response | null, ignoreDiscriminator?: boolean): any;
+export declare function instanceOfGetStripeConfigHistory200Response(value: object): value is GetStripeConfigHistory200Response;
+export declare function GetStripeConfigHistory200ResponseFromJSON(json: any): GetStripeConfigHistory200Response;
+export declare function GetStripeConfigHistory200ResponseFromJSONTyped(json: any, ignoreDiscriminator: boolean): GetStripeConfigHistory200Response;
+export declare function GetStripeConfigHistory200ResponseToJSON(json: any): GetStripeConfigHistory200Response;
+export declare function GetStripeConfigHistory200ResponseToJSONTyped(value?: GetStripeConfigHistory200Response | null, ignoreDiscriminator?: boolean): any;

package/dist/models/{StripeConfigHistoryGet200Response.js → GetStripeConfigHistory200Response.js}

@@ -5,7 +5,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.0
+ * The version of the OpenAPI document: 0.9.2
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
@@ -13,22 +13,22 @@
  * Do not edit the class manually.
  */
 Object.defineProperty(exports, "__esModule", { value: true });
-exports.instanceOfStripeConfigHistoryGet200Response = instanceOfStripeConfigHistoryGet200Response;
-exports.StripeConfigHistoryGet200ResponseFromJSON = StripeConfigHistoryGet200ResponseFromJSON;
-exports.StripeConfigHistoryGet200ResponseFromJSONTyped = StripeConfigHistoryGet200ResponseFromJSONTyped;
-exports.StripeConfigHistoryGet200ResponseToJSON = StripeConfigHistoryGet200ResponseToJSON;
-exports.StripeConfigHistoryGet200ResponseToJSONTyped = StripeConfigHistoryGet200ResponseToJSONTyped;
+exports.instanceOfGetStripeConfigHistory200Response = instanceOfGetStripeConfigHistory200Response;
+exports.GetStripeConfigHistory200ResponseFromJSON = GetStripeConfigHistory200ResponseFromJSON;
+exports.GetStripeConfigHistory200ResponseFromJSONTyped = GetStripeConfigHistory200ResponseFromJSONTyped;
+exports.GetStripeConfigHistory200ResponseToJSON = GetStripeConfigHistory200ResponseToJSON;
+exports.GetStripeConfigHistory200ResponseToJSONTyped = GetStripeConfigHistory200ResponseToJSONTyped;
 const V1ConfigHistoryResponse_1 = require("./V1ConfigHistoryResponse");
 /**
- * Check if a given object implements the StripeConfigHistoryGet200Response interface.
+ * Check if a given object implements the GetStripeConfigHistory200Response interface.
  */
-function instanceOfStripeConfigHistoryGet200Response(value) {
+function instanceOfGetStripeConfigHistory200Response(value) {
     return true;
 }
-function StripeConfigHistoryGet200ResponseFromJSON(json) {
-    return StripeConfigHistoryGet200ResponseFromJSONTyped(json, false);
+function GetStripeConfigHistory200ResponseFromJSON(json) {
+    return GetStripeConfigHistory200ResponseFromJSONTyped(json, false);
 }
-function StripeConfigHistoryGet200ResponseFromJSONTyped(json, ignoreDiscriminator) {
+function GetStripeConfigHistory200ResponseFromJSONTyped(json, ignoreDiscriminator) {
     if (json == null) {
         return json;
     }
@@ -37,10 +37,10 @@ function StripeConfigHistoryGet200ResponseFromJSONTyped(json, ignoreDiscriminato
         'status': json['status'] == null ? undefined : json['status'],
     };
 }
-function StripeConfigHistoryGet200ResponseToJSON(json) {
-    return StripeConfigHistoryGet200ResponseToJSONTyped(json, false);
+function GetStripeConfigHistory200ResponseToJSON(json) {
+    return GetStripeConfigHistory200ResponseToJSONTyped(json, false);
 }
-function StripeConfigHistoryGet200ResponseToJSONTyped(value, ignoreDiscriminator = false) {
+function GetStripeConfigHistory200ResponseToJSONTyped(value, ignoreDiscriminator = false) {
     if (value == null) {
         return value;
     }

package/dist/models/GetTenantBillingStatus200Response.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.0
+ * The version of the OpenAPI document: 0.9.2
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/models/GetTenantBillingStatus200Response.js

@@ -5,7 +5,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.0
+ * The version of the OpenAPI document: 0.9.2
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/models/GetTenantJWT200Response.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.0
+ * The version of the OpenAPI document: 0.9.2
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/models/GetTenantJWT200Response.js

@@ -5,7 +5,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.0
+ * The version of the OpenAPI document: 0.9.2
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/models/HandlersBadRequestResponse.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.0
+ * The version of the OpenAPI document: 0.9.2
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/models/HandlersBadRequestResponse.js

@@ -5,7 +5,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.0
+ * The version of the OpenAPI document: 0.9.2
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/models/HandlersForbiddenResponse.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.0
+ * The version of the OpenAPI document: 0.9.2
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/models/HandlersForbiddenResponse.js

@@ -5,7 +5,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.0
+ * The version of the OpenAPI document: 0.9.2
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/models/HandlersInternalServerErrorResponse.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.0
+ * The version of the OpenAPI document: 0.9.2
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/models/HandlersInternalServerErrorResponse.js

@@ -5,7 +5,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.0
+ * The version of the OpenAPI document: 0.9.2
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/models/HandlersNotFoundErrorResponse.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.0
+ * The version of the OpenAPI document: 0.9.2
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/models/HandlersNotFoundErrorResponse.js

@@ -5,7 +5,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.0
+ * The version of the OpenAPI document: 0.9.2
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/models/HandlersSuccessResponse.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.0
+ * The version of the OpenAPI document: 0.9.2
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/models/HandlersSuccessResponse.js

@@ -5,7 +5,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.0
+ * The version of the OpenAPI document: 0.9.2
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/models/HandlersUnauthorizedResponse.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.0
+ * The version of the OpenAPI document: 0.9.2
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/models/HandlersUnauthorizedResponse.js

@@ -5,7 +5,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.0
+ * The version of the OpenAPI document: 0.9.2
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/models/ListRoles200Response.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.0
+ * The version of the OpenAPI document: 0.9.2
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/models/ListRoles200Response.js

@@ -5,7 +5,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.0
+ * The version of the OpenAPI document: 0.9.2
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/models/ListTenantSubscriptions200Response.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.0
+ * The version of the OpenAPI document: 0.9.2
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/models/ListTenantSubscriptions200Response.js

@@ -5,7 +5,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.0
+ * The version of the OpenAPI document: 0.9.2
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/models/ListTenantUsers200Response.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.0
+ * The version of the OpenAPI document: 0.9.2
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/models/ListTenantUsers200Response.js

@@ -5,7 +5,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.0
+ * The version of the OpenAPI document: 0.9.2
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/models/ModelsBillingStatusResponse.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.0
+ * The version of the OpenAPI document: 0.9.2
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/models/ModelsBillingStatusResponse.js

@@ -5,7 +5,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.0
+ * The version of the OpenAPI document: 0.9.2
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/models/ModelsDeleteObjectRequest.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.0
+ * The version of the OpenAPI document: 0.9.2
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/models/ModelsDeleteObjectRequest.js

@@ -5,7 +5,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.0
+ * The version of the OpenAPI document: 0.9.2
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/models/ModelsDownloadRequest.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.0
+ * The version of the OpenAPI document: 0.9.2
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/models/ModelsDownloadRequest.js

@@ -5,7 +5,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.0
+ * The version of the OpenAPI document: 0.9.2
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/models/ModelsDownloadResponse.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.0
+ * The version of the OpenAPI document: 0.9.2
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/models/ModelsDownloadResponse.js

@@ -5,7 +5,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.0
+ * The version of the OpenAPI document: 0.9.2
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/models/ModelsMessageResponse.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.0
+ * The version of the OpenAPI document: 0.9.2
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/models/ModelsMessageResponse.js

@@ -5,7 +5,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.0
+ * The version of the OpenAPI document: 0.9.2
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/models/ModelsMeter.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.0
+ * The version of the OpenAPI document: 0.9.2
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/models/ModelsMeter.js

@@ -5,7 +5,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.0
+ * The version of the OpenAPI document: 0.9.2
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/models/ModelsMeterCustomerMapping.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.0
+ * The version of the OpenAPI document: 0.9.2
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).