http-api-cloudbase

You can call CloudBase functions using raw HTTP requests by utilizing OpenAPI definitions to discover endpoint paths and constructing proper authentication headers. This allows server-side backends and CLI tools to access platform features directly without needing the SDK.

The best way to access CloudBase database and storage via HTTP APIs is by following OpenAPI specifications to build correct requests. This method relies on precise endpoint paths and proper authentication headers to interact directly with the platform.

Yes, you can run integration tests for CloudBase features without the SDK by making direct HTTP API calls. By using OpenAPI definitions to validate request schemas and endpoints, your tests can interact with authentication, database, and storage services natively.

OpenAPI helps direct HTTP calls to CloudBase by providing the exact endpoint paths and request schemas needed. It uses searchKnowledgeBase to discover definitions, ensuring your raw HTTP interactions for database and authentication endpoints are built correctly.

You should use raw HTTP endpoints instead of the CloudBase SDK in environments where SDKs are unavailable or unsuitable, such as specific server-side backends, integration tests, or CLI tools that require lightweight, direct HTTP access.

To authenticate raw HTTP requests to CloudBase platform features, you need to include proper authentication headers in your HTTP calls. The exact headers and endpoint paths are determined by referencing the OpenAPI definitions for the specific service.