@omnibase/core-js 0.9.3 → 0.9.5

package/dist/apis/index.js

@@ -16,6 +16,7 @@ var __exportStar = (this && this.__exportStar) || function(m, exports) {
 Object.defineProperty(exports, "__esModule", { value: true });
 /* tslint:disable */
 /* eslint-disable */
+__exportStar(require("./V1AuthApi"), exports);
 __exportStar(require("./V1DatabaseApi"), exports);
 __exportStar(require("./V1PaymentsApi"), exports);
 __exportStar(require("./V1PermissionsApi"), exports);

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

@@ -0,0 +1,68 @@
+/**
+ * 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.5
+ * 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 { ApiV1AuthActiveTenantGet200Response, ApiV1AuthIdentityGet200Response, ApiV1AuthLogoutPost200Response, ApiV1AuthSessionGet200Response, ApiV1AuthWhoamiGet200Response } from '../models/index';
+/**
+ *
+ */
+export declare class V1AuthApi extends runtime.BaseAPI {
+    /**
+     * Returns the full tenant object for the user\'s currently active tenant.  ## Tenant Context Users can be members of multiple tenants but only one is active at a time. The active tenant determines which resources and data the user can access.  ## Use Case Determine which tenant context to use for API calls and data filtering.
+     * Get active tenant
+     */
+    apiV1AuthActiveTenantGetRaw(initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<ApiV1AuthActiveTenantGet200Response>>;
+    /**
+     * Returns the full tenant object for the user\'s currently active tenant.  ## Tenant Context Users can be members of multiple tenants but only one is active at a time. The active tenant determines which resources and data the user can access.  ## Use Case Determine which tenant context to use for API calls and data filtering.
+     * Get active tenant
+     */
+    apiV1AuthActiveTenantGet(initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<ApiV1AuthActiveTenantGet200Response>;
+    /**
+     * Returns the current authenticated user\'s identity information (traits like email, name).  ## Identity Data - User ID (unique identifier) - Traits (email, first name, last name based on identity schema) - Schema ID - Created/updated timestamps  ## Use Case Lighter alternative to full session when you only need user profile data.
+     * Get current identity
+     */
+    apiV1AuthIdentityGetRaw(initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<ApiV1AuthIdentityGet200Response>>;
+    /**
+     * Returns the current authenticated user\'s identity information (traits like email, name).  ## Identity Data - User ID (unique identifier) - Traits (email, first name, last name based on identity schema) - Schema ID - Created/updated timestamps  ## Use Case Lighter alternative to full session when you only need user profile data.
+     * Get current identity
+     */
+    apiV1AuthIdentityGet(initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<ApiV1AuthIdentityGet200Response>;
+    /**
+     * Creates a Kratos logout flow and returns the logout URL for browser redirect.  ## Logout Process 1. Request this endpoint to get logout URL 2. Redirect browser to the returned logout_url 3. Session will be invalidated and user logged out  ## Cookie Cleanup The logout URL handles clearing session cookies automatically.
+     * Logout user
+     */
+    apiV1AuthLogoutPostRaw(initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<ApiV1AuthLogoutPost200Response>>;
+    /**
+     * Creates a Kratos logout flow and returns the logout URL for browser redirect.  ## Logout Process 1. Request this endpoint to get logout URL 2. Redirect browser to the returned logout_url 3. Session will be invalidated and user logged out  ## Cookie Cleanup The logout URL handles clearing session cookies automatically.
+     * Logout user
+     */
+    apiV1AuthLogoutPost(initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<ApiV1AuthLogoutPost200Response>;
+    /**
+     * Returns the current authenticated user\'s session including identity and tenant information.  ## Session Data - Session metadata (ID, expiry, authentication methods) - Identity information (user ID, traits like email, name) - Active tenant context (if user has tenant membership)  ## Authentication Requires valid session via Cookie or X-Session-Token header.
+     * Get current session
+     */
+    apiV1AuthSessionGetRaw(initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<ApiV1AuthSessionGet200Response>>;
+    /**
+     * Returns the current authenticated user\'s session including identity and tenant information.  ## Session Data - Session metadata (ID, expiry, authentication methods) - Identity information (user ID, traits like email, name) - Active tenant context (if user has tenant membership)  ## Authentication Requires valid session via Cookie or X-Session-Token header.
+     * Get current session
+     */
+    apiV1AuthSessionGet(initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<ApiV1AuthSessionGet200Response>;
+    /**
+     * Lightweight endpoint to check if the user is authenticated.  ## Response Returns boolean authentication status and user ID if authenticated.  ## Use Case Quick auth checks for route guards without fetching full session data.
+     * Check authentication status
+     */
+    apiV1AuthWhoamiGetRaw(initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<ApiV1AuthWhoamiGet200Response>>;
+    /**
+     * Lightweight endpoint to check if the user is authenticated.  ## Response Returns boolean authentication status and user ID if authenticated.  ## Use Case Quick auth checks for route guards without fetching full session data.
+     * Check authentication status
+     */
+    apiV1AuthWhoamiGet(initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<ApiV1AuthWhoamiGet200Response>;
+}

package/dist/esm/apis/V1AuthApi.js

@@ -0,0 +1,184 @@
+/* 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.5
+ * 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.
+ */
+var __awaiter = (this && this.__awaiter) || function (thisArg, _arguments, P, generator) {
+    function adopt(value) { return value instanceof P ? value : new P(function (resolve) { resolve(value); }); }
+    return new (P || (P = Promise))(function (resolve, reject) {
+        function fulfilled(value) { try { step(generator.next(value)); } catch (e) { reject(e); } }
+        function rejected(value) { try { step(generator["throw"](value)); } catch (e) { reject(e); } }
+        function step(result) { result.done ? resolve(result.value) : adopt(result.value).then(fulfilled, rejected); }
+        step((generator = generator.apply(thisArg, _arguments || [])).next());
+    });
+};
+import * as runtime from '../runtime';
+import { ApiV1AuthActiveTenantGet200ResponseFromJSON, ApiV1AuthIdentityGet200ResponseFromJSON, ApiV1AuthLogoutPost200ResponseFromJSON, ApiV1AuthSessionGet200ResponseFromJSON, ApiV1AuthWhoamiGet200ResponseFromJSON, } from '../models/index';
+/**
+ *
+ */
+export class V1AuthApi extends runtime.BaseAPI {
+    /**
+     * Returns the full tenant object for the user\'s currently active tenant.  ## Tenant Context Users can be members of multiple tenants but only one is active at a time. The active tenant determines which resources and data the user can access.  ## Use Case Determine which tenant context to use for API calls and data filtering.
+     * Get active tenant
+     */
+    apiV1AuthActiveTenantGetRaw(initOverrides) {
+        return __awaiter(this, void 0, void 0, function* () {
+            const queryParameters = {};
+            const headerParameters = {};
+            if (this.configuration && this.configuration.apiKey) {
+                headerParameters["Cookie"] = yield this.configuration.apiKey("Cookie"); // SessionAuth authentication
+            }
+            let urlPath = `/api/v1/auth/active-tenant`;
+            const response = yield this.request({
+                path: urlPath,
+                method: 'GET',
+                headers: headerParameters,
+                query: queryParameters,
+            }, initOverrides);
+            return new runtime.JSONApiResponse(response, (jsonValue) => ApiV1AuthActiveTenantGet200ResponseFromJSON(jsonValue));
+        });
+    }
+    /**
+     * Returns the full tenant object for the user\'s currently active tenant.  ## Tenant Context Users can be members of multiple tenants but only one is active at a time. The active tenant determines which resources and data the user can access.  ## Use Case Determine which tenant context to use for API calls and data filtering.
+     * Get active tenant
+     */
+    apiV1AuthActiveTenantGet(initOverrides) {
+        return __awaiter(this, void 0, void 0, function* () {
+            const response = yield this.apiV1AuthActiveTenantGetRaw(initOverrides);
+            return yield response.value();
+        });
+    }
+    /**
+     * Returns the current authenticated user\'s identity information (traits like email, name).  ## Identity Data - User ID (unique identifier) - Traits (email, first name, last name based on identity schema) - Schema ID - Created/updated timestamps  ## Use Case Lighter alternative to full session when you only need user profile data.
+     * Get current identity
+     */
+    apiV1AuthIdentityGetRaw(initOverrides) {
+        return __awaiter(this, void 0, void 0, function* () {
+            const queryParameters = {};
+            const headerParameters = {};
+            if (this.configuration && this.configuration.apiKey) {
+                headerParameters["Cookie"] = yield this.configuration.apiKey("Cookie"); // SessionAuth authentication
+            }
+            let urlPath = `/api/v1/auth/identity`;
+            const response = yield this.request({
+                path: urlPath,
+                method: 'GET',
+                headers: headerParameters,
+                query: queryParameters,
+            }, initOverrides);
+            return new runtime.JSONApiResponse(response, (jsonValue) => ApiV1AuthIdentityGet200ResponseFromJSON(jsonValue));
+        });
+    }
+    /**
+     * Returns the current authenticated user\'s identity information (traits like email, name).  ## Identity Data - User ID (unique identifier) - Traits (email, first name, last name based on identity schema) - Schema ID - Created/updated timestamps  ## Use Case Lighter alternative to full session when you only need user profile data.
+     * Get current identity
+     */
+    apiV1AuthIdentityGet(initOverrides) {
+        return __awaiter(this, void 0, void 0, function* () {
+            const response = yield this.apiV1AuthIdentityGetRaw(initOverrides);
+            return yield response.value();
+        });
+    }
+    /**
+     * Creates a Kratos logout flow and returns the logout URL for browser redirect.  ## Logout Process 1. Request this endpoint to get logout URL 2. Redirect browser to the returned logout_url 3. Session will be invalidated and user logged out  ## Cookie Cleanup The logout URL handles clearing session cookies automatically.
+     * Logout user
+     */
+    apiV1AuthLogoutPostRaw(initOverrides) {
+        return __awaiter(this, void 0, void 0, function* () {
+            const queryParameters = {};
+            const headerParameters = {};
+            if (this.configuration && this.configuration.apiKey) {
+                headerParameters["Cookie"] = yield this.configuration.apiKey("Cookie"); // SessionAuth authentication
+            }
+            let urlPath = `/api/v1/auth/logout`;
+            const response = yield this.request({
+                path: urlPath,
+                method: 'POST',
+                headers: headerParameters,
+                query: queryParameters,
+            }, initOverrides);
+            return new runtime.JSONApiResponse(response, (jsonValue) => ApiV1AuthLogoutPost200ResponseFromJSON(jsonValue));
+        });
+    }
+    /**
+     * Creates a Kratos logout flow and returns the logout URL for browser redirect.  ## Logout Process 1. Request this endpoint to get logout URL 2. Redirect browser to the returned logout_url 3. Session will be invalidated and user logged out  ## Cookie Cleanup The logout URL handles clearing session cookies automatically.
+     * Logout user
+     */
+    apiV1AuthLogoutPost(initOverrides) {
+        return __awaiter(this, void 0, void 0, function* () {
+            const response = yield this.apiV1AuthLogoutPostRaw(initOverrides);
+            return yield response.value();
+        });
+    }
+    /**
+     * Returns the current authenticated user\'s session including identity and tenant information.  ## Session Data - Session metadata (ID, expiry, authentication methods) - Identity information (user ID, traits like email, name) - Active tenant context (if user has tenant membership)  ## Authentication Requires valid session via Cookie or X-Session-Token header.
+     * Get current session
+     */
+    apiV1AuthSessionGetRaw(initOverrides) {
+        return __awaiter(this, void 0, void 0, function* () {
+            const queryParameters = {};
+            const headerParameters = {};
+            if (this.configuration && this.configuration.apiKey) {
+                headerParameters["Cookie"] = yield this.configuration.apiKey("Cookie"); // SessionAuth authentication
+            }
+            let urlPath = `/api/v1/auth/session`;
+            const response = yield this.request({
+                path: urlPath,
+                method: 'GET',
+                headers: headerParameters,
+                query: queryParameters,
+            }, initOverrides);
+            return new runtime.JSONApiResponse(response, (jsonValue) => ApiV1AuthSessionGet200ResponseFromJSON(jsonValue));
+        });
+    }
+    /**
+     * Returns the current authenticated user\'s session including identity and tenant information.  ## Session Data - Session metadata (ID, expiry, authentication methods) - Identity information (user ID, traits like email, name) - Active tenant context (if user has tenant membership)  ## Authentication Requires valid session via Cookie or X-Session-Token header.
+     * Get current session
+     */
+    apiV1AuthSessionGet(initOverrides) {
+        return __awaiter(this, void 0, void 0, function* () {
+            const response = yield this.apiV1AuthSessionGetRaw(initOverrides);
+            return yield response.value();
+        });
+    }
+    /**
+     * Lightweight endpoint to check if the user is authenticated.  ## Response Returns boolean authentication status and user ID if authenticated.  ## Use Case Quick auth checks for route guards without fetching full session data.
+     * Check authentication status
+     */
+    apiV1AuthWhoamiGetRaw(initOverrides) {
+        return __awaiter(this, void 0, void 0, function* () {
+            const queryParameters = {};
+            const headerParameters = {};
+            if (this.configuration && this.configuration.apiKey) {
+                headerParameters["Cookie"] = yield this.configuration.apiKey("Cookie"); // SessionAuth authentication
+            }
+            let urlPath = `/api/v1/auth/whoami`;
+            const response = yield this.request({
+                path: urlPath,
+                method: 'GET',
+                headers: headerParameters,
+                query: queryParameters,
+            }, initOverrides);
+            return new runtime.JSONApiResponse(response, (jsonValue) => ApiV1AuthWhoamiGet200ResponseFromJSON(jsonValue));
+        });
+    }
+    /**
+     * Lightweight endpoint to check if the user is authenticated.  ## Response Returns boolean authentication status and user ID if authenticated.  ## Use Case Quick auth checks for route guards without fetching full session data.
+     * Check authentication status
+     */
+    apiV1AuthWhoamiGet(initOverrides) {
+        return __awaiter(this, void 0, void 0, function* () {
+            const response = yield this.apiV1AuthWhoamiGetRaw(initOverrides);
+            return yield response.value();
+        });
+    }
+}

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

package/dist/esm/apis/V1DatabaseApi.js

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

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

package/dist/esm/apis/V1PaymentsApi.js

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

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

package/dist/esm/apis/V1PermissionsApi.js

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

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

package/dist/esm/apis/V1StorageApi.js

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

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

package/dist/esm/apis/V1StripeApi.js

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

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

package/dist/esm/apis/V1TenantsApi.js

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

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

@@ -1,3 +1,4 @@
+export * from './V1AuthApi';
 export * from './V1DatabaseApi';
 export * from './V1PaymentsApi';
 export * from './V1PermissionsApi';

package/dist/esm/apis/index.js

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

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

package/dist/esm/models/AcceptInvite200Response.js

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

package/dist/esm/models/ApiV1AuthActiveTenantGet200Response.d.ts

@@ -0,0 +1,39 @@
+/**
+ * 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.5
+ * 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 type { ModelsActiveTenantResponse } from './ModelsActiveTenantResponse';
+/**
+ *
+ * @export
+ * @interface ApiV1AuthActiveTenantGet200Response
+ */
+export interface ApiV1AuthActiveTenantGet200Response {
+    /**
+     *
+     * @type {ModelsActiveTenantResponse}
+     * @memberof ApiV1AuthActiveTenantGet200Response
+     */
+    data?: ModelsActiveTenantResponse;
+    /**
+     *
+     * @type {number}
+     * @memberof ApiV1AuthActiveTenantGet200Response
+     */
+    status?: number;
+}
+/**
+ * Check if a given object implements the ApiV1AuthActiveTenantGet200Response interface.
+ */
+export declare function instanceOfApiV1AuthActiveTenantGet200Response(value: object): value is ApiV1AuthActiveTenantGet200Response;
+export declare function ApiV1AuthActiveTenantGet200ResponseFromJSON(json: any): ApiV1AuthActiveTenantGet200Response;
+export declare function ApiV1AuthActiveTenantGet200ResponseFromJSONTyped(json: any, ignoreDiscriminator: boolean): ApiV1AuthActiveTenantGet200Response;
+export declare function ApiV1AuthActiveTenantGet200ResponseToJSON(json: any): ApiV1AuthActiveTenantGet200Response;
+export declare function ApiV1AuthActiveTenantGet200ResponseToJSONTyped(value?: ApiV1AuthActiveTenantGet200Response | null, ignoreDiscriminator?: boolean): any;

package/dist/esm/models/ApiV1AuthActiveTenantGet200Response.js

@@ -0,0 +1,44 @@
+/* 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.5
+ * 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 { ModelsActiveTenantResponseFromJSON, ModelsActiveTenantResponseToJSON, } from './ModelsActiveTenantResponse';
+/**
+ * Check if a given object implements the ApiV1AuthActiveTenantGet200Response interface.
+ */
+export function instanceOfApiV1AuthActiveTenantGet200Response(value) {
+    return true;
+}
+export function ApiV1AuthActiveTenantGet200ResponseFromJSON(json) {
+    return ApiV1AuthActiveTenantGet200ResponseFromJSONTyped(json, false);
+}
+export function ApiV1AuthActiveTenantGet200ResponseFromJSONTyped(json, ignoreDiscriminator) {
+    if (json == null) {
+        return json;
+    }
+    return {
+        'data': json['data'] == null ? undefined : ModelsActiveTenantResponseFromJSON(json['data']),
+        'status': json['status'] == null ? undefined : json['status'],
+    };
+}
+export function ApiV1AuthActiveTenantGet200ResponseToJSON(json) {
+    return ApiV1AuthActiveTenantGet200ResponseToJSONTyped(json, false);
+}
+export function ApiV1AuthActiveTenantGet200ResponseToJSONTyped(value, ignoreDiscriminator = false) {
+    if (value == null) {
+        return value;
+    }
+    return {
+        'data': ModelsActiveTenantResponseToJSON(value['data']),
+        'status': value['status'],
+    };
+}

package/dist/esm/models/ApiV1AuthIdentityGet200Response.d.ts

@@ -0,0 +1,38 @@
+/**
+ * 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.5
+ * 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.
+ */
+/**
+ *
+ * @export
+ * @interface ApiV1AuthIdentityGet200Response
+ */
+export interface ApiV1AuthIdentityGet200Response {
+    /**
+     *
+     * @type {object}
+     * @memberof ApiV1AuthIdentityGet200Response
+     */
+    data?: object;
+    /**
+     *
+     * @type {number}
+     * @memberof ApiV1AuthIdentityGet200Response
+     */
+    status?: number;
+}
+/**
+ * Check if a given object implements the ApiV1AuthIdentityGet200Response interface.
+ */
+export declare function instanceOfApiV1AuthIdentityGet200Response(value: object): value is ApiV1AuthIdentityGet200Response;
+export declare function ApiV1AuthIdentityGet200ResponseFromJSON(json: any): ApiV1AuthIdentityGet200Response;
+export declare function ApiV1AuthIdentityGet200ResponseFromJSONTyped(json: any, ignoreDiscriminator: boolean): ApiV1AuthIdentityGet200Response;
+export declare function ApiV1AuthIdentityGet200ResponseToJSON(json: any): ApiV1AuthIdentityGet200Response;
+export declare function ApiV1AuthIdentityGet200ResponseToJSONTyped(value?: ApiV1AuthIdentityGet200Response | null, ignoreDiscriminator?: boolean): any;

package/dist/esm/models/ApiV1AuthIdentityGet200Response.js

@@ -0,0 +1,43 @@
+/* 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.5
+ * 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.
+ */
+/**
+ * Check if a given object implements the ApiV1AuthIdentityGet200Response interface.
+ */
+export function instanceOfApiV1AuthIdentityGet200Response(value) {
+    return true;
+}
+export function ApiV1AuthIdentityGet200ResponseFromJSON(json) {
+    return ApiV1AuthIdentityGet200ResponseFromJSONTyped(json, false);
+}
+export function ApiV1AuthIdentityGet200ResponseFromJSONTyped(json, ignoreDiscriminator) {
+    if (json == null) {
+        return json;
+    }
+    return {
+        'data': json['data'] == null ? undefined : json['data'],
+        'status': json['status'] == null ? undefined : json['status'],
+    };
+}
+export function ApiV1AuthIdentityGet200ResponseToJSON(json) {
+    return ApiV1AuthIdentityGet200ResponseToJSONTyped(json, false);
+}
+export function ApiV1AuthIdentityGet200ResponseToJSONTyped(value, ignoreDiscriminator = false) {
+    if (value == null) {
+        return value;
+    }
+    return {
+        'data': value['data'],
+        'status': value['status'],
+    };
+}