@omnibase/core-js 0.7.6 → 0.9.0

package/docs/PaymentsApi.md

@@ -0,0 +1,233 @@
+# PaymentsApi
+
+All URIs are relative to *http://https://api.omnibase.tech/api/v1*
+
+| Method | HTTP request | Description |
+|------------- | ------------- | -------------|
+| [**createCheckout**](PaymentsApi.md#createcheckout) | **POST** /payments/checkout | Create checkout session |
+| [**createCustomerPortal**](PaymentsApi.md#createcustomerportal) | **POST** /payments/portal | Create customer portal session |
+| [**recordUsage**](PaymentsApi.md#recordusage) | **POST** /payments/usage | Record metered usage |
+
+
+
+## createCheckout
+
+> CreateCheckout200Response createCheckout(request)
+
+Create checkout session
+
+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
+
+### Example
+
+```ts
+import {
+  Configuration,
+  PaymentsApi,
+} from '@omnibase/core-js';
+import type { CreateCheckoutRequest } from '@omnibase/core-js';
+
+async function example() {
+  console.log("🚀 Testing @omnibase/core-js SDK...");
+  const config = new Configuration({ 
+    // To configure API key authorization: BearerAuth
+    apiKey: "YOUR API KEY",
+  });
+  const api = new PaymentsApi(config);
+
+  const body = {
+    // V1CreateCheckoutRequest | Checkout session parameters
+    request: ...,
+  } satisfies CreateCheckoutRequest;
+
+  try {
+    const data = await api.createCheckout(body);
+    console.log(data);
+  } catch (error) {
+    console.error(error);
+  }
+}
+
+// Run the test
+example().catch(console.error);
+```
+
+### Parameters
+
+
+| Name | Type | Description  | Notes |
+|------------- | ------------- | ------------- | -------------|
+| **request** | [V1CreateCheckoutRequest](V1CreateCheckoutRequest.md) | Checkout session parameters | |
+
+### Return type
+
+[**CreateCheckout200Response**](CreateCheckout200Response.md)
+
+### Authorization
+
+[BearerAuth](../README.md#BearerAuth)
+
+### HTTP request headers
+
+- **Content-Type**: `application/json`
+- **Accept**: `application/json`
+
+
+### HTTP response details
+| Status code | Description | Response headers |
+|-------------|-------------|------------------|
+| **200** | Checkout session created successfully |  -  |
+| **400** | Invalid request payload |  -  |
+| **401** | Invalid or missing JWT token |  -  |
+| **500** | Failed to create checkout session |  -  |
+
+[[Back to top]](#) [[Back to API list]](../README.md#api-endpoints) [[Back to Model list]](../README.md#models) [[Back to README]](../README.md)
+
+
+## createCustomerPortal
+
+> CreateCustomerPortal200Response createCustomerPortal(request)
+
+Create customer portal session
+
+Creates a Stripe Customer Portal session where users can manage their subscription, payment methods, and billing history.  ## Authentication Requires JWT token and an associated Stripe customer ID.  ## Use Cases - Subscription management - Payment method updates - Invoice history viewing
+
+### Example
+
+```ts
+import {
+  Configuration,
+  PaymentsApi,
+} from '@omnibase/core-js';
+import type { CreateCustomerPortalRequest } from '@omnibase/core-js';
+
+async function example() {
+  console.log("🚀 Testing @omnibase/core-js SDK...");
+  const config = new Configuration({ 
+    // To configure API key authorization: BearerAuth
+    apiKey: "YOUR API KEY",
+  });
+  const api = new PaymentsApi(config);
+
+  const body = {
+    // V1CreatePortalRequest | Portal session parameters
+    request: ...,
+  } satisfies CreateCustomerPortalRequest;
+
+  try {
+    const data = await api.createCustomerPortal(body);
+    console.log(data);
+  } catch (error) {
+    console.error(error);
+  }
+}
+
+// Run the test
+example().catch(console.error);
+```
+
+### Parameters
+
+
+| Name | Type | Description  | Notes |
+|------------- | ------------- | ------------- | -------------|
+| **request** | [V1CreatePortalRequest](V1CreatePortalRequest.md) | Portal session parameters | |
+
+### Return type
+
+[**CreateCustomerPortal200Response**](CreateCustomerPortal200Response.md)
+
+### Authorization
+
+[BearerAuth](../README.md#BearerAuth)
+
+### HTTP request headers
+
+- **Content-Type**: `application/json`
+- **Accept**: `application/json`
+
+
+### HTTP response details
+| Status code | Description | Response headers |
+|-------------|-------------|------------------|
+| **200** | Portal session created successfully |  -  |
+| **400** | Invalid request or missing customer ID |  -  |
+| **401** | Invalid or missing JWT token |  -  |
+| **500** | Failed to create portal session |  -  |
+
+[[Back to top]](#) [[Back to API list]](../README.md#api-endpoints) [[Back to Model list]](../README.md#models) [[Back to README]](../README.md)
+
+
+## recordUsage
+
+> HandlersSuccessResponse recordUsage(request)
+
+Record metered usage
+
+Records a usage event for metered billing. The customer must have an active subscription with metered pricing.  ## Authentication Requires JWT token and an associated Stripe customer ID.  ## Use Cases - API request metering - Compute time tracking - Storage usage recording - Any metered billing scenario
+
+### Example
+
+```ts
+import {
+  Configuration,
+  PaymentsApi,
+} from '@omnibase/core-js';
+import type { RecordUsageRequest } from '@omnibase/core-js';
+
+async function example() {
+  console.log("🚀 Testing @omnibase/core-js SDK...");
+  const config = new Configuration({ 
+    // To configure API key authorization: BearerAuth
+    apiKey: "YOUR API KEY",
+  });
+  const api = new PaymentsApi(config);
+
+  const body = {
+    // V1RecordUsageRequest | Usage event parameters
+    request: ...,
+  } satisfies RecordUsageRequest;
+
+  try {
+    const data = await api.recordUsage(body);
+    console.log(data);
+  } catch (error) {
+    console.error(error);
+  }
+}
+
+// Run the test
+example().catch(console.error);
+```
+
+### Parameters
+
+
+| Name | Type | Description  | Notes |
+|------------- | ------------- | ------------- | -------------|
+| **request** | [V1RecordUsageRequest](V1RecordUsageRequest.md) | Usage event parameters | |
+
+### Return type
+
+[**HandlersSuccessResponse**](HandlersSuccessResponse.md)
+
+### Authorization
+
+[BearerAuth](../README.md#BearerAuth)
+
+### HTTP request headers
+
+- **Content-Type**: `application/json`
+- **Accept**: `application/json`
+
+
+### HTTP response details
+| Status code | Description | Response headers |
+|-------------|-------------|------------------|
+| **200** | Usage recorded successfully |  -  |
+| **400** | Invalid request or missing customer ID |  -  |
+| **401** | Invalid or missing JWT token |  -  |
+| **500** | Failed to record usage |  -  |
+
+[[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/PermissionsApi.md

@@ -0,0 +1,233 @@
+# PermissionsApi
+
+All URIs are relative to *http://https://api.omnibase.tech/api/v1*
+
+| Method | HTTP request | Description |
+|------------- | ------------- | -------------|
+| [**checkPermission**](PermissionsApi.md#checkpermission) | **POST** /permissions/check | Check permission |
+| [**createRelationship**](PermissionsApi.md#createrelationship) | **POST** /permissions/relationships | Create relationship |
+| [**deployPermissionNamespaces**](PermissionsApi.md#deploypermissionnamespaces) | **POST** /permissions/namespaces | Deploy Keto namespace configurations |
+
+
+
+## checkPermission
+
+> CheckPermission200Response checkPermission(body)
+
+Check permission
+
+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
+
+### Example
+
+```ts
+import {
+  Configuration,
+  PermissionsApi,
+} from '@omnibase/core-js';
+import type { CheckPermissionRequest } from '@omnibase/core-js';
+
+async function example() {
+  console.log("🚀 Testing @omnibase/core-js SDK...");
+  const config = new Configuration({ 
+    // To configure API key authorization: SessionAuth
+    apiKey: "YOUR API KEY",
+  });
+  const api = new PermissionsApi(config);
+
+  const body = {
+    // V1CheckPermissionRequest | Permission check request
+    body: ...,
+  } satisfies CheckPermissionRequest;
+
+  try {
+    const data = await api.checkPermission(body);
+    console.log(data);
+  } catch (error) {
+    console.error(error);
+  }
+}
+
+// Run the test
+example().catch(console.error);
+```
+
+### Parameters
+
+
+| Name | Type | Description  | Notes |
+|------------- | ------------- | ------------- | -------------|
+| **body** | [V1CheckPermissionRequest](V1CheckPermissionRequest.md) | Permission check request | |
+
+### Return type
+
+[**CheckPermission200Response**](CheckPermission200Response.md)
+
+### Authorization
+
+[SessionAuth](../README.md#SessionAuth)
+
+### HTTP request headers
+
+- **Content-Type**: `application/json`
+- **Accept**: `application/json`
+
+
+### HTTP response details
+| Status code | Description | Response headers |
+|-------------|-------------|------------------|
+| **200** | Permission check result |  -  |
+| **400** | Invalid request body |  -  |
+| **401** | Not authenticated |  -  |
+| **500** | Failed to check permission |  -  |
+
+[[Back to top]](#) [[Back to API list]](../README.md#api-endpoints) [[Back to Model list]](../README.md#models) [[Back to README]](../README.md)
+
+
+## createRelationship
+
+> CreateRelationship200Response createRelationship(body)
+
+Create relationship
+
+Creates a new relationship tuple in Ory Keto.  ## Authentication Requires session authentication.  ## Request Format Provide either `subject_id` or `subject_set` (not both).  ## Use Cases - Link resources to tenants - Assign users to projects - Create permission relationships
+
+### Example
+
+```ts
+import {
+  Configuration,
+  PermissionsApi,
+} from '@omnibase/core-js';
+import type { CreateRelationshipRequest } from '@omnibase/core-js';
+
+async function example() {
+  console.log("🚀 Testing @omnibase/core-js SDK...");
+  const config = new Configuration({ 
+    // To configure API key authorization: SessionAuth
+    apiKey: "YOUR API KEY",
+  });
+  const api = new PermissionsApi(config);
+
+  const body = {
+    // V1CreateRelationshipRequest | Relationship creation request
+    body: ...,
+  } satisfies CreateRelationshipRequest;
+
+  try {
+    const data = await api.createRelationship(body);
+    console.log(data);
+  } catch (error) {
+    console.error(error);
+  }
+}
+
+// Run the test
+example().catch(console.error);
+```
+
+### Parameters
+
+
+| Name | Type | Description  | Notes |
+|------------- | ------------- | ------------- | -------------|
+| **body** | [V1CreateRelationshipRequest](V1CreateRelationshipRequest.md) | Relationship creation request | |
+
+### Return type
+
+[**CreateRelationship200Response**](CreateRelationship200Response.md)
+
+### Authorization
+
+[SessionAuth](../README.md#SessionAuth)
+
+### HTTP request headers
+
+- **Content-Type**: `application/json`
+- **Accept**: `application/json`
+
+
+### HTTP response details
+| Status code | Description | Response headers |
+|-------------|-------------|------------------|
+| **200** | Relationship created successfully |  -  |
+| **400** | Invalid request body |  -  |
+| **401** | Not authenticated |  -  |
+| **500** | Failed to create relationship |  -  |
+
+[[Back to top]](#) [[Back to API list]](../README.md#api-endpoints) [[Back to Model list]](../README.md#models) [[Back to README]](../README.md)
+
+
+## deployPermissionNamespaces
+
+> DeployPermissionNamespaces200Response deployPermissionNamespaces(namespaces)
+
+Deploy Keto namespace configurations
+
+Uploads and deploys permission namespace configurations as a zip file.  ## Authentication Requires JWT token with appropriate permissions.  ## File Format Upload a zip file containing namespace definition files and optionally a roles.config.json file. The namespace files are stored in S3 and parsed to extract permission definitions.  ## Managed Mode If managed hosting is enabled, this endpoint will also trigger a restart of the Keto service.  ## Use Cases - CLI namespace deployment via `omnibase permissions push` - CI/CD pipeline integrations - Programmatic permission management
+
+### Example
+
+```ts
+import {
+  Configuration,
+  PermissionsApi,
+} from '@omnibase/core-js';
+import type { DeployPermissionNamespacesRequest } from '@omnibase/core-js';
+
+async function example() {
+  console.log("🚀 Testing @omnibase/core-js SDK...");
+  const config = new Configuration({ 
+    // To configure API key authorization: BearerAuth
+    apiKey: "YOUR API KEY",
+  });
+  const api = new PermissionsApi(config);
+
+  const body = {
+    // Blob | Zip file containing namespace configuration files
+    namespaces: BINARY_DATA_HERE,
+  } satisfies DeployPermissionNamespacesRequest;
+
+  try {
+    const data = await api.deployPermissionNamespaces(body);
+    console.log(data);
+  } catch (error) {
+    console.error(error);
+  }
+}
+
+// Run the test
+example().catch(console.error);
+```
+
+### Parameters
+
+
+| Name | Type | Description  | Notes |
+|------------- | ------------- | ------------- | -------------|
+| **namespaces** | `Blob` | Zip file containing namespace configuration files | [Defaults to `undefined`] |
+
+### Return type
+
+[**DeployPermissionNamespaces200Response**](DeployPermissionNamespaces200Response.md)
+
+### Authorization
+
+[BearerAuth](../README.md#BearerAuth)
+
+### HTTP request headers
+
+- **Content-Type**: `multipart/form-data`
+- **Accept**: `application/json`
+
+
+### HTTP response details
+| Status code | Description | Response headers |
+|-------------|-------------|------------------|
+| **200** | Namespaces deployed successfully |  -  |
+| **400** | Invalid file or missing tenant ID |  -  |
+| **401** | Invalid or missing JWT token |  -  |
+| **500** | Failed to deploy namespaces |  -  |
+
+[[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/StorageApi.md

@@ -0,0 +1,237 @@
+# StorageApi
+
+All URIs are relative to *http://https://api.omnibase.tech/api/v1*
+
+| Method | HTTP request | Description |
+|------------- | ------------- | -------------|
+| [**storageDownloadPost**](StorageApi.md#storagedownloadpost) | **POST** /storage/download | Download file from storage |
+| [**storageObjectDelete**](StorageApi.md#storageobjectdelete) | **DELETE** /storage/object | Delete file from storage |
+| [**storageUploadPost**](StorageApi.md#storageuploadpost) | **POST** /storage/upload | Upload file to storage |
+
+
+
+## storageDownloadPost
+
+> StorageDownloadPost200Response storageDownloadPost(request)
+
+Download file from storage
+
+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.
+
+### Example
+
+```ts
+import {
+  Configuration,
+  StorageApi,
+} from '@omnibase/core-js';
+import type { StorageDownloadPostRequest } from '@omnibase/core-js';
+
+async function example() {
+  console.log("🚀 Testing @omnibase/core-js SDK...");
+  const config = new Configuration({ 
+    // To configure API key authorization: SessionAuth
+    apiKey: "YOUR API KEY",
+  });
+  const api = new StorageApi(config);
+
+  const body = {
+    // ModelsDownloadRequest | Path of file to download
+    request: ...,
+  } satisfies StorageDownloadPostRequest;
+
+  try {
+    const data = await api.storageDownloadPost(body);
+    console.log(data);
+  } catch (error) {
+    console.error(error);
+  }
+}
+
+// Run the test
+example().catch(console.error);
+```
+
+### Parameters
+
+
+| Name | Type | Description  | Notes |
+|------------- | ------------- | ------------- | -------------|
+| **request** | [ModelsDownloadRequest](ModelsDownloadRequest.md) | Path of file to download | |
+
+### Return type
+
+[**StorageDownloadPost200Response**](StorageDownloadPost200Response.md)
+
+### Authorization
+
+[SessionAuth](../README.md#SessionAuth)
+
+### HTTP request headers
+
+- **Content-Type**: `application/json`
+- **Accept**: `application/json`
+
+
+### HTTP response details
+| Status code | Description | Response headers |
+|-------------|-------------|------------------|
+| **200** | Download URL generated successfully |  -  |
+| **400** | Invalid request body or missing path |  -  |
+| **401** | Missing authentication session |  -  |
+| **403** | RLS policy denied download access for this path |  -  |
+| **404** | File not found in storage |  -  |
+| **500** | Failed to generate presigned URL |  -  |
+
+[[Back to top]](#) [[Back to API list]](../README.md#api-endpoints) [[Back to Model list]](../README.md#models) [[Back to README]](../README.md)
+
+
+## storageObjectDelete
+
+> StorageObjectDelete200Response storageObjectDelete(request)
+
+Delete file from storage
+
+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)
+
+### Example
+
+```ts
+import {
+  Configuration,
+  StorageApi,
+} from '@omnibase/core-js';
+import type { StorageObjectDeleteRequest } from '@omnibase/core-js';
+
+async function example() {
+  console.log("🚀 Testing @omnibase/core-js SDK...");
+  const config = new Configuration({ 
+    // To configure API key authorization: SessionAuth
+    apiKey: "YOUR API KEY",
+  });
+  const api = new StorageApi(config);
+
+  const body = {
+    // ModelsDeleteObjectRequest | Path of file to delete
+    request: ...,
+  } satisfies StorageObjectDeleteRequest;
+
+  try {
+    const data = await api.storageObjectDelete(body);
+    console.log(data);
+  } catch (error) {
+    console.error(error);
+  }
+}
+
+// Run the test
+example().catch(console.error);
+```
+
+### Parameters
+
+
+| Name | Type | Description  | Notes |
+|------------- | ------------- | ------------- | -------------|
+| **request** | [ModelsDeleteObjectRequest](ModelsDeleteObjectRequest.md) | Path of file to delete | |
+
+### Return type
+
+[**StorageObjectDelete200Response**](StorageObjectDelete200Response.md)
+
+### Authorization
+
+[SessionAuth](../README.md#SessionAuth)
+
+### HTTP request headers
+
+- **Content-Type**: `application/json`
+- **Accept**: `application/json`
+
+
+### HTTP response details
+| Status code | Description | Response headers |
+|-------------|-------------|------------------|
+| **200** | File deleted successfully |  -  |
+| **400** | Invalid request body or missing path |  -  |
+| **401** | Missing authentication session |  -  |
+| **403** | RLS policy denied delete access for this path |  -  |
+| **404** | File not found or already deleted |  -  |
+
+[[Back to top]](#) [[Back to API list]](../README.md#api-endpoints) [[Back to Model list]](../README.md#models) [[Back to README]](../README.md)
+
+
+## storageUploadPost
+
+> StorageUploadPost200Response storageUploadPost(request)
+
+Upload file to storage
+
+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.
+
+### Example
+
+```ts
+import {
+  Configuration,
+  StorageApi,
+} from '@omnibase/core-js';
+import type { StorageUploadPostRequest } from '@omnibase/core-js';
+
+async function example() {
+  console.log("🚀 Testing @omnibase/core-js SDK...");
+  const config = new Configuration({ 
+    // To configure API key authorization: SessionAuth
+    apiKey: "YOUR API KEY",
+  });
+  const api = new StorageApi(config);
+
+  const body = {
+    // ModelsUploadRequest | Upload configuration with path and optional metadata
+    request: ...,
+  } satisfies StorageUploadPostRequest;
+
+  try {
+    const data = await api.storageUploadPost(body);
+    console.log(data);
+  } catch (error) {
+    console.error(error);
+  }
+}
+
+// Run the test
+example().catch(console.error);
+```
+
+### Parameters
+
+
+| Name | Type | Description  | Notes |
+|------------- | ------------- | ------------- | -------------|
+| **request** | [ModelsUploadRequest](ModelsUploadRequest.md) | Upload configuration with path and optional metadata | |
+
+### Return type
+
+[**StorageUploadPost200Response**](StorageUploadPost200Response.md)
+
+### Authorization
+
+[SessionAuth](../README.md#SessionAuth)
+
+### HTTP request headers
+
+- **Content-Type**: `application/json`
+- **Accept**: `application/json`
+
+
+### HTTP response details
+| Status code | Description | Response headers |
+|-------------|-------------|------------------|
+| **200** | Upload URL generated successfully |  -  |
+| **400** | Invalid request body or missing required fields |  -  |
+| **401** | Missing authentication session |  -  |
+| **403** | RLS policy denied upload access for this path |  -  |
+| **500** | Failed to generate presigned URL or store metadata |  -  |
+
+[[Back to top]](#) [[Back to API list]](../README.md#api-endpoints) [[Back to Model list]](../README.md#models) [[Back to README]](../README.md)
+