CloudBase official HTTP API client guide. This skill should be used when backends, scripts, or non-SDK clients must call CloudBase platform APIs over raw HTTP instead of using a platform SDK or MCP management tool.
If this environment only installed the current skill, start from the CloudBase main entry and use the published cloudbase/references/... paths for sibling skills.
https://cnb.cool/tencent/cloud/cloudbase/cloudbase-skills/-/git/raw/main/skills/cloudbase/SKILL.mdhttps://cnb.cool/tencent/cloud/cloudbase/cloudbase-skills/-/git/raw/main/skills/cloudbase/references/http-api/SKILL.mdKeep local references/... paths for files that ship with the current skill directory. When this file points to a sibling skill such as auth-tool or web-development, use the standalone fallback URL shown next to that reference.
../auth-tool/SKILL.md (standalone fallback: https://cnb.cool/tencent/cloud/cloudbase/cloudbase-skills/-/git/raw/main/skills/cloudbase/references/auth-tool/SKILL.md)../relational-database-tool/SKILL.md (standalone fallback: https://cnb.cool/tencent/cloud/cloudbase/cloudbase-skills/-/git/raw/main/skills/cloudbase/references/relational-database-tool/SKILL.md)../cloud-functions/SKILL.md (standalone fallback: https://cnb.cool/tencent/cloud/cloudbase/cloudbase-skills/-/git/raw/main/skills/cloudbase/references/cloud-functions/SKILL.md) or ../cloudrun-development/SKILL.md (standalone fallback: https://cnb.cool/tencent/cloud/cloudbase/cloudbase-skills/-/git/raw/main/skills/cloudbase/references/cloudrun-development/SKILL.md)Use this skill whenever you need to call CloudBase platform features via raw HTTP APIs, for example:
Do not use this skill for:
@cloudbase/js-sdk (use CloudBase Web skills)@cloudbase/node-sdk (use CloudBase Node skills)Clarify the scenario
env – CloudBase environment IDDetermine the base URL
Set up authentication
Authorization: Bearer <token> header to requests.Reference OpenAPI Swagger documentation
searchKnowledgeBase tool to get OpenAPI specificationsmode=openapi and specify the apiName:
mysqldb - MySQL RESTful APIfunctions - Cloud Functions APIauth - Authentication APIcloudrun - CloudRun APIstorage - Storage APIsearchKnowledgeBase({ mode: "openapi", apiName: "mysqldb" })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.
⚠️ 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 APIfunctions - Cloud Functions APIauth - Authentication APIcloudrun - CloudRun APIstorage - Storage APIParse and use the swagger documentation:
Never invent API endpoints or parameters - always base your implementation on the official swagger documentation.
Before starting, ensure you have:
CloudBase HTTP API requires authentication. Choose the appropriate method based on your use case:
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
Applicable environments: Server
User permissions: Administrator permissions
⚠️ Warning: Tokens are critical credentials for identity authentication. Keep them secure. API Key must NOT be used in client-side code.
Applicable environments: Client/Server
User permissions: Anonymous user permissions
💡 Note: Can be exposed in browsers, used for requesting publicly accessible resources, effectively reducing MAU.
CloudBase HTTP API uses unified domain names for API calls. The domain varies based on the environment's region.
For environments in domestic regions like Shanghai (ap-shanghai), use: