@omnibase/core-js 0.9.0 → 0.9.2

package/dist/esm/apis/{DatabaseApi.js → 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.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).
@@ -25,7 +25,7 @@ import { V1MigrationSuccessResponseFromJSON, } from '../models/index';
 /**
  *
  */
-export class DatabaseApi extends runtime.BaseAPI {
+export class V1DatabaseApi extends runtime.BaseAPI {
     /**
      * Uploads SQL migration files and applies them to the user\'s PostgreSQL database.  ## Authentication Requires JWT token (typically used by CLI tools, not browser sessions).  ## Migration Format Upload a zip file containing SQL files named like: `001-seed.sql`, `002-rls.sql`, etc. Files are automatically renamed to golang-migrate format: `001_seed.up.sql`, `002_rls.up.sql`.  ## Use Cases - CLI migration uploads via `omnibase db migration push` - CI/CD pipeline integrations - Programmatic schema management
      * Upload database migrations
@@ -58,7 +58,7 @@ export class DatabaseApi extends runtime.BaseAPI {
             if (requestParameters['migrations'] != null) {
                 formParams.append('migrations', requestParameters['migrations']);
             }
-            let urlPath = `/database/migrations`;
+            let urlPath = `/api/v1/database/migrations`;
             const response = yield this.request({
                 path: urlPath,
                 method: 'POST',

package/dist/{apis/PaymentsApi.d.ts → 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.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).
@@ -23,7 +23,7 @@ export interface RecordUsageRequest {
 /**
  *
  */
-export declare class PaymentsApi extends runtime.BaseAPI {
+export declare class V1PaymentsApi extends runtime.BaseAPI {
     /**
      * Creates a Stripe Checkout Session for the specified price ID. The session URL can be used to redirect users to complete payment.  ## Authentication Requires JWT token. If the user has an existing Stripe customer ID, it will be used; otherwise, a new customer will be created.  ## Use Cases - Subscription sign-ups - One-time purchases - Trial period checkouts - Promotional code redemption
      * Create checkout session

package/dist/esm/apis/{PaymentsApi.js → 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.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).
@@ -25,7 +25,7 @@ import { CreateCheckout200ResponseFromJSON, CreateCustomerPortal200ResponseFromJ
 /**
  *
  */
-export class PaymentsApi extends runtime.BaseAPI {
+export class V1PaymentsApi extends runtime.BaseAPI {
     /**
      * Creates a Stripe Checkout Session for the specified price ID. The session URL can be used to redirect users to complete payment.  ## Authentication Requires JWT token. If the user has an existing Stripe customer ID, it will be used; otherwise, a new customer will be created.  ## Use Cases - Subscription sign-ups - One-time purchases - Trial period checkouts - Promotional code redemption
      * Create checkout session
@@ -41,7 +41,7 @@ export class PaymentsApi extends runtime.BaseAPI {
             if (this.configuration && this.configuration.apiKey) {
                 headerParameters["Authorization"] = yield this.configuration.apiKey("Authorization"); // BearerAuth authentication
             }
-            let urlPath = `/payments/checkout`;
+            let urlPath = `/api/v1/payments/checkout`;
             const response = yield this.request({
                 path: urlPath,
                 method: 'POST',
@@ -77,7 +77,7 @@ export class PaymentsApi extends runtime.BaseAPI {
             if (this.configuration && this.configuration.apiKey) {
                 headerParameters["Authorization"] = yield this.configuration.apiKey("Authorization"); // BearerAuth authentication
             }
-            let urlPath = `/payments/portal`;
+            let urlPath = `/api/v1/payments/portal`;
             const response = yield this.request({
                 path: urlPath,
                 method: 'POST',
@@ -113,7 +113,7 @@ export class PaymentsApi extends runtime.BaseAPI {
             if (this.configuration && this.configuration.apiKey) {
                 headerParameters["Authorization"] = yield this.configuration.apiKey("Authorization"); // BearerAuth authentication
             }
-            let urlPath = `/payments/usage`;
+            let urlPath = `/api/v1/payments/usage`;
             const response = yield this.request({
                 path: urlPath,
                 method: 'POST',

package/dist/{apis/PermissionsApi.d.ts → 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.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).
@@ -23,7 +23,7 @@ export interface DeployPermissionNamespacesRequest {
 /**
  *
  */
-export declare class PermissionsApi extends runtime.BaseAPI {
+export declare class V1PermissionsApi extends runtime.BaseAPI {
     /**
      * Checks if a subject has a specific permission on an object using Ory Keto.  ## Authentication Requires session authentication.  ## Request Format Provide either `subject_id` or `subject_set` (not both).  ## Use Cases - Verify user permissions before performing actions - Implement fine-grained access control - Check role-based permissions
      * Check permission

package/dist/esm/apis/{PermissionsApi.js → 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.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).
@@ -25,7 +25,7 @@ import { CheckPermission200ResponseFromJSON, CreateRelationship200ResponseFromJS
 /**
  *
  */
-export class PermissionsApi extends runtime.BaseAPI {
+export class V1PermissionsApi extends runtime.BaseAPI {
     /**
      * Checks if a subject has a specific permission on an object using Ory Keto.  ## Authentication Requires session authentication.  ## Request Format Provide either `subject_id` or `subject_set` (not both).  ## Use Cases - Verify user permissions before performing actions - Implement fine-grained access control - Check role-based permissions
      * Check permission
@@ -41,7 +41,7 @@ export class PermissionsApi extends runtime.BaseAPI {
             if (this.configuration && this.configuration.apiKey) {
                 headerParameters["Cookie"] = yield this.configuration.apiKey("Cookie"); // SessionAuth authentication
             }
-            let urlPath = `/permissions/check`;
+            let urlPath = `/api/v1/permissions/check`;
             const response = yield this.request({
                 path: urlPath,
                 method: 'POST',
@@ -77,7 +77,7 @@ export class PermissionsApi extends runtime.BaseAPI {
             if (this.configuration && this.configuration.apiKey) {
                 headerParameters["Cookie"] = yield this.configuration.apiKey("Cookie"); // SessionAuth authentication
             }
-            let urlPath = `/permissions/relationships`;
+            let urlPath = `/api/v1/permissions/relationships`;
             const response = yield this.request({
                 path: urlPath,
                 method: 'POST',
@@ -130,7 +130,7 @@ export class PermissionsApi extends runtime.BaseAPI {
             if (requestParameters['namespaces'] != null) {
                 formParams.append('namespaces', requestParameters['namespaces']);
             }
-            let urlPath = `/permissions/namespaces`;
+            let urlPath = `/api/v1/permissions/namespaces`;
             const response = yield this.request({
                 path: urlPath,
                 method: 'POST',

package/dist/{apis/StorageApi.d.ts → 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.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).
@@ -10,48 +10,48 @@
  * Do not edit the class manually.
  */
 import * as runtime from '../runtime';
-import type { ModelsDeleteObjectRequest, ModelsDownloadRequest, ModelsUploadRequest, StorageDownloadPost200Response, StorageObjectDelete200Response, StorageUploadPost200Response } from '../models/index';
-export interface StorageDownloadPostRequest {
+import type { ApiV1StorageDownloadPost200Response, ApiV1StorageObjectDelete200Response, ApiV1StorageUploadPost200Response, ModelsDeleteObjectRequest, ModelsDownloadRequest, ModelsUploadRequest } from '../models/index';
+export interface ApiV1StorageDownloadPostRequest {
     request: ModelsDownloadRequest;
 }
-export interface StorageObjectDeleteRequest {
+export interface ApiV1StorageObjectDeleteRequest {
     request: ModelsDeleteObjectRequest;
 }
-export interface StorageUploadPostRequest {
+export interface ApiV1StorageUploadPostRequest {
     request: ModelsUploadRequest;
 }
 /**
  *
  */
-export declare class StorageApi extends runtime.BaseAPI {
+export declare class V1StorageApi extends runtime.BaseAPI {
     /**
      * Generates a presigned S3 download URL with Row-Level Security (RLS) enforcement.  ## RLS Policy Download permission is checked via PostgREST against the `storage.objects` table. Users must have SELECT permission based on their custom RLS policies.  ## Download Process 1. Request presigned URL from this endpoint 2. Download file directly from S3 using returned URL (GET request)  ## URL Expiration Presigned URLs are valid for 15 minutes after generation.
      * Download file from storage
      */
-    storageDownloadPostRaw(requestParameters: StorageDownloadPostRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<StorageDownloadPost200Response>>;
+    apiV1StorageDownloadPostRaw(requestParameters: ApiV1StorageDownloadPostRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<ApiV1StorageDownloadPost200Response>>;
     /**
      * Generates a presigned S3 download URL with Row-Level Security (RLS) enforcement.  ## RLS Policy Download permission is checked via PostgREST against the `storage.objects` table. Users must have SELECT permission based on their custom RLS policies.  ## Download Process 1. Request presigned URL from this endpoint 2. Download file directly from S3 using returned URL (GET request)  ## URL Expiration Presigned URLs are valid for 15 minutes after generation.
      * Download file from storage
      */
-    storageDownloadPost(requestParameters: StorageDownloadPostRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<StorageDownloadPost200Response>;
+    apiV1StorageDownloadPost(requestParameters: ApiV1StorageDownloadPostRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<ApiV1StorageDownloadPost200Response>;
     /**
      * Deletes a file from S3 storage with Row-Level Security (RLS) enforcement.  ## RLS Policy Delete permission is checked via PostgREST against the `storage.objects` table. Users must have DELETE permission based on their custom RLS policies.  ## Deletion Process 1. Metadata is deleted from database (with RLS check) 2. File is deleted from S3 storage 3. If S3 deletion fails, metadata is already removed (eventual consistency)
      * Delete file from storage
      */
-    storageObjectDeleteRaw(requestParameters: StorageObjectDeleteRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<StorageObjectDelete200Response>>;
+    apiV1StorageObjectDeleteRaw(requestParameters: ApiV1StorageObjectDeleteRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<ApiV1StorageObjectDelete200Response>>;
     /**
      * Deletes a file from S3 storage with Row-Level Security (RLS) enforcement.  ## RLS Policy Delete permission is checked via PostgREST against the `storage.objects` table. Users must have DELETE permission based on their custom RLS policies.  ## Deletion Process 1. Metadata is deleted from database (with RLS check) 2. File is deleted from S3 storage 3. If S3 deletion fails, metadata is already removed (eventual consistency)
      * Delete file from storage
      */
-    storageObjectDelete(requestParameters: StorageObjectDeleteRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<StorageObjectDelete200Response>;
+    apiV1StorageObjectDelete(requestParameters: ApiV1StorageObjectDeleteRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<ApiV1StorageObjectDelete200Response>;
     /**
      * Generates a presigned S3 upload URL with Row-Level Security (RLS) enforcement.  ## RLS Policy Upload permission is checked via PostgREST against the `storage.objects` table. Users must have INSERT permission based on their custom RLS policies.  ## Upload Process 1. Request presigned URL from this endpoint 2. Upload file directly to S3 using returned URL (PUT request) 3. File metadata is automatically stored in database  ## URL Expiration Presigned URLs are valid for 15 minutes after generation.
      * Upload file to storage
      */
-    storageUploadPostRaw(requestParameters: StorageUploadPostRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<StorageUploadPost200Response>>;
+    apiV1StorageUploadPostRaw(requestParameters: ApiV1StorageUploadPostRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<ApiV1StorageUploadPost200Response>>;
     /**
      * Generates a presigned S3 upload URL with Row-Level Security (RLS) enforcement.  ## RLS Policy Upload permission is checked via PostgREST against the `storage.objects` table. Users must have INSERT permission based on their custom RLS policies.  ## Upload Process 1. Request presigned URL from this endpoint 2. Upload file directly to S3 using returned URL (PUT request) 3. File metadata is automatically stored in database  ## URL Expiration Presigned URLs are valid for 15 minutes after generation.
      * Upload file to storage
      */
-    storageUploadPost(requestParameters: StorageUploadPostRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<StorageUploadPost200Response>;
+    apiV1StorageUploadPost(requestParameters: ApiV1StorageUploadPostRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<ApiV1StorageUploadPost200Response>;
 }

package/dist/esm/apis/{StorageApi.js → 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.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).
@@ -21,19 +21,19 @@ var __awaiter = (this && this.__awaiter) || function (thisArg, _arguments, P, ge
     });
 };
 import * as runtime from '../runtime';
-import { ModelsDeleteObjectRequestToJSON, ModelsDownloadRequestToJSON, ModelsUploadRequestToJSON, StorageDownloadPost200ResponseFromJSON, StorageObjectDelete200ResponseFromJSON, StorageUploadPost200ResponseFromJSON, } from '../models/index';
+import { ApiV1StorageDownloadPost200ResponseFromJSON, ApiV1StorageObjectDelete200ResponseFromJSON, ApiV1StorageUploadPost200ResponseFromJSON, ModelsDeleteObjectRequestToJSON, ModelsDownloadRequestToJSON, ModelsUploadRequestToJSON, } from '../models/index';
 /**
  *
  */
-export class StorageApi extends runtime.BaseAPI {
+export class V1StorageApi extends runtime.BaseAPI {
     /**
      * Generates a presigned S3 download URL with Row-Level Security (RLS) enforcement.  ## RLS Policy Download permission is checked via PostgREST against the `storage.objects` table. Users must have SELECT permission based on their custom RLS policies.  ## Download Process 1. Request presigned URL from this endpoint 2. Download file directly from S3 using returned URL (GET request)  ## URL Expiration Presigned URLs are valid for 15 minutes after generation.
      * Download file from storage
      */
-    storageDownloadPostRaw(requestParameters, initOverrides) {
+    apiV1StorageDownloadPostRaw(requestParameters, initOverrides) {
         return __awaiter(this, void 0, void 0, function* () {
             if (requestParameters['request'] == null) {
-                throw new runtime.RequiredError('request', 'Required parameter "request" was null or undefined when calling storageDownloadPost().');
+                throw new runtime.RequiredError('request', 'Required parameter "request" was null or undefined when calling apiV1StorageDownloadPost().');
             }
             const queryParameters = {};
             const headerParameters = {};
@@ -41,7 +41,7 @@ export class StorageApi extends runtime.BaseAPI {
             if (this.configuration && this.configuration.apiKey) {
                 headerParameters["Cookie"] = yield this.configuration.apiKey("Cookie"); // SessionAuth authentication
             }
-            let urlPath = `/storage/download`;
+            let urlPath = `/api/v1/storage/download`;
             const response = yield this.request({
                 path: urlPath,
                 method: 'POST',
@@ -49,16 +49,16 @@ export class StorageApi extends runtime.BaseAPI {
                 query: queryParameters,
                 body: ModelsDownloadRequestToJSON(requestParameters['request']),
             }, initOverrides);
-            return new runtime.JSONApiResponse(response, (jsonValue) => StorageDownloadPost200ResponseFromJSON(jsonValue));
+            return new runtime.JSONApiResponse(response, (jsonValue) => ApiV1StorageDownloadPost200ResponseFromJSON(jsonValue));
         });
     }
     /**
      * Generates a presigned S3 download URL with Row-Level Security (RLS) enforcement.  ## RLS Policy Download permission is checked via PostgREST against the `storage.objects` table. Users must have SELECT permission based on their custom RLS policies.  ## Download Process 1. Request presigned URL from this endpoint 2. Download file directly from S3 using returned URL (GET request)  ## URL Expiration Presigned URLs are valid for 15 minutes after generation.
      * Download file from storage
      */
-    storageDownloadPost(requestParameters, initOverrides) {
+    apiV1StorageDownloadPost(requestParameters, initOverrides) {
         return __awaiter(this, void 0, void 0, function* () {
-            const response = yield this.storageDownloadPostRaw(requestParameters, initOverrides);
+            const response = yield this.apiV1StorageDownloadPostRaw(requestParameters, initOverrides);
             return yield response.value();
         });
     }
@@ -66,10 +66,10 @@ export class StorageApi extends runtime.BaseAPI {
      * Deletes a file from S3 storage with Row-Level Security (RLS) enforcement.  ## RLS Policy Delete permission is checked via PostgREST against the `storage.objects` table. Users must have DELETE permission based on their custom RLS policies.  ## Deletion Process 1. Metadata is deleted from database (with RLS check) 2. File is deleted from S3 storage 3. If S3 deletion fails, metadata is already removed (eventual consistency)
      * Delete file from storage
      */
-    storageObjectDeleteRaw(requestParameters, initOverrides) {
+    apiV1StorageObjectDeleteRaw(requestParameters, initOverrides) {
         return __awaiter(this, void 0, void 0, function* () {
             if (requestParameters['request'] == null) {
-                throw new runtime.RequiredError('request', 'Required parameter "request" was null or undefined when calling storageObjectDelete().');
+                throw new runtime.RequiredError('request', 'Required parameter "request" was null or undefined when calling apiV1StorageObjectDelete().');
             }
             const queryParameters = {};
             const headerParameters = {};
@@ -77,7 +77,7 @@ export class StorageApi extends runtime.BaseAPI {
             if (this.configuration && this.configuration.apiKey) {
                 headerParameters["Cookie"] = yield this.configuration.apiKey("Cookie"); // SessionAuth authentication
             }
-            let urlPath = `/storage/object`;
+            let urlPath = `/api/v1/storage/object`;
             const response = yield this.request({
                 path: urlPath,
                 method: 'DELETE',
@@ -85,16 +85,16 @@ export class StorageApi extends runtime.BaseAPI {
                 query: queryParameters,
                 body: ModelsDeleteObjectRequestToJSON(requestParameters['request']),
             }, initOverrides);
-            return new runtime.JSONApiResponse(response, (jsonValue) => StorageObjectDelete200ResponseFromJSON(jsonValue));
+            return new runtime.JSONApiResponse(response, (jsonValue) => ApiV1StorageObjectDelete200ResponseFromJSON(jsonValue));
         });
     }
     /**
      * Deletes a file from S3 storage with Row-Level Security (RLS) enforcement.  ## RLS Policy Delete permission is checked via PostgREST against the `storage.objects` table. Users must have DELETE permission based on their custom RLS policies.  ## Deletion Process 1. Metadata is deleted from database (with RLS check) 2. File is deleted from S3 storage 3. If S3 deletion fails, metadata is already removed (eventual consistency)
      * Delete file from storage
      */
-    storageObjectDelete(requestParameters, initOverrides) {
+    apiV1StorageObjectDelete(requestParameters, initOverrides) {
         return __awaiter(this, void 0, void 0, function* () {
-            const response = yield this.storageObjectDeleteRaw(requestParameters, initOverrides);
+            const response = yield this.apiV1StorageObjectDeleteRaw(requestParameters, initOverrides);
             return yield response.value();
         });
     }
@@ -102,10 +102,10 @@ export class StorageApi extends runtime.BaseAPI {
      * Generates a presigned S3 upload URL with Row-Level Security (RLS) enforcement.  ## RLS Policy Upload permission is checked via PostgREST against the `storage.objects` table. Users must have INSERT permission based on their custom RLS policies.  ## Upload Process 1. Request presigned URL from this endpoint 2. Upload file directly to S3 using returned URL (PUT request) 3. File metadata is automatically stored in database  ## URL Expiration Presigned URLs are valid for 15 minutes after generation.
      * Upload file to storage
      */
-    storageUploadPostRaw(requestParameters, initOverrides) {
+    apiV1StorageUploadPostRaw(requestParameters, initOverrides) {
         return __awaiter(this, void 0, void 0, function* () {
             if (requestParameters['request'] == null) {
-                throw new runtime.RequiredError('request', 'Required parameter "request" was null or undefined when calling storageUploadPost().');
+                throw new runtime.RequiredError('request', 'Required parameter "request" was null or undefined when calling apiV1StorageUploadPost().');
             }
             const queryParameters = {};
             const headerParameters = {};
@@ -113,7 +113,7 @@ export class StorageApi extends runtime.BaseAPI {
             if (this.configuration && this.configuration.apiKey) {
                 headerParameters["Cookie"] = yield this.configuration.apiKey("Cookie"); // SessionAuth authentication
             }
-            let urlPath = `/storage/upload`;
+            let urlPath = `/api/v1/storage/upload`;
             const response = yield this.request({
                 path: urlPath,
                 method: 'POST',
@@ -121,16 +121,16 @@ export class StorageApi extends runtime.BaseAPI {
                 query: queryParameters,
                 body: ModelsUploadRequestToJSON(requestParameters['request']),
             }, initOverrides);
-            return new runtime.JSONApiResponse(response, (jsonValue) => StorageUploadPost200ResponseFromJSON(jsonValue));
+            return new runtime.JSONApiResponse(response, (jsonValue) => ApiV1StorageUploadPost200ResponseFromJSON(jsonValue));
         });
     }
     /**
      * Generates a presigned S3 upload URL with Row-Level Security (RLS) enforcement.  ## RLS Policy Upload permission is checked via PostgREST against the `storage.objects` table. Users must have INSERT permission based on their custom RLS policies.  ## Upload Process 1. Request presigned URL from this endpoint 2. Upload file directly to S3 using returned URL (PUT request) 3. File metadata is automatically stored in database  ## URL Expiration Presigned URLs are valid for 15 minutes after generation.
      * Upload file to storage
      */
-    storageUploadPost(requestParameters, initOverrides) {
+    apiV1StorageUploadPost(requestParameters, initOverrides) {
         return __awaiter(this, void 0, void 0, function* () {
-            const response = yield this.storageUploadPostRaw(requestParameters, initOverrides);
+            const response = yield this.apiV1StorageUploadPostRaw(requestParameters, initOverrides);
             return yield response.value();
         });
     }

package/dist/{apis/StripeApi.d.ts → 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.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).
@@ -10,17 +10,17 @@
  * Do not edit the class manually.
  */
 import * as runtime from '../runtime';
-import type { HandlersSuccessResponse, StripeConfigArchiveAllPost200Response, StripeConfigGet200Response, StripeConfigHistoryGet200Response, StripeConfigPullGet200Response } from '../models/index';
-export interface StripeConfigHistoryGetRequest {
+import type { ArchiveAllStripeConfig200Response, GetStripeConfig200Response, GetStripeConfigHistory200Response, HandlersSuccessResponse, PullStripeConfig200Response } from '../models/index';
+export interface GetStripeConfigHistoryRequest {
     limit?: number;
     offset?: number;
 }
-export interface StripeConfigPostRequest {
+export interface UpdateStripeConfigRequest {
     config: {
         [key: string]: any;
     };
 }
-export interface StripeConfigValidatePostRequest {
+export interface ValidateStripeConfigRequest {
     config: {
         [key: string]: any;
     };
@@ -28,85 +28,85 @@ export interface StripeConfigValidatePostRequest {
 /**
  *
  */
-export declare class StripeApi extends runtime.BaseAPI {
-    /**
-     * Returns the complete Stripe configuration including all prices (both public and enterprise).  ## Authentication Requires admin JWT token.  ## Use Cases - Admin configuration management - Enterprise pricing display - Configuration auditing
-     * Get full Stripe config (admin)
-     */
-    stripeConfigAdminGetRaw(initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<StripeConfigGet200Response>>;
-    /**
-     * Returns the complete Stripe configuration including all prices (both public and enterprise).  ## Authentication Requires admin JWT token.  ## Use Cases - Admin configuration management - Enterprise pricing display - Configuration auditing
-     * Get full Stripe config (admin)
-     */
-    stripeConfigAdminGet(initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<StripeConfigGet200Response>;
+export declare class V1StripeApi extends runtime.BaseAPI {
     /**
      * Archives all active products, prices, and meters in Stripe and clears the local configuration.  ## Authentication Requires admin JWT token.  ## Warning This is a destructive operation that will archive ALL active Stripe resources.  ## Use Cases - Clean slate for new configuration - Remove all test data - Reset Stripe account
      * Archive all Stripe config
      */
-    stripeConfigArchiveAllPostRaw(initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<StripeConfigArchiveAllPost200Response>>;
+    archiveAllStripeConfigRaw(initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<ArchiveAllStripeConfig200Response>>;
     /**
      * Archives all active products, prices, and meters in Stripe and clears the local configuration.  ## Authentication Requires admin JWT token.  ## Warning This is a destructive operation that will archive ALL active Stripe resources.  ## Use Cases - Clean slate for new configuration - Remove all test data - Reset Stripe account
      * Archive all Stripe config
      */
-    stripeConfigArchiveAllPost(initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<StripeConfigArchiveAllPost200Response>;
+    archiveAllStripeConfig(initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<ArchiveAllStripeConfig200Response>;
     /**
      * Returns the current Stripe configuration with public prices only (filters out enterprise prices).  ## Authentication No authentication required for public endpoint.  ## Use Cases - Display pricing to users - Build subscription selection UI - Public pricing pages
      * Get public Stripe config
      */
-    stripeConfigGetRaw(initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<StripeConfigGet200Response>>;
+    getStripeConfigRaw(initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<GetStripeConfig200Response>>;
     /**
      * Returns the current Stripe configuration with public prices only (filters out enterprise prices).  ## Authentication No authentication required for public endpoint.  ## Use Cases - Display pricing to users - Build subscription selection UI - Public pricing pages
      * Get public Stripe config
      */
-    stripeConfigGet(initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<StripeConfigGet200Response>;
+    getStripeConfig(initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<GetStripeConfig200Response>;
+    /**
+     * Returns the complete Stripe configuration including all prices (both public and enterprise).  ## Authentication Requires admin JWT token.  ## Use Cases - Admin configuration management - Enterprise pricing display - Configuration auditing
+     * Get full Stripe config (admin)
+     */
+    getStripeConfigAdminRaw(initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<GetStripeConfig200Response>>;
+    /**
+     * Returns the complete Stripe configuration including all prices (both public and enterprise).  ## Authentication Requires admin JWT token.  ## Use Cases - Admin configuration management - Enterprise pricing display - Configuration auditing
+     * Get full Stripe config (admin)
+     */
+    getStripeConfigAdmin(initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<GetStripeConfig200Response>;
     /**
      * Returns paginated history of all Stripe configurations.  ## Authentication Requires admin JWT token.  ## Query Parameters - limit: Items per page (default: 10, max: 100) - offset: Number of items to skip (default: 0)
      * Get config history
      */
-    stripeConfigHistoryGetRaw(requestParameters: StripeConfigHistoryGetRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<StripeConfigHistoryGet200Response>>;
+    getStripeConfigHistoryRaw(requestParameters: GetStripeConfigHistoryRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<GetStripeConfigHistory200Response>>;
     /**
      * Returns paginated history of all Stripe configurations.  ## Authentication Requires admin JWT token.  ## Query Parameters - limit: Items per page (default: 10, max: 100) - offset: Number of items to skip (default: 0)
      * Get config history
      */
-    stripeConfigHistoryGet(requestParameters?: StripeConfigHistoryGetRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<StripeConfigHistoryGet200Response>;
+    getStripeConfigHistory(requestParameters?: GetStripeConfigHistoryRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<GetStripeConfigHistory200Response>;
     /**
-     * Updates the Stripe configuration and syncs with Stripe API to create/update products, prices, and meters.  ## Authentication Requires admin JWT token.  ## Use Cases - Deploy new pricing - Update product definitions - Modify metered billing settings
-     * Update Stripe config
+     * Returns the JSON schema definition for validating Stripe configuration files.  ## Use Cases - Validate configuration before upload - IDE autocomplete support - Generate configuration templates
+     * Get Stripe config schema
      */
-    stripeConfigPostRaw(requestParameters: StripeConfigPostRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<HandlersSuccessResponse>>;
+    getStripeConfigSchemaRaw(initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<object>>;
     /**
-     * Updates the Stripe configuration and syncs with Stripe API to create/update products, prices, and meters.  ## Authentication Requires admin JWT token.  ## Use Cases - Deploy new pricing - Update product definitions - Modify metered billing settings
-     * Update Stripe config
+     * Returns the JSON schema definition for validating Stripe configuration files.  ## Use Cases - Validate configuration before upload - IDE autocomplete support - Generate configuration templates
+     * Get Stripe config schema
      */
-    stripeConfigPost(requestParameters: StripeConfigPostRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<HandlersSuccessResponse>;
+    getStripeConfigSchema(initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<object>;
     /**
      * Fetches all active products, prices, and meters from Stripe API and converts them to the local configuration format.  ## Authentication Requires admin JWT token.  ## Use Cases - Sync remote Stripe config to local - Import existing Stripe setup - Configuration backup
      * Pull config from Stripe
      */
-    stripeConfigPullGetRaw(initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<StripeConfigPullGet200Response>>;
+    pullStripeConfigRaw(initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<PullStripeConfig200Response>>;
     /**
      * Fetches all active products, prices, and meters from Stripe API and converts them to the local configuration format.  ## Authentication Requires admin JWT token.  ## Use Cases - Sync remote Stripe config to local - Import existing Stripe setup - Configuration backup
      * Pull config from Stripe
      */
-    stripeConfigPullGet(initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<StripeConfigPullGet200Response>;
+    pullStripeConfig(initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<PullStripeConfig200Response>;
     /**
-     * Validates a Stripe configuration against the schema without saving or deploying it.  ## Authentication Requires admin JWT token.  ## Use Cases - Pre-deployment validation - Configuration testing - Schema compliance checking
-     * Validate Stripe config
+     * Updates the Stripe configuration and syncs with Stripe API to create/update products, prices, and meters.  ## Authentication Requires admin JWT token.  ## Use Cases - Deploy new pricing - Update product definitions - Modify metered billing settings
+     * Update Stripe config
      */
-    stripeConfigValidatePostRaw(requestParameters: StripeConfigValidatePostRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<HandlersSuccessResponse>>;
+    updateStripeConfigRaw(requestParameters: UpdateStripeConfigRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<HandlersSuccessResponse>>;
     /**
-     * Validates a Stripe configuration against the schema without saving or deploying it.  ## Authentication Requires admin JWT token.  ## Use Cases - Pre-deployment validation - Configuration testing - Schema compliance checking
-     * Validate Stripe config
+     * Updates the Stripe configuration and syncs with Stripe API to create/update products, prices, and meters.  ## Authentication Requires admin JWT token.  ## Use Cases - Deploy new pricing - Update product definitions - Modify metered billing settings
+     * Update Stripe config
      */
-    stripeConfigValidatePost(requestParameters: StripeConfigValidatePostRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<HandlersSuccessResponse>;
+    updateStripeConfig(requestParameters: UpdateStripeConfigRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<HandlersSuccessResponse>;
     /**
-     * Returns the JSON schema definition for validating Stripe configuration files.  ## Use Cases - Validate configuration before upload - IDE autocomplete support - Generate configuration templates
-     * Get Stripe config schema
+     * Validates a Stripe configuration against the schema without saving or deploying it.  ## Authentication Requires admin JWT token.  ## Use Cases - Pre-deployment validation - Configuration testing - Schema compliance checking
+     * Validate Stripe config
      */
-    stripeSchemaGetRaw(initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<object>>;
+    validateStripeConfigRaw(requestParameters: ValidateStripeConfigRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<HandlersSuccessResponse>>;
     /**
-     * Returns the JSON schema definition for validating Stripe configuration files.  ## Use Cases - Validate configuration before upload - IDE autocomplete support - Generate configuration templates
-     * Get Stripe config schema
+     * Validates a Stripe configuration against the schema without saving or deploying it.  ## Authentication Requires admin JWT token.  ## Use Cases - Pre-deployment validation - Configuration testing - Schema compliance checking
+     * Validate Stripe config
      */
-    stripeSchemaGet(initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<object>;
+    validateStripeConfig(requestParameters: ValidateStripeConfigRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<HandlersSuccessResponse>;
 }