npm - @omnibase/core-js - Versions diffs - 0.9.1 → 0.9.3 - Mend

@omnibase/core-js 0.9.1 → 0.9.3

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (596) hide show

package/.openapi-generator/FILES CHANGED Viewed

@@ -1,7 +1,11 @@
 .gitignore
 .npmignore
+.openapi-generator-ignore
 README.md
 docs/AcceptInvite200Response.md
+docs/ApiV1StorageDownloadPost200Response.md
+docs/ApiV1StorageObjectDelete200Response.md
+docs/ApiV1StorageUploadPost200Response.md
 docs/ArchiveAllStripeConfig200Response.md
 docs/AssignRole200Response.md
 docs/CheckPermission200Response.md
@@ -13,7 +17,6 @@ docs/CreateInvite200Response.md
 docs/CreateRelationship200Response.md
 docs/CreateRole200Response.md
 docs/CreateTenant200Response.md
-docs/DatabaseApi.md
 docs/DeleteRole200Response.md
 docs/DeleteTenant200Response.md
 docs/DeployPermissionNamespaces200Response.md
@@ -60,18 +63,10 @@ docs/ModelsTenantSettings.md
 docs/ModelsTier.md
 docs/ModelsUploadRequest.md
 docs/ModelsUploadResponse.md
-docs/PaymentsApi.md
-docs/PermissionsApi.md
 docs/PullStripeConfig200Response.md
-docs/StorageApi.md
-docs/StorageDownloadPost200Response.md
-docs/StorageObjectDelete200Response.md
-docs/StorageUploadPost200Response.md
-docs/StripeApi.md
 docs/SwitchActiveTenant200Response.md
 docs/TenantsAcceptInviteRequest.md
 docs/TenantsAcceptInviteResponse.md
-docs/TenantsApi.md
 docs/TenantsAssignRoleRequest.md
 docs/TenantsAssignRoleResponse.md
 docs/TenantsCreateRoleRequest.md
@@ -104,22 +99,31 @@ docs/V1CreatePortalRequest.md
 docs/V1CreatePortalResponse.md
 docs/V1CreateRelationshipRequest.md
 docs/V1CreateRelationshipResponse.md
+docs/V1DatabaseApi.md
 docs/V1MigrationErrorResponse.md
 docs/V1MigrationSuccessResponse.md
 docs/V1NamespaceDeploymentResponse.md
+docs/V1PaymentsApi.md
+docs/V1PermissionsApi.md
 docs/V1RecordUsageRequest.md
+docs/V1StorageApi.md
+docs/V1StripeApi.md
 docs/V1StripeConfigResponse.md
 docs/V1SubjectSetRequest.md
+docs/V1TenantsApi.md
 package.json
-src/apis/DatabaseApi.ts
-src/apis/PaymentsApi.ts
-src/apis/PermissionsApi.ts
-src/apis/StorageApi.ts
-src/apis/StripeApi.ts
-src/apis/TenantsApi.ts
+src/apis/V1DatabaseApi.ts
+src/apis/V1PaymentsApi.ts
+src/apis/V1PermissionsApi.ts
+src/apis/V1StorageApi.ts
+src/apis/V1StripeApi.ts
+src/apis/V1TenantsApi.ts
 src/apis/index.ts
 src/index.ts
 src/models/AcceptInvite200Response.ts
+src/models/ApiV1StorageDownloadPost200Response.ts
+src/models/ApiV1StorageObjectDelete200Response.ts
+src/models/ApiV1StorageUploadPost200Response.ts
 src/models/ArchiveAllStripeConfig200Response.ts
 src/models/AssignRole200Response.ts
 src/models/CheckPermission200Response.ts
@@ -178,9 +182,6 @@ src/models/ModelsTier.ts
 src/models/ModelsUploadRequest.ts
 src/models/ModelsUploadResponse.ts
 src/models/PullStripeConfig200Response.ts
-src/models/StorageDownloadPost200Response.ts
-src/models/StorageObjectDelete200Response.ts
-src/models/StorageUploadPost200Response.ts
 src/models/SwitchActiveTenant200Response.ts
 src/models/TenantsAcceptInviteRequest.ts
 src/models/TenantsAcceptInviteResponse.ts

package/README.md CHANGED Viewed

@@ -1,4 +1,4 @@
-# @omnibase/core-js@0.9.1
+# @omnibase/core-js@0.9.3
 A TypeScript SDK client for the https API.
@@ -16,7 +16,7 @@ Next, try it out.
 ```ts
 import {
   Configuration,
-  DatabaseApi,
+  V1DatabaseApi,
 } from '@omnibase/core-js';
 import type { UploadDatabaseMigrationsRequest } from '@omnibase/core-js';
@@ -26,7 +26,7 @@ async function example() {
     // To configure API key authorization: BearerAuth
     apiKey: "YOUR API KEY",
   });
-  const api = new DatabaseApi(config);
+  const api = new V1DatabaseApi(config);
   const body = {
     // Blob | Zip file containing SQL migration files
@@ -50,50 +50,53 @@ example().catch(console.error);
 ### API Endpoints
-All URIs are relative to *http://https://api.omnibase.tech/api/v1*
+All URIs are relative to *http://https://api.omnibase.tech*
 | Class | Method | HTTP request | Description
 | ----- | ------ | ------------ | -------------
-*DatabaseApi* | [**uploadDatabaseMigrations**](docs/DatabaseApi.md#uploaddatabasemigrations) | **POST** /database/migrations | Upload database migrations
-*PaymentsApi* | [**createCheckout**](docs/PaymentsApi.md#createcheckout) | **POST** /payments/checkout | Create checkout session
-*PaymentsApi* | [**createCustomerPortal**](docs/PaymentsApi.md#createcustomerportal) | **POST** /payments/portal | Create customer portal session
-*PaymentsApi* | [**recordUsage**](docs/PaymentsApi.md#recordusage) | **POST** /payments/usage | Record metered usage
-*PermissionsApi* | [**checkPermission**](docs/PermissionsApi.md#checkpermission) | **POST** /permissions/check | Check permission
-*PermissionsApi* | [**createRelationship**](docs/PermissionsApi.md#createrelationship) | **POST** /permissions/relationships | Create relationship
-*PermissionsApi* | [**deployPermissionNamespaces**](docs/PermissionsApi.md#deploypermissionnamespaces) | **POST** /permissions/namespaces | Deploy Keto namespace configurations
-*StorageApi* | [**storageDownloadPost**](docs/StorageApi.md#storagedownloadpost) | **POST** /storage/download | Download file from storage
-*StorageApi* | [**storageObjectDelete**](docs/StorageApi.md#storageobjectdelete) | **DELETE** /storage/object | Delete file from storage
-*StorageApi* | [**storageUploadPost**](docs/StorageApi.md#storageuploadpost) | **POST** /storage/upload | Upload file to storage
-*StripeApi* | [**archiveAllStripeConfig**](docs/StripeApi.md#archiveallstripeconfig) | **POST** /stripe/config/archive-all | Archive all Stripe config
-*StripeApi* | [**getStripeConfig**](docs/StripeApi.md#getstripeconfig) | **GET** /stripe/config | Get public Stripe config
-*StripeApi* | [**getStripeConfigAdmin**](docs/StripeApi.md#getstripeconfigadmin) | **GET** /stripe/config/admin | Get full Stripe config (admin)
-*StripeApi* | [**getStripeConfigHistory**](docs/StripeApi.md#getstripeconfighistory) | **GET** /stripe/config/history | Get config history
-*StripeApi* | [**getStripeConfigSchema**](docs/StripeApi.md#getstripeconfigschema) | **GET** /stripe/schema | Get Stripe config schema
-*StripeApi* | [**pullStripeConfig**](docs/StripeApi.md#pullstripeconfig) | **GET** /stripe/config/pull | Pull config from Stripe
-*StripeApi* | [**updateStripeConfig**](docs/StripeApi.md#updatestripeconfig) | **POST** /stripe/config | Update Stripe config
-*StripeApi* | [**validateStripeConfig**](docs/StripeApi.md#validatestripeconfig) | **POST** /stripe/config/validate | Validate Stripe config
-*TenantsApi* | [**acceptInvite**](docs/TenantsApi.md#acceptinvite) | **PUT** /tenants/invites/accept | Accept tenant invite
-*TenantsApi* | [**assignRole**](docs/TenantsApi.md#assignrole) | **POST** /tenants/roles/assign/{user_id} | Assign role to user
-*TenantsApi* | [**createInvite**](docs/TenantsApi.md#createinvite) | **POST** /tenants/invites | Create tenant invite
-*TenantsApi* | [**createRole**](docs/TenantsApi.md#createrole) | **POST** /tenants/roles | Create role
-*TenantsApi* | [**createTenant**](docs/TenantsApi.md#createtenant) | **POST** /tenants | Create tenant
-*TenantsApi* | [**deleteRole**](docs/TenantsApi.md#deleterole) | **DELETE** /tenants/roles/{role_id} | Delete role
-*TenantsApi* | [**deleteTenant**](docs/TenantsApi.md#deletetenant) | **DELETE** /tenants | Delete tenant
-*TenantsApi* | [**getRoleDefinitions**](docs/TenantsApi.md#getroledefinitions) | **GET** /tenants/roles/definitions | Get namespace definitions
-*TenantsApi* | [**getTenantBillingStatus**](docs/TenantsApi.md#gettenantbillingstatus) | **GET** /tenants/billing-status | Get billing status
-*TenantsApi* | [**getTenantJWT**](docs/TenantsApi.md#gettenantjwt) | **GET** /tenants/jwt | Get PostgREST JWT token
-*TenantsApi* | [**listRoles**](docs/TenantsApi.md#listroles) | **GET** /tenants/roles | List roles
-*TenantsApi* | [**listTenantSubscriptions**](docs/TenantsApi.md#listtenantsubscriptions) | **GET** /tenants/subscriptions | Get tenant subscriptions
-*TenantsApi* | [**listTenantUsers**](docs/TenantsApi.md#listtenantusers) | **GET** /tenants/users | Get tenant users
-*TenantsApi* | [**removeTenantUser**](docs/TenantsApi.md#removetenantuser) | **DELETE** /tenants/users | Remove tenant user
-*TenantsApi* | [**switchActiveTenant**](docs/TenantsApi.md#switchactivetenant) | **PUT** /tenants/switch-active | Switch active tenant
-*TenantsApi* | [**updateRole**](docs/TenantsApi.md#updaterole) | **PUT** /tenants/roles/{role_id} | Update role
-*TenantsApi* | [**updateTenantUserRole**](docs/TenantsApi.md#updatetenantuserrole) | **PUT** /tenants/users/role | Update user role
+*V1DatabaseApi* | [**uploadDatabaseMigrations**](docs/V1DatabaseApi.md#uploaddatabasemigrations) | **POST** /api/v1/database/migrations | Upload database migrations
+*V1PaymentsApi* | [**createCheckout**](docs/V1PaymentsApi.md#createcheckout) | **POST** /api/v1/payments/checkout | Create checkout session
+*V1PaymentsApi* | [**createCustomerPortal**](docs/V1PaymentsApi.md#createcustomerportal) | **POST** /api/v1/payments/portal | Create customer portal session
+*V1PaymentsApi* | [**recordUsage**](docs/V1PaymentsApi.md#recordusage) | **POST** /api/v1/payments/usage | Record metered usage
+*V1PermissionsApi* | [**checkPermission**](docs/V1PermissionsApi.md#checkpermission) | **POST** /api/v1/permissions/check | Check permission
+*V1PermissionsApi* | [**createRelationship**](docs/V1PermissionsApi.md#createrelationship) | **POST** /api/v1/permissions/relationships | Create relationship
+*V1PermissionsApi* | [**deployPermissionNamespaces**](docs/V1PermissionsApi.md#deploypermissionnamespaces) | **POST** /api/v1/permissions/namespaces | Deploy Keto namespace configurations
+*V1StorageApi* | [**apiV1StorageDownloadPost**](docs/V1StorageApi.md#apiv1storagedownloadpost) | **POST** /api/v1/storage/download | Download file from storage
+*V1StorageApi* | [**apiV1StorageObjectDelete**](docs/V1StorageApi.md#apiv1storageobjectdelete) | **DELETE** /api/v1/storage/object | Delete file from storage
+*V1StorageApi* | [**apiV1StorageUploadPost**](docs/V1StorageApi.md#apiv1storageuploadpost) | **POST** /api/v1/storage/upload | Upload file to storage
+*V1StripeApi* | [**archiveAllStripeConfig**](docs/V1StripeApi.md#archiveallstripeconfig) | **POST** /api/v1/stripe/config/archive-all | Archive all Stripe config
+*V1StripeApi* | [**getStripeConfig**](docs/V1StripeApi.md#getstripeconfig) | **GET** /api/v1/stripe/config | Get public Stripe config
+*V1StripeApi* | [**getStripeConfigAdmin**](docs/V1StripeApi.md#getstripeconfigadmin) | **GET** /api/v1/stripe/config/admin | Get full Stripe config (admin)
+*V1StripeApi* | [**getStripeConfigHistory**](docs/V1StripeApi.md#getstripeconfighistory) | **GET** /api/v1/stripe/config/history | Get config history
+*V1StripeApi* | [**getStripeConfigSchema**](docs/V1StripeApi.md#getstripeconfigschema) | **GET** /api/v1/stripe/schema | Get Stripe config schema
+*V1StripeApi* | [**pullStripeConfig**](docs/V1StripeApi.md#pullstripeconfig) | **GET** /api/v1/stripe/config/pull | Pull config from Stripe
+*V1StripeApi* | [**updateStripeConfig**](docs/V1StripeApi.md#updatestripeconfig) | **POST** /api/v1/stripe/config | Update Stripe config
+*V1StripeApi* | [**validateStripeConfig**](docs/V1StripeApi.md#validatestripeconfig) | **POST** /api/v1/stripe/config/validate | Validate Stripe config
+*V1TenantsApi* | [**acceptInvite**](docs/V1TenantsApi.md#acceptinvite) | **PUT** /api/v1/tenants/invites/accept | Accept tenant invite
+*V1TenantsApi* | [**assignRole**](docs/V1TenantsApi.md#assignrole) | **POST** /api/v1/tenants/roles/assign/{user_id} | Assign role to user
+*V1TenantsApi* | [**createInvite**](docs/V1TenantsApi.md#createinvite) | **POST** /api/v1/tenants/invites | Create tenant invite
+*V1TenantsApi* | [**createRole**](docs/V1TenantsApi.md#createrole) | **POST** /api/v1/tenants/roles | Create role
+*V1TenantsApi* | [**createTenant**](docs/V1TenantsApi.md#createtenant) | **POST** /api/v1/tenants | Create tenant
+*V1TenantsApi* | [**deleteRole**](docs/V1TenantsApi.md#deleterole) | **DELETE** /api/v1/tenants/roles/{role_id} | Delete role
+*V1TenantsApi* | [**deleteTenant**](docs/V1TenantsApi.md#deletetenant) | **DELETE** /api/v1/tenants | Delete tenant
+*V1TenantsApi* | [**getRoleDefinitions**](docs/V1TenantsApi.md#getroledefinitions) | **GET** /api/v1/tenants/roles/definitions | Get namespace definitions
+*V1TenantsApi* | [**getTenantBillingStatus**](docs/V1TenantsApi.md#gettenantbillingstatus) | **GET** /api/v1/tenants/billing-status | Get billing status
+*V1TenantsApi* | [**getTenantJWT**](docs/V1TenantsApi.md#gettenantjwt) | **GET** /api/v1/tenants/jwt | Get PostgREST JWT token
+*V1TenantsApi* | [**listRoles**](docs/V1TenantsApi.md#listroles) | **GET** /api/v1/tenants/roles | List roles
+*V1TenantsApi* | [**listTenantSubscriptions**](docs/V1TenantsApi.md#listtenantsubscriptions) | **GET** /api/v1/tenants/subscriptions | Get tenant subscriptions
+*V1TenantsApi* | [**listTenantUsers**](docs/V1TenantsApi.md#listtenantusers) | **GET** /api/v1/tenants/users | Get tenant users
+*V1TenantsApi* | [**removeTenantUser**](docs/V1TenantsApi.md#removetenantuser) | **DELETE** /api/v1/tenants/users | Remove tenant user
+*V1TenantsApi* | [**switchActiveTenant**](docs/V1TenantsApi.md#switchactivetenant) | **PUT** /api/v1/tenants/switch-active | Switch active tenant
+*V1TenantsApi* | [**updateRole**](docs/V1TenantsApi.md#updaterole) | **PUT** /api/v1/tenants/roles/{role_id} | Update role
+*V1TenantsApi* | [**updateTenantUserRole**](docs/V1TenantsApi.md#updatetenantuserrole) | **PUT** /api/v1/tenants/users/role | Update user role
 ### Models
 - [AcceptInvite200Response](docs/AcceptInvite200Response.md)
+- [ApiV1StorageDownloadPost200Response](docs/ApiV1StorageDownloadPost200Response.md)
+- [ApiV1StorageObjectDelete200Response](docs/ApiV1StorageObjectDelete200Response.md)
+- [ApiV1StorageUploadPost200Response](docs/ApiV1StorageUploadPost200Response.md)
 - [ArchiveAllStripeConfig200Response](docs/ArchiveAllStripeConfig200Response.md)
 - [AssignRole200Response](docs/AssignRole200Response.md)
 - [CheckPermission200Response](docs/CheckPermission200Response.md)
@@ -152,9 +155,6 @@ All URIs are relative to *http://https://api.omnibase.tech/api/v1*
 - [ModelsUploadRequest](docs/ModelsUploadRequest.md)
 - [ModelsUploadResponse](docs/ModelsUploadResponse.md)
 - [PullStripeConfig200Response](docs/PullStripeConfig200Response.md)
-- [StorageDownloadPost200Response](docs/StorageDownloadPost200Response.md)
-- [StorageObjectDelete200Response](docs/StorageObjectDelete200Response.md)
-- [StorageUploadPost200Response](docs/StorageUploadPost200Response.md)
 - [SwitchActiveTenant200Response](docs/SwitchActiveTenant200Response.md)
 - [TenantsAcceptInviteRequest](docs/TenantsAcceptInviteRequest.md)
 - [TenantsAcceptInviteResponse](docs/TenantsAcceptInviteResponse.md)
@@ -222,8 +222,8 @@ This TypeScript SDK client supports the [Fetch API](https://fetch.spec.whatwg.or
 and is automatically generated by the
 [OpenAPI Generator](https://openapi-generator.tech) project:
-- API version: `0.9.1`
-- Package version: `0.9.1`
+- API version: `0.9.3`
+- Package version: `0.9.3`
 - Generator version: `7.17.0`
 - Build package: `org.openapitools.codegen.languages.TypeScriptFetchClientCodegen`

package/dist/apis/{DatabaseApi.d.ts → V1DatabaseApi.d.ts} RENAMED Viewed

@@ -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.1
+ * The version of the OpenAPI document: 0.9.3
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
@@ -17,7 +17,7 @@ export interface UploadDatabaseMigrationsRequest {
 /**
  *
  */
-export declare class DatabaseApi extends runtime.BaseAPI {
+export declare 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

package/dist/apis/{DatabaseApi.js → V1DatabaseApi.js} RENAMED Viewed

@@ -5,7 +5,7 @@
  * Omnibase REST API
  * Self-hostable Backend-as-a-Service providing database management, authentication, payments, storage, and email services.  ## Features - **Database**: PostgreSQL with RLS and migrations - **Authentication**: Ory Kratos integration with session management - **Payments**: Stripe integration with version-controlled billing configs - **Storage**: S3-compatible object storage with RLS - **Email**: Transactional email service - **Permissions**: Fine-grained access control via Ory Keto  ## Authentication Most endpoints require authentication via session cookies or JWT tokens. Use the appropriate security scheme based on the endpoint requirements.
  *
- * The version of the OpenAPI document: 0.9.1
+ * The version of the OpenAPI document: 0.9.3
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
@@ -22,13 +22,13 @@ var __awaiter = (this && this.__awaiter) || function (thisArg, _arguments, P, ge
     });
 };
 Object.defineProperty(exports, "__esModule", { value: true });
-exports.DatabaseApi = void 0;
+exports.V1DatabaseApi = void 0;
 const runtime = require("../runtime");
 const index_1 = require("../models/index");
 /**
  *
  */
-class DatabaseApi extends runtime.BaseAPI {
+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
@@ -61,7 +61,7 @@ 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',
@@ -83,4 +83,4 @@ class DatabaseApi extends runtime.BaseAPI {
         });
     }
 }
-exports.DatabaseApi = DatabaseApi;
+exports.V1DatabaseApi = V1DatabaseApi;

package/dist/{esm/apis/PaymentsApi.d.ts → apis/V1PaymentsApi.d.ts} RENAMED Viewed

@@ -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.1
+ * The version of the OpenAPI document: 0.9.3
  * 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/apis/{PaymentsApi.js → V1PaymentsApi.js} RENAMED Viewed

@@ -5,7 +5,7 @@
  * Omnibase REST API
  * Self-hostable Backend-as-a-Service providing database management, authentication, payments, storage, and email services.  ## Features - **Database**: PostgreSQL with RLS and migrations - **Authentication**: Ory Kratos integration with session management - **Payments**: Stripe integration with version-controlled billing configs - **Storage**: S3-compatible object storage with RLS - **Email**: Transactional email service - **Permissions**: Fine-grained access control via Ory Keto  ## Authentication Most endpoints require authentication via session cookies or JWT tokens. Use the appropriate security scheme based on the endpoint requirements.
  *
- * The version of the OpenAPI document: 0.9.1
+ * The version of the OpenAPI document: 0.9.3
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
@@ -22,13 +22,13 @@ var __awaiter = (this && this.__awaiter) || function (thisArg, _arguments, P, ge
     });
 };
 Object.defineProperty(exports, "__esModule", { value: true });
-exports.PaymentsApi = void 0;
+exports.V1PaymentsApi = void 0;
 const runtime = require("../runtime");
 const index_1 = require("../models/index");
 /**
  *
  */
-class PaymentsApi extends runtime.BaseAPI {
+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
@@ -44,7 +44,7 @@ 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',
@@ -80,7 +80,7 @@ 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',
@@ -116,7 +116,7 @@ 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',
@@ -138,4 +138,4 @@ class PaymentsApi extends runtime.BaseAPI {
         });
     }
 }
-exports.PaymentsApi = PaymentsApi;
+exports.V1PaymentsApi = V1PaymentsApi;

package/dist/{esm/apis/PermissionsApi.d.ts → apis/V1PermissionsApi.d.ts} RENAMED Viewed

@@ -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.1
+ * The version of the OpenAPI document: 0.9.3
  * 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/apis/{PermissionsApi.js → V1PermissionsApi.js} RENAMED Viewed

@@ -5,7 +5,7 @@
  * Omnibase REST API
  * Self-hostable Backend-as-a-Service providing database management, authentication, payments, storage, and email services.  ## Features - **Database**: PostgreSQL with RLS and migrations - **Authentication**: Ory Kratos integration with session management - **Payments**: Stripe integration with version-controlled billing configs - **Storage**: S3-compatible object storage with RLS - **Email**: Transactional email service - **Permissions**: Fine-grained access control via Ory Keto  ## Authentication Most endpoints require authentication via session cookies or JWT tokens. Use the appropriate security scheme based on the endpoint requirements.
  *
- * The version of the OpenAPI document: 0.9.1
+ * The version of the OpenAPI document: 0.9.3
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
@@ -22,13 +22,13 @@ var __awaiter = (this && this.__awaiter) || function (thisArg, _arguments, P, ge
     });
 };
 Object.defineProperty(exports, "__esModule", { value: true });
-exports.PermissionsApi = void 0;
+exports.V1PermissionsApi = void 0;
 const runtime = require("../runtime");
 const index_1 = require("../models/index");
 /**
  *
  */
-class PermissionsApi extends runtime.BaseAPI {
+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
@@ -44,7 +44,7 @@ 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',
@@ -80,7 +80,7 @@ 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',
@@ -133,7 +133,7 @@ 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',
@@ -155,4 +155,4 @@ class PermissionsApi extends runtime.BaseAPI {
         });
     }
 }
-exports.PermissionsApi = PermissionsApi;
+exports.V1PermissionsApi = V1PermissionsApi;

package/dist/{esm/apis/StorageApi.d.ts → apis/V1StorageApi.d.ts} RENAMED Viewed

@@ -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.1
+ * The version of the OpenAPI document: 0.9.3
  * 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>;
 }