@omnibase/core-js 0.9.16 → 0.9.18

package/.openapi-generator/FILES

@@ -16,8 +16,8 @@ docs/BillingInterval.md
 docs/BillingStatusResponse.md
 docs/CheckPermission200Response.md
 docs/CheckPermissionRequest.md
-docs/CheckPermissionRequestOneOf.md
-docs/CheckPermissionRequestOneOf1.md
+docs/CheckPermissionRequestWithSubjectId.md
+docs/CheckPermissionRequestWithSubjectSet.md
 docs/CheckPermissionResponse.md
 docs/ConfigHistoryItem.md
 docs/ConfigHistoryPagination.md
@@ -36,8 +36,8 @@ docs/CreatePortalRequest.md
 docs/CreatePortalResponse.md
 docs/CreateRelationship200Response.md
 docs/CreateRelationshipRequest.md
-docs/CreateRelationshipRequestOneOf.md
-docs/CreateRelationshipRequestOneOf1.md
+docs/CreateRelationshipRequestWithSubjectId.md
+docs/CreateRelationshipRequestWithSubjectSet.md
 docs/CreateRelationshipResponse.md
 docs/CreateRole200Response.md
 docs/CreateRoleRequest.md
@@ -56,6 +56,8 @@ docs/DeleteObject200Response.md
 docs/DeleteObjectRequest.md
 docs/DeleteRelationship200Response.md
 docs/DeleteRelationshipRequest.md
+docs/DeleteRelationshipRequestWithSubjectId.md
+docs/DeleteRelationshipRequestWithSubjectSet.md
 docs/DeleteRelationshipResponse.md
 docs/DeleteRole200Response.md
 docs/DeleteRoleResponse.md
@@ -199,8 +201,8 @@ src/models/BillingInterval.ts
 src/models/BillingStatusResponse.ts
 src/models/CheckPermission200Response.ts
 src/models/CheckPermissionRequest.ts
-src/models/CheckPermissionRequestOneOf.ts
-src/models/CheckPermissionRequestOneOf1.ts
+src/models/CheckPermissionRequestWithSubjectId.ts
+src/models/CheckPermissionRequestWithSubjectSet.ts
 src/models/CheckPermissionResponse.ts
 src/models/ConfigHistoryItem.ts
 src/models/ConfigHistoryPagination.ts
@@ -219,8 +221,8 @@ src/models/CreatePortalRequest.ts
 src/models/CreatePortalResponse.ts
 src/models/CreateRelationship200Response.ts
 src/models/CreateRelationshipRequest.ts
-src/models/CreateRelationshipRequestOneOf.ts
-src/models/CreateRelationshipRequestOneOf1.ts
+src/models/CreateRelationshipRequestWithSubjectId.ts
+src/models/CreateRelationshipRequestWithSubjectSet.ts
 src/models/CreateRelationshipResponse.ts
 src/models/CreateRole200Response.ts
 src/models/CreateRoleRequest.ts
@@ -239,6 +241,8 @@ src/models/DeleteObject200Response.ts
 src/models/DeleteObjectRequest.ts
 src/models/DeleteRelationship200Response.ts
 src/models/DeleteRelationshipRequest.ts
+src/models/DeleteRelationshipRequestWithSubjectId.ts
+src/models/DeleteRelationshipRequestWithSubjectSet.ts
 src/models/DeleteRelationshipResponse.ts
 src/models/DeleteRole200Response.ts
 src/models/DeleteRoleResponse.ts

package/README.md

@@ -1,4 +1,4 @@
-# @omnibase/core-js@0.9.16
+# @omnibase/core-js@0.9.18
 
 A TypeScript SDK client for the api.omnibase.tech API.
 
@@ -122,8 +122,8 @@ All URIs are relative to *https://api.omnibase.tech*
 - [BillingStatusResponse](docs/BillingStatusResponse.md)
 - [CheckPermission200Response](docs/CheckPermission200Response.md)
 - [CheckPermissionRequest](docs/CheckPermissionRequest.md)
-- [CheckPermissionRequestOneOf](docs/CheckPermissionRequestOneOf.md)
-- [CheckPermissionRequestOneOf1](docs/CheckPermissionRequestOneOf1.md)
+- [CheckPermissionRequestWithSubjectId](docs/CheckPermissionRequestWithSubjectId.md)
+- [CheckPermissionRequestWithSubjectSet](docs/CheckPermissionRequestWithSubjectSet.md)
 - [CheckPermissionResponse](docs/CheckPermissionResponse.md)
 - [ConfigHistoryItem](docs/ConfigHistoryItem.md)
 - [ConfigHistoryPagination](docs/ConfigHistoryPagination.md)
@@ -142,8 +142,8 @@ All URIs are relative to *https://api.omnibase.tech*
 - [CreatePortalResponse](docs/CreatePortalResponse.md)
 - [CreateRelationship200Response](docs/CreateRelationship200Response.md)
 - [CreateRelationshipRequest](docs/CreateRelationshipRequest.md)
-- [CreateRelationshipRequestOneOf](docs/CreateRelationshipRequestOneOf.md)
-- [CreateRelationshipRequestOneOf1](docs/CreateRelationshipRequestOneOf1.md)
+- [CreateRelationshipRequestWithSubjectId](docs/CreateRelationshipRequestWithSubjectId.md)
+- [CreateRelationshipRequestWithSubjectSet](docs/CreateRelationshipRequestWithSubjectSet.md)
 - [CreateRelationshipResponse](docs/CreateRelationshipResponse.md)
 - [CreateRole200Response](docs/CreateRole200Response.md)
 - [CreateRoleRequest](docs/CreateRoleRequest.md)
@@ -162,6 +162,8 @@ All URIs are relative to *https://api.omnibase.tech*
 - [DeleteObjectRequest](docs/DeleteObjectRequest.md)
 - [DeleteRelationship200Response](docs/DeleteRelationship200Response.md)
 - [DeleteRelationshipRequest](docs/DeleteRelationshipRequest.md)
+- [DeleteRelationshipRequestWithSubjectId](docs/DeleteRelationshipRequestWithSubjectId.md)
+- [DeleteRelationshipRequestWithSubjectSet](docs/DeleteRelationshipRequestWithSubjectSet.md)
 - [DeleteRelationshipResponse](docs/DeleteRelationshipResponse.md)
 - [DeleteRole200Response](docs/DeleteRole200Response.md)
 - [DeleteRoleResponse](docs/DeleteRoleResponse.md)
@@ -304,8 +306,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.16`
-- Package version: `0.9.16`
+- API version: `0.9.18`
+- Package version: `0.9.18`
 - Generator version: `7.17.0`
 - Build package: `org.openapitools.codegen.languages.TypeScriptFetchClientCodegen`
 

package/docs/CheckPermissionRequestWithSubjectId.md

@@ -0,0 +1,41 @@
+
+# CheckPermissionRequestWithSubjectId
+
+Check permission request using a direct subject identifier
+
+## Properties
+
+Name | Type
+------------ | -------------
+`namespace` | string
+`object` | string
+`relation` | string
+`subjectId` | string
+
+## Example
+
+```typescript
+import type { CheckPermissionRequestWithSubjectId } from '@omnibase/core-js'
+
+// TODO: Update the object below with actual values
+const example = {
+  "namespace": null,
+  "object": null,
+  "relation": null,
+  "subjectId": null,
+} satisfies CheckPermissionRequestWithSubjectId
+
+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 CheckPermissionRequestWithSubjectId
+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/CheckPermissionRequestWithSubjectSet.md

@@ -0,0 +1,41 @@
+
+# CheckPermissionRequestWithSubjectSet
+
+Check permission request using a subject set
+
+## Properties
+
+Name | Type
+------------ | -------------
+`namespace` | string
+`object` | string
+`relation` | string
+`subjectSet` | [SubjectSetRequest](SubjectSetRequest.md)
+
+## Example
+
+```typescript
+import type { CheckPermissionRequestWithSubjectSet } from '@omnibase/core-js'
+
+// TODO: Update the object below with actual values
+const example = {
+  "namespace": null,
+  "object": null,
+  "relation": null,
+  "subjectSet": null,
+} satisfies CheckPermissionRequestWithSubjectSet
+
+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 CheckPermissionRequestWithSubjectSet
+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/CreateRelationshipRequestWithSubjectId.md

@@ -0,0 +1,41 @@
+
+# CreateRelationshipRequestWithSubjectId
+
+Create relationship request using a direct subject identifier
+
+## Properties
+
+Name | Type
+------------ | -------------
+`namespace` | string
+`object` | string
+`relation` | string
+`subjectId` | string
+
+## Example
+
+```typescript
+import type { CreateRelationshipRequestWithSubjectId } from '@omnibase/core-js'
+
+// TODO: Update the object below with actual values
+const example = {
+  "namespace": null,
+  "object": null,
+  "relation": null,
+  "subjectId": null,
+} satisfies CreateRelationshipRequestWithSubjectId
+
+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 CreateRelationshipRequestWithSubjectId
+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/CreateRelationshipRequestWithSubjectSet.md

@@ -0,0 +1,41 @@
+
+# CreateRelationshipRequestWithSubjectSet
+
+Create relationship request using a subject set
+
+## Properties
+
+Name | Type
+------------ | -------------
+`namespace` | string
+`object` | string
+`relation` | string
+`subjectSet` | [SubjectSetRequest](SubjectSetRequest.md)
+
+## Example
+
+```typescript
+import type { CreateRelationshipRequestWithSubjectSet } from '@omnibase/core-js'
+
+// TODO: Update the object below with actual values
+const example = {
+  "namespace": null,
+  "object": null,
+  "relation": null,
+  "subjectSet": null,
+} satisfies CreateRelationshipRequestWithSubjectSet
+
+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 CreateRelationshipRequestWithSubjectSet
+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/DeleteRelationshipRequestWithSubjectId.md

@@ -0,0 +1,41 @@
+
+# DeleteRelationshipRequestWithSubjectId
+
+Delete relationship request using a direct subject identifier
+
+## Properties
+
+Name | Type
+------------ | -------------
+`namespace` | string
+`object` | string
+`relation` | string
+`subjectId` | string
+
+## Example
+
+```typescript
+import type { DeleteRelationshipRequestWithSubjectId } from '@omnibase/core-js'
+
+// TODO: Update the object below with actual values
+const example = {
+  "namespace": null,
+  "object": null,
+  "relation": null,
+  "subjectId": null,
+} satisfies DeleteRelationshipRequestWithSubjectId
+
+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 DeleteRelationshipRequestWithSubjectId
+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/DeleteRelationshipRequestWithSubjectSet.md

@@ -0,0 +1,41 @@
+
+# DeleteRelationshipRequestWithSubjectSet
+
+Delete relationship request using a subject set
+
+## Properties
+
+Name | Type
+------------ | -------------
+`namespace` | string
+`object` | string
+`relation` | string
+`subjectSet` | [SubjectSetRequest](SubjectSetRequest.md)
+
+## Example
+
+```typescript
+import type { DeleteRelationshipRequestWithSubjectSet } from '@omnibase/core-js'
+
+// TODO: Update the object below with actual values
+const example = {
+  "namespace": null,
+  "object": null,
+  "relation": null,
+  "subjectSet": null,
+} satisfies DeleteRelationshipRequestWithSubjectSet
+
+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 DeleteRelationshipRequestWithSubjectSet
+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/NamespaceDefinition.md

@@ -10,6 +10,7 @@ Name | Type
 `id` | string
 `namespace` | string
 `relations` | Array<string>
+`subjectRelations` | { [key: string]: Array<string>; }
 `updatedAt` | Date
 
 ## Example
@@ -22,6 +23,7 @@ const example = {
   "id": bfab650b-f834-4904-a4e8-41343fea86bc,
   "namespace": Tenant,
   "relations": [can_delete_tenant, can_invite_user, can_update_user_role],
+  "subjectRelations": {User=[can_delete_tenant, can_invite_user, can_rotate_keys], ApiKey=[can_rotate_keys, can_view_db_secret_key]},
   "updatedAt": 2025-11-10T00:33:08.720326Z,
 } satisfies NamespaceDefinition
 

package/docs/V1TenantsApi.md

@@ -610,11 +610,11 @@ example().catch(console.error);
 
 ## getRoleDefinitions
 
-> GetRoleDefinitions200Response getRoleDefinitions()
+> GetRoleDefinitions200Response getRoleDefinitions(subject)
 
 Get namespace definitions
 
-Returns all available permission namespaces and their relations from the database.  ## Authentication Requires JWT token with appropriate permissions.  ## Use Cases - Discover available permission namespaces - List relations for each namespace - Build dynamic permission UIs 
+Returns all available permission namespaces and their relations from the database.  ## Authentication Requires JWT token with appropriate permissions.  ## Use Cases - Discover available permission namespaces - List relations for each namespace - Build dynamic permission UIs - Filter by subject type for API key creation 
 
 ### Example
 
@@ -637,8 +637,13 @@ async function example() {
   });
   const api = new V1TenantsApi(config);
 
+  const body = {
+    // string | Filter to only return relations that accept this subject type (e.g., \"ApiKey\", \"User\") (optional)
+    subject: ApiKey,
+  } satisfies GetRoleDefinitionsRequest;
+
   try {
-    const data = await api.getRoleDefinitions();
+    const data = await api.getRoleDefinitions(body);
     console.log(data);
   } catch (error) {
     console.error(error);
@@ -651,7 +656,10 @@ example().catch(console.error);
 
 ### Parameters
 
-This endpoint does not need any parameter.
+
+| Name | Type | Description  | Notes |
+|------------- | ------------- | ------------- | -------------|
+| **subject** | `string` | Filter to only return relations that accept this subject type (e.g., \"ApiKey\", \"User\") | [Optional] [Defaults to `undefined`] |
 
 ### Return type
 

package/package.json

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

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

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

package/src/apis/V1EventsApi.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.16
+ * The version of the OpenAPI document: 0.9.18
  * 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.16
+ * The version of the OpenAPI document: 0.9.18
  * 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.16
+ * The version of the OpenAPI document: 0.9.18
  * 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.16
+ * The version of the OpenAPI document: 0.9.18
  * 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.16
+ * The version of the OpenAPI document: 0.9.18
  * 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.16
+ * The version of the OpenAPI document: 0.9.18
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
@@ -149,6 +149,10 @@ export interface DeleteTenantRequest {
     xTenantId?: string;
 }
 
+export interface GetRoleDefinitionsRequest {
+    subject?: string;
+}
+
 export interface GetTenantJWTRequest {
     xUserId?: string;
     xTenantId?: string;
@@ -566,12 +570,16 @@ export class V1TenantsApi extends runtime.BaseAPI {
     }
 
     /**
-     * Returns all available permission namespaces and their relations from the database.  ## Authentication Requires JWT token with appropriate permissions.  ## Use Cases - Discover available permission namespaces - List relations for each namespace - Build dynamic permission UIs 
+     * Returns all available permission namespaces and their relations from the database.  ## Authentication Requires JWT token with appropriate permissions.  ## Use Cases - Discover available permission namespaces - List relations for each namespace - Build dynamic permission UIs - Filter by subject type for API key creation 
      * Get namespace definitions
      */
-    async getRoleDefinitionsRaw(initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<GetRoleDefinitions200Response>> {
+    async getRoleDefinitionsRaw(requestParameters: GetRoleDefinitionsRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<GetRoleDefinitions200Response>> {
         const queryParameters: any = {};
 
+        if (requestParameters['subject'] != null) {
+            queryParameters['subject'] = requestParameters['subject'];
+        }
+
         const headerParameters: runtime.HTTPHeaders = {};
 
         if (this.configuration && this.configuration.apiKey) {
@@ -596,11 +604,11 @@ export class V1TenantsApi extends runtime.BaseAPI {
     }
 
     /**
-     * Returns all available permission namespaces and their relations from the database.  ## Authentication Requires JWT token with appropriate permissions.  ## Use Cases - Discover available permission namespaces - List relations for each namespace - Build dynamic permission UIs 
+     * Returns all available permission namespaces and their relations from the database.  ## Authentication Requires JWT token with appropriate permissions.  ## Use Cases - Discover available permission namespaces - List relations for each namespace - Build dynamic permission UIs - Filter by subject type for API key creation 
      * Get namespace definitions
      */
-    async getRoleDefinitions(initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<GetRoleDefinitions200Response> {
-        const response = await this.getRoleDefinitionsRaw(initOverrides);
+    async getRoleDefinitions(requestParameters: GetRoleDefinitionsRequest = {}, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<GetRoleDefinitions200Response> {
+        const response = await this.getRoleDefinitionsRaw(requestParameters, initOverrides);
         return await response.value();
     }
 

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

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

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

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

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

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

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

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