http-api-cloudbase

You can call CloudBase APIs via raw HTTP by selecting the correct environment base URL, setting up Bearer authentication in the Authorization header, and looking up the OpenAPI spec to ensure your endpoint paths and parameters match documented contracts.

The best way to invoke CloudBase database and cloud functions from a non-Node backend is using official raw HTTP endpoints, applying RESTful operations for MySQL databases and specific HTTP routes for functions while authenticating with an AccessToken or API Key.

To set up authentication headers for CloudBase REST API requests, choose an AccessToken, API Key, or Publishable Key, and send the correct Authorization header format containing the Bearer token to verify your access to the platform features.

Yes, you can use raw HTTP API requests to manage CloudBase storage and CloudRun in native apps, as this approach bypasses SDK requirements by directly targeting gateway base URLs with explicit environment selection and valid authentication.

You should always use the CloudBase OpenAPI spec lookup via searchKnowledgeBase before making raw HTTP requests to ensure endpoint paths, parameters, and schemas match documented contracts, reducing guesswork about URLs and preventing API integration errors.

Yes, calling CloudBase functions via HTTP works for both regions by using the correct gateway base URL patterns specific to domestic and international environments to route requests to the intended platform feature reliably.