When to use this skill

Use this skill whenever you need to call CloudBase platform features via raw HTTP APIs, for example:

• Non-Node backends (Go, Python, Java, PHP, etc.)

• Integration tests or admin scripts that use curl or language HTTP clients

• Direct database operations via MySQL RESTful API

• Cloud function invocation via HTTP

• Any scenario where SDKs are not available or not preferred

Do not use this skill for:

• Frontend Web apps using @cloudbase/js-sdk (use CloudBase Web skills)

• Node.js code using @cloudbase/node-sdk (use CloudBase Node skills)

• Authentication flows (use CloudBase Auth HTTP API skill for auth-specific endpoints)

How to use this skill (for a coding agent)

Clarify the scenario

• Confirm this code will call HTTP endpoints directly (not SDKs).

• Ask for:

• env – CloudBase environment ID

• Authentication method (AccessToken, API Key, or Publishable Key)

• Confirm which CloudBase feature is needed (database, functions, storage, etc.).

• For user authentication: If no specific method is requested, always default to Phone SMS Verification - it's the most user-friendly and secure option for Chinese users.

Determine the base URL

• Use the correct domain based on region (domestic vs. international).

• Default is domestic Shanghai region.

Set up authentication

• Choose appropriate authentication method based on use case.

• Add Authorization: Bearer <token> header to requests.

Reference OpenAPI Swagger documentation

• MUST use searchKnowledgeBase tool to get OpenAPI specifications

• Use the tool with mode=openapi and specify the apiName :

• mysqldb

• MySQL RESTful API

• functions

• Cloud Functions API

• auth

• Authentication API

• cloudrun

• CloudRun API

• storage

• Storage API

• Example: searchKnowledgeBase({ mode: "openapi", apiName: "mysqldb" })

• Parse the returned YAML content to understand exact endpoint paths, parameters, request/response schemas

• Never invent endpoints or parameters - always reference the swagger documentation

Overview

CloudBase HTTP API is a set of interfaces for accessing CloudBase platform features via HTTP protocol, supporting database, user authentication, cloud functions, cloud hosting, cloud storage, AI, and more.

OpenAPI Swagger Documentation

⚠️ IMPORTANT: Always use searchKnowledgeBase tool to get OpenAPI Swagger specifications

Before implementing any HTTP API calls, you should:

Use searchKnowledgeBase tool to get OpenAPI documentation:

searchKnowledgeBase({ mode: "openapi", apiName: "<api-name>" })

Available API names:

• mysqldb

• MySQL RESTful API

• functions

• Cloud Functions API

• auth

• Authentication API

• cloudrun

• CloudRun API

• storage

• Storage API

Parse and use the swagger documentation:

• Extract exact endpoint paths and HTTP methods

• Understand required and optional parameters

• Review request/response schemas

• Check authentication requirements

• Verify error response formats

Never invent API endpoints or parameters - always base your implementation on the official swagger documentation.

Prerequisites

Before starting, ensure you have:

• CloudBase environment created and activated

• Authentication credentials (AccessToken, API Key, or Publishable Key)

Authentication and Authorization

CloudBase HTTP API requires authentication. Choose the appropriate method based on your use case:

AccessToken Authentication

Applicable environments: Client/Server

User permissions: Logged-in user permissions

How to get: Use searchKnowledgeBase({ mode: "openapi", apiName: "auth" }) to get the Authentication API specification

API Key

Applicable environments: Server

User permissions: Administrator permissions

• Validity: Long-term valid

• How to get: Get from CloudBase Platform/ApiKey Management Page

⚠️ Warning: Tokens are critical credentials for identity authentication. Keep them secure. API Key must NOT be used in client-side code.

Publishable Key

Applicable environments: Client/Server

User permissions: Anonymous user permissions

• Validity: Long-term valid

• How to get: Get from CloudBase Platform/ApiKey Management Page

💡 Note: Can be exposed in browsers, used for requesting publicly accessible resources, effectively reducing MAU.

API Endpoint URLs

CloudBase HTTP API uses unified domain names for API calls. The domain varies based on the environment's region.

Domestic Regions

For environments in domestic regions like Shanghai (ap-shanghai ), use:

https://{your-env}.api.tcloudbasegateway.com

Replace {your-env} with the actual environment ID. For example, if environment ID is cloud1-abc :

https://cloud1-abc.api.tcloudbasegateway.com

International Regions

For environments in international regions like Singapore (ap-singapore ), use:

https://{your-env}.api.intl.tcloudbasegateway.com

Replace {your-env} with the actual environment ID. For example, if environment ID is cloud1-abc :

https://cloud1-abc.api.intl.tcloudbasegateway.com

Using Authentication in Requests

Add the token to the request header:

Authorization: Bearer <access_token/apikey/publishable_key>

:::warning Note

When making actual calls, replace the entire part including angle brackets (< > ) with your obtained key. For example, if the obtained key is eymykey , fill it as:

Authorization: Bearer eymykey

:::

Usage Examples

Cloud Function Invocation Example

curl -X POST "https://your-env-id.api.tcloudbasegateway.com/v1/functions/YOUR_FUNCTION_NAME"
-H "Authorization: Bearer <access_token/apikey/publishable_key>"
-H "Content-Type: application/json"
-d '{"name": "张三", "age": 25}'

For detailed API specifications, always download and reference the OpenAPI Swagger files mentioned above.

MySQL RESTful API

The MySQL RESTful API provides all MySQL database operations via HTTP endpoints.

Base URL Patterns

Support three domain access patterns:

• https://{envId}.api.tcloudbasegateway.com/v1/rdb/rest/{table}

• https://{envId}.api.tcloudbasegateway.com/v1/rdb/rest/{schema}/{table}

• https://{envId}.api.tcloudbasegateway.com/v1/rdb/rest/{instance}/{schema}/{table}

Where:

• envId is the environment ID

• instance is the database instance identifier

• schema is the database name

• table is the table name

If using the system database, recommend pattern 1.

Request Headers

Header Parameter Description Example

Accept application/json , application/vnd.pgrst.object+json

Control data return format Accept: application/json

Content-Type application/json , application/vnd.pgrst.object+json

Request content type Content-Type: application/json

Prefer Operation-dependent feature values

• return=representation Write operation, return data body and headers- return=minimal Write operation, return headers only (default)- count=exact Read operation, specify count- resolution=merge-duplicates Upsert operation, merge conflicts- resolution=ignore-duplicates Upsert operation, ignore conflicts Prefer: return=representation

Authorization Bearer <token>

Authentication token Authorization: Bearer <access_token>

Query Records

GET /v1/rdb/rest/{table}

Query Parameters:

• select : Field selection, supports * or field list, supports join queries like class_id(grade,class_number)

• limit : Limit return count

• offset : Offset for pagination

• order : Sort field, format field.asc or field.desc

Example:

Before URL encoding

curl -X GET 'https://your-env.api.tcloudbasegateway.com/v1/rdb/rest/course?select=name,position&#x26;name=like.%张三%&#x26;title=eq.文章标题'
-H "Authorization: Bearer <access_token>"

After URL encoding

curl -X GET 'https://your-env.api.tcloudbasegateway.com/v1/rdb/rest/course?select=name,position&#x26;name=like.%%E5%BC%A0%E4%B8%89%&#x26;title=eq.%E6%96%87%E7%AB%A0%E6%A0%87%E9%A2%98'
-H "Authorization: Bearer <access_token>"

Response Headers:

• Content-Range : Data range, e.g., 0-9/100 (0=start, 9=end, 100=total)

Insert Records

POST /v1/rdb/rest/{table}

Request Body: JSON object or array of objects

💡 Note about _openid : When a user is logged in (using AccessToken authentication), the _openid field is automatically populated by the server with the current user's identity. You do NOT need to manually set this field in INSERT operations - the server will fill it automatically based on the authenticated user's session.

Example:

curl -X POST 'https://your-env.api.tcloudbasegateway.com/v1/rdb/rest/course'
-H "Authorization: Bearer <access_token>"
-H "Content-Type: application/json"
-H "Prefer: return=representation"
-d '{ "name": "数学", "position": 1 }'

Update Records

PATCH /v1/rdb/rest/{table}

Request Body: JSON object with fields to update

Example:

curl -X PATCH 'https://your-env.api.tcloudbasegateway.com/v1/rdb/rest/course?id=eq.1'
-H "Authorization: Bearer <access_token>"
-H "Content-Type: application/json"
-H "Prefer: return=representation"
-d '{ "name": "高等数学", "position": 2 }'

⚠️ Important: UPDATE requires a WHERE clause. Use query parameters like ?id=eq.1 to specify conditions.

Delete Records

DELETE /v1/rdb/rest/{table}

Example:

curl -X DELETE 'https://your-env.api.tcloudbasegateway.com/v1/rdb/rest/course?id=eq.1'
-H "Authorization: Bearer <access_token>"

⚠️ Important: DELETE requires a WHERE clause. Use query parameters to specify conditions.

Error Codes and HTTP Status Codes

Error Code HTTP Status Description

INVALID_PARAM 400 Invalid request parameters

INVALID_REQUEST 400 Invalid request content: missing permission fields, SQL execution errors, etc.

INVALID_REQUEST 406 Does not meet single record return constraint

PERMISSION_DENIED 401, 403 Authentication failed: 401 for identity authentication failure, 403 for authorization failure

RESOURCE_NOT_FOUND 404 Database instance or table not found

SYS_ERR 500 Internal system error

OPERATION_FAILED 503 Failed to establish database connection

RESOURCE_UNAVAILABLE 503 Database unavailable due to certain reasons

Response Format

All POST, PATCH, DELETE operations: Request header with Prefer: return=representation means there is a response body, without it means only response headers.

POST, PATCH, DELETE response bodies are usually JSON array type [] . If request header specifies Accept: application/vnd.pgrst.object+json , it will return JSON object type {} .

If Accept: application/vnd.pgrst.object+json is specified but data quantity is greater than 1, an error will be returned.

URL Encoding

When making requests, please perform URL encoding. For example:

Original request:

curl -i -X GET 'https://{{host}}/v1/rdb/rest/course?select=name,position&name=like.%张三%&title=eq.文章标题'

Encoded request:

curl -i -X GET 'https://{{host}}/v1/rdb/rest/course?select=name,position&name=like.%%E5%BC%A0%E4%B8%89%&title=eq.%E6%96%87%E7%AB%A0%E6%A0%87%E9%A2%98'

Online Debugging Tool

CloudBase platform provides an online debugging tool where you can test API interfaces without writing code:

• Visit the API documentation page

• Find the debugging tool entry

• Fill in environment ID and request parameters

• Click send request to view response

API Documentation References

⚠️ Always use searchKnowledgeBase tool to get OpenAPI Swagger specifications:

Use searchKnowledgeBase({ mode: "openapi", apiName: "<api-name>" }) with these API names:

• auth

• Authentication API

• mysqldb

• MySQL RESTful API

• functions

• Cloud Functions API

• cloudrun

• CloudRun API

• storage

• Storage API

How to use the OpenAPI documentation:

• Call searchKnowledgeBase tool with the appropriate apiName

• Parse the returned YAML content to extract:

• Endpoint paths (e.g., /v1/rdb/rest/{table} )

• HTTP methods (GET, POST, PATCH, DELETE)

• Path parameters, query parameters, request body schemas

• Response schemas and status codes

• Authentication requirements

• Use the extracted information to construct accurate API calls

• Never assume endpoint structure - always verify against swagger documentation

Common Patterns

Reusable Shell Variables

env="your-env-id" token="your-access-token-or-api-key" base="https://${env}.api.tcloudbasegateway.com"

Common Request Pattern

curl -X GET "${base}/v1/rdb/rest/table_name"
-H "Authorization: Bearer ${token}"
-H "Content-Type: application/json"

Error Handling

Always check HTTP status codes and error response format:

{ "code": "ERROR_CODE", "message": "Error message details", "requestId": "request-unique-id" }

Common Authentication Flows

🌟 IMPORTANT: Default Authentication Method

When no specific signup/signin method is specified by the user, ALWAYS use Phone SMS Verification as the default and recommended method. It is:

• ✅ The most user-friendly for Chinese users

• ✅ No password to remember

• ✅ Works for both new users (registration) and existing users (login)

• ✅ Most secure with OTP verification

• ✅ Supported by default in CloudBase

Phone Number Verification Code Login (Native Apps) ⭐ RECOMMENDED

This is the preferred authentication flow for native mobile apps (iOS/Android/Flutter/React Native):

┌─────────────────────────────────────────────────────────────────────────┐ │ Step 1: Send Verification Code │ │ POST /auth/v1/verification │ │ Body: { "phone_number": "+86 13800138000", "target": "ANY" } │ │ ⚠️ IMPORTANT: phone_number MUST include "+86 " prefix WITH SPACE │ │ Response: { "verification_id": "xxx", "expires_in": 600 } │ │ 📝 SAVE verification_id for next step! │ └─────────────────────────────────────────────────────────────────────────┘ ↓ ┌─────────────────────────────────────────────────────────────────────────┐ │ Step 2: Verify Code │ │ POST /auth/v1/verification/verify │ │ Body: { "verification_id": "<saved_id>", "verification_code": "123456" }│ │ Response: { "verification_token": "xxx" } │ │ 📝 SAVE verification_token for login! │ └─────────────────────────────────────────────────────────────────────────┘ ↓ ┌─────────────────────────────────────────────────────────────────────────┐ │ Step 3: Sign In with Token │ │ POST /auth/v1/signin │ │ Body: { "verification_token": "<saved_token>" } │ │ Response: { "access_token": "xxx", "refresh_token": "xxx" } │ └─────────────────────────────────────────────────────────────────────────┘

⚠️ Critical Notes:

• Phone number format: MUST be "+86 13800138000" with space after country code

• Save verification_id : Returned from Step 1, required for Step 2

• Save verification_token : Returned from Step 2, required for Step 3

Best Practices

• Always use URL encoding for query parameters containing special characters

• Include WHERE clauses for UPDATE and DELETE operations

• Use appropriate Prefer headers to control response format

• Handle errors gracefully by checking status codes and error responses

• Keep tokens secure - never expose API Keys in client-side code

• Use appropriate authentication method based on your use case:

• AccessToken for user-specific operations

• API Key for server-side admin operations

• Publishable Key for public/anonymous access

• Phone number format: Always use international format with space: "+86 13800138000"

• Verification flow: Save verification_id from send step, use it in verify step