@omnibase/core-js 0.9.3 → 0.9.5

package/docs/ModelsWhoAmIResponse.md

@@ -0,0 +1,36 @@
+
+# ModelsWhoAmIResponse
+
+
+## Properties
+
+Name | Type
+------------ | -------------
+`authenticated` | boolean
+`userId` | string
+
+## Example
+
+```typescript
+import type { ModelsWhoAmIResponse } from '@omnibase/core-js'
+
+// TODO: Update the object below with actual values
+const example = {
+  "authenticated": true,
+  "userId": 550e8400-e29b-41d4-a716-446655440000,
+} satisfies ModelsWhoAmIResponse
+
+console.log(example)
+
+// Convert the instance to a JSON string
+const exampleJSON: string = JSON.stringify(example)
+console.log(exampleJSON)
+
+// Parse the JSON string back to an object
+const exampleParsed = JSON.parse(exampleJSON) as ModelsWhoAmIResponse
+console.log(exampleParsed)
+```
+
+[[Back to top]](#) [[Back to API list]](../README.md#api-endpoints) [[Back to Model list]](../README.md#models) [[Back to README]](../README.md)
+
+

package/docs/V1AuthApi.md

@@ -0,0 +1,334 @@
+# V1AuthApi
+
+All URIs are relative to *http://https://api.omnibase.tech*
+
+| Method | HTTP request | Description |
+|------------- | ------------- | -------------|
+| [**apiV1AuthActiveTenantGet**](V1AuthApi.md#apiv1authactivetenantget) | **GET** /api/v1/auth/active-tenant | Get active tenant |
+| [**apiV1AuthIdentityGet**](V1AuthApi.md#apiv1authidentityget) | **GET** /api/v1/auth/identity | Get current identity |
+| [**apiV1AuthLogoutPost**](V1AuthApi.md#apiv1authlogoutpost) | **POST** /api/v1/auth/logout | Logout user |
+| [**apiV1AuthSessionGet**](V1AuthApi.md#apiv1authsessionget) | **GET** /api/v1/auth/session | Get current session |
+| [**apiV1AuthWhoamiGet**](V1AuthApi.md#apiv1authwhoamiget) | **GET** /api/v1/auth/whoami | Check authentication status |
+
+
+
+## apiV1AuthActiveTenantGet
+
+> ApiV1AuthActiveTenantGet200Response apiV1AuthActiveTenantGet()
+
+Get active tenant
+
+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.
+
+### Example
+
+```ts
+import {
+  Configuration,
+  V1AuthApi,
+} from '@omnibase/core-js';
+import type { ApiV1AuthActiveTenantGetRequest } from '@omnibase/core-js';
+
+async function example() {
+  console.log("🚀 Testing @omnibase/core-js SDK...");
+  const config = new Configuration({ 
+    // To configure API key authorization: SessionAuth
+    apiKey: "YOUR API KEY",
+  });
+  const api = new V1AuthApi(config);
+
+  try {
+    const data = await api.apiV1AuthActiveTenantGet();
+    console.log(data);
+  } catch (error) {
+    console.error(error);
+  }
+}
+
+// Run the test
+example().catch(console.error);
+```
+
+### Parameters
+
+This endpoint does not need any parameter.
+
+### Return type
+
+[**ApiV1AuthActiveTenantGet200Response**](ApiV1AuthActiveTenantGet200Response.md)
+
+### Authorization
+
+[SessionAuth](../README.md#SessionAuth)
+
+### HTTP request headers
+
+- **Content-Type**: Not defined
+- **Accept**: `application/json`
+
+
+### HTTP response details
+| Status code | Description | Response headers |
+|-------------|-------------|------------------|
+| **200** | Active tenant retrieved |  -  |
+| **401** | Not authenticated |  -  |
+
+[[Back to top]](#) [[Back to API list]](../README.md#api-endpoints) [[Back to Model list]](../README.md#models) [[Back to README]](../README.md)
+
+
+## apiV1AuthIdentityGet
+
+> ApiV1AuthIdentityGet200Response apiV1AuthIdentityGet()
+
+Get current identity
+
+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.
+
+### Example
+
+```ts
+import {
+  Configuration,
+  V1AuthApi,
+} from '@omnibase/core-js';
+import type { ApiV1AuthIdentityGetRequest } from '@omnibase/core-js';
+
+async function example() {
+  console.log("🚀 Testing @omnibase/core-js SDK...");
+  const config = new Configuration({ 
+    // To configure API key authorization: SessionAuth
+    apiKey: "YOUR API KEY",
+  });
+  const api = new V1AuthApi(config);
+
+  try {
+    const data = await api.apiV1AuthIdentityGet();
+    console.log(data);
+  } catch (error) {
+    console.error(error);
+  }
+}
+
+// Run the test
+example().catch(console.error);
+```
+
+### Parameters
+
+This endpoint does not need any parameter.
+
+### Return type
+
+[**ApiV1AuthIdentityGet200Response**](ApiV1AuthIdentityGet200Response.md)
+
+### Authorization
+
+[SessionAuth](../README.md#SessionAuth)
+
+### HTTP request headers
+
+- **Content-Type**: Not defined
+- **Accept**: `application/json`
+
+
+### HTTP response details
+| Status code | Description | Response headers |
+|-------------|-------------|------------------|
+| **200** | Identity retrieved successfully |  -  |
+| **401** | Not authenticated or session expired |  -  |
+
+[[Back to top]](#) [[Back to API list]](../README.md#api-endpoints) [[Back to Model list]](../README.md#models) [[Back to README]](../README.md)
+
+
+## apiV1AuthLogoutPost
+
+> ApiV1AuthLogoutPost200Response apiV1AuthLogoutPost()
+
+Logout user
+
+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.
+
+### Example
+
+```ts
+import {
+  Configuration,
+  V1AuthApi,
+} from '@omnibase/core-js';
+import type { ApiV1AuthLogoutPostRequest } from '@omnibase/core-js';
+
+async function example() {
+  console.log("🚀 Testing @omnibase/core-js SDK...");
+  const config = new Configuration({ 
+    // To configure API key authorization: SessionAuth
+    apiKey: "YOUR API KEY",
+  });
+  const api = new V1AuthApi(config);
+
+  try {
+    const data = await api.apiV1AuthLogoutPost();
+    console.log(data);
+  } catch (error) {
+    console.error(error);
+  }
+}
+
+// Run the test
+example().catch(console.error);
+```
+
+### Parameters
+
+This endpoint does not need any parameter.
+
+### Return type
+
+[**ApiV1AuthLogoutPost200Response**](ApiV1AuthLogoutPost200Response.md)
+
+### Authorization
+
+[SessionAuth](../README.md#SessionAuth)
+
+### HTTP request headers
+
+- **Content-Type**: Not defined
+- **Accept**: `application/json`
+
+
+### HTTP response details
+| Status code | Description | Response headers |
+|-------------|-------------|------------------|
+| **200** | Logout flow created successfully |  -  |
+| **401** | Not authenticated |  -  |
+| **500** | Failed to create logout flow |  -  |
+
+[[Back to top]](#) [[Back to API list]](../README.md#api-endpoints) [[Back to Model list]](../README.md#models) [[Back to README]](../README.md)
+
+
+## apiV1AuthSessionGet
+
+> ApiV1AuthSessionGet200Response apiV1AuthSessionGet()
+
+Get current session
+
+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.
+
+### Example
+
+```ts
+import {
+  Configuration,
+  V1AuthApi,
+} from '@omnibase/core-js';
+import type { ApiV1AuthSessionGetRequest } from '@omnibase/core-js';
+
+async function example() {
+  console.log("🚀 Testing @omnibase/core-js SDK...");
+  const config = new Configuration({ 
+    // To configure API key authorization: SessionAuth
+    apiKey: "YOUR API KEY",
+  });
+  const api = new V1AuthApi(config);
+
+  try {
+    const data = await api.apiV1AuthSessionGet();
+    console.log(data);
+  } catch (error) {
+    console.error(error);
+  }
+}
+
+// Run the test
+example().catch(console.error);
+```
+
+### Parameters
+
+This endpoint does not need any parameter.
+
+### Return type
+
+[**ApiV1AuthSessionGet200Response**](ApiV1AuthSessionGet200Response.md)
+
+### Authorization
+
+[SessionAuth](../README.md#SessionAuth)
+
+### HTTP request headers
+
+- **Content-Type**: Not defined
+- **Accept**: `application/json`
+
+
+### HTTP response details
+| Status code | Description | Response headers |
+|-------------|-------------|------------------|
+| **200** | Session retrieved successfully |  -  |
+| **401** | Not authenticated or session expired |  -  |
+
+[[Back to top]](#) [[Back to API list]](../README.md#api-endpoints) [[Back to Model list]](../README.md#models) [[Back to README]](../README.md)
+
+
+## apiV1AuthWhoamiGet
+
+> ApiV1AuthWhoamiGet200Response apiV1AuthWhoamiGet()
+
+Check authentication status
+
+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.
+
+### Example
+
+```ts
+import {
+  Configuration,
+  V1AuthApi,
+} from '@omnibase/core-js';
+import type { ApiV1AuthWhoamiGetRequest } from '@omnibase/core-js';
+
+async function example() {
+  console.log("🚀 Testing @omnibase/core-js SDK...");
+  const config = new Configuration({ 
+    // To configure API key authorization: SessionAuth
+    apiKey: "YOUR API KEY",
+  });
+  const api = new V1AuthApi(config);
+
+  try {
+    const data = await api.apiV1AuthWhoamiGet();
+    console.log(data);
+  } catch (error) {
+    console.error(error);
+  }
+}
+
+// Run the test
+example().catch(console.error);
+```
+
+### Parameters
+
+This endpoint does not need any parameter.
+
+### Return type
+
+[**ApiV1AuthWhoamiGet200Response**](ApiV1AuthWhoamiGet200Response.md)
+
+### Authorization
+
+[SessionAuth](../README.md#SessionAuth)
+
+### HTTP request headers
+
+- **Content-Type**: Not defined
+- **Accept**: `application/json`
+
+
+### HTTP response details
+| Status code | Description | Response headers |
+|-------------|-------------|------------------|
+| **200** | Authentication status checked |  -  |
+| **401** | Not authenticated |  -  |
+
+[[Back to top]](#) [[Back to API list]](../README.md#api-endpoints) [[Back to Model list]](../README.md#models) [[Back to README]](../README.md)
+

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@omnibase/core-js",
-  "version": "0.9.3",
+  "version": "0.9.5",
   "description": "OpenAPI client for @omnibase/core-js",
   "author": "OpenAPI-Generator",
   "repository": {

package/src/apis/V1AuthApi.ts

@@ -0,0 +1,223 @@
+/* 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 * as runtime from '../runtime';
+import type {
+  ApiV1AuthActiveTenantGet200Response,
+  ApiV1AuthIdentityGet200Response,
+  ApiV1AuthLogoutPost200Response,
+  ApiV1AuthSessionGet200Response,
+  ApiV1AuthWhoamiGet200Response,
+  HandlersInternalServerErrorResponse,
+  HandlersUnauthorizedResponse,
+} from '../models/index';
+import {
+    ApiV1AuthActiveTenantGet200ResponseFromJSON,
+    ApiV1AuthActiveTenantGet200ResponseToJSON,
+    ApiV1AuthIdentityGet200ResponseFromJSON,
+    ApiV1AuthIdentityGet200ResponseToJSON,
+    ApiV1AuthLogoutPost200ResponseFromJSON,
+    ApiV1AuthLogoutPost200ResponseToJSON,
+    ApiV1AuthSessionGet200ResponseFromJSON,
+    ApiV1AuthSessionGet200ResponseToJSON,
+    ApiV1AuthWhoamiGet200ResponseFromJSON,
+    ApiV1AuthWhoamiGet200ResponseToJSON,
+    HandlersInternalServerErrorResponseFromJSON,
+    HandlersInternalServerErrorResponseToJSON,
+    HandlersUnauthorizedResponseFromJSON,
+    HandlersUnauthorizedResponseToJSON,
+} 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
+     */
+    async apiV1AuthActiveTenantGetRaw(initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<ApiV1AuthActiveTenantGet200Response>> {
+        const queryParameters: any = {};
+
+        const headerParameters: runtime.HTTPHeaders = {};
+
+        if (this.configuration && this.configuration.apiKey) {
+            headerParameters["Cookie"] = await this.configuration.apiKey("Cookie"); // SessionAuth authentication
+        }
+
+
+        let urlPath = `/api/v1/auth/active-tenant`;
+
+        const response = await 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
+     */
+    async apiV1AuthActiveTenantGet(initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<ApiV1AuthActiveTenantGet200Response> {
+        const response = await this.apiV1AuthActiveTenantGetRaw(initOverrides);
+        return await 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
+     */
+    async apiV1AuthIdentityGetRaw(initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<ApiV1AuthIdentityGet200Response>> {
+        const queryParameters: any = {};
+
+        const headerParameters: runtime.HTTPHeaders = {};
+
+        if (this.configuration && this.configuration.apiKey) {
+            headerParameters["Cookie"] = await this.configuration.apiKey("Cookie"); // SessionAuth authentication
+        }
+
+
+        let urlPath = `/api/v1/auth/identity`;
+
+        const response = await 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
+     */
+    async apiV1AuthIdentityGet(initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<ApiV1AuthIdentityGet200Response> {
+        const response = await this.apiV1AuthIdentityGetRaw(initOverrides);
+        return await 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
+     */
+    async apiV1AuthLogoutPostRaw(initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<ApiV1AuthLogoutPost200Response>> {
+        const queryParameters: any = {};
+
+        const headerParameters: runtime.HTTPHeaders = {};
+
+        if (this.configuration && this.configuration.apiKey) {
+            headerParameters["Cookie"] = await this.configuration.apiKey("Cookie"); // SessionAuth authentication
+        }
+
+
+        let urlPath = `/api/v1/auth/logout`;
+
+        const response = await 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
+     */
+    async apiV1AuthLogoutPost(initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<ApiV1AuthLogoutPost200Response> {
+        const response = await this.apiV1AuthLogoutPostRaw(initOverrides);
+        return await 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
+     */
+    async apiV1AuthSessionGetRaw(initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<ApiV1AuthSessionGet200Response>> {
+        const queryParameters: any = {};
+
+        const headerParameters: runtime.HTTPHeaders = {};
+
+        if (this.configuration && this.configuration.apiKey) {
+            headerParameters["Cookie"] = await this.configuration.apiKey("Cookie"); // SessionAuth authentication
+        }
+
+
+        let urlPath = `/api/v1/auth/session`;
+
+        const response = await 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
+     */
+    async apiV1AuthSessionGet(initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<ApiV1AuthSessionGet200Response> {
+        const response = await this.apiV1AuthSessionGetRaw(initOverrides);
+        return await 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
+     */
+    async apiV1AuthWhoamiGetRaw(initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<ApiV1AuthWhoamiGet200Response>> {
+        const queryParameters: any = {};
+
+        const headerParameters: runtime.HTTPHeaders = {};
+
+        if (this.configuration && this.configuration.apiKey) {
+            headerParameters["Cookie"] = await this.configuration.apiKey("Cookie"); // SessionAuth authentication
+        }
+
+
+        let urlPath = `/api/v1/auth/whoami`;
+
+        const response = await 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
+     */
+    async apiV1AuthWhoamiGet(initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<ApiV1AuthWhoamiGet200Response> {
+        const response = await this.apiV1AuthWhoamiGetRaw(initOverrides);
+        return await response.value();
+    }
+
+}

package/src/apis/V1DatabaseApi.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.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/src/apis/V1PaymentsApi.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.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/src/apis/V1PermissionsApi.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.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/src/apis/V1StorageApi.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.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/src/apis/V1StripeApi.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.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/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.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/src/apis/index.ts

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

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.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).