メニュー
Use when you need to implement CloudBase Auth v2 over raw HTTP endpoints (login/signup, tokens, user operations) from backends or scripts that are not using the Web or Node SDKs.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/TencentCloudBase/awesome-cloudbase-examples --skill auth-http-api-cloudbaseコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SOC 職業分類に基づく
SKILL.md を表示中
| name | auth-http-api-cloudbase |
| description | Use when you need to implement CloudBase Auth v2 over raw HTTP endpoints (login/signup, tokens, user operations) from backends or scripts that are not using the Web or Node SDKs. |
| alwaysApply | false |
Use this skill whenever you need to call CloudBase Auth via raw HTTP APIs, for example:
Do not use this skill for:
@cloudbase/js-sdk@2.x (use CloudBase Web Auth skill)@cloudbase/node-sdk (use CloudBase Node Auth skill)Clarify the scenario
env – CloudBase environment IDclientId / clientSecret – HTTP auth client credentialsSet common variables once
Pick a scenario from this file
Never invent endpoints or fields
/source-of-truth/auth/http-api/登录认证接口.info.mdx and the specific *.api.mdx files.Base URL pattern
https://${env}.ap-shanghai.tcb-api.tencentcloudapi.com/auth/v1/...Common headers
x-device-id – device or client identifierx-request-id – unique request ID for tracingAuthorization – Bearer <access_token> for user endpoints-u clientId:clientSecret) for client-credential style endpointsReusable shell variables
env="your-env-id"
deviceID="backend-service-1"
requestID="$(uuidgen || echo manual-request-id)"
clientId="your-client-id"
clientSecret="your-client-secret"
base="https://${env}.ap-shanghai.tcb-api.tencentcloudapi.com/auth/v1"
access_token and refresh_token.Authorization: Bearer ${accessToken}.verification endpoints before sign-up.curl "${base}/signin" \
-X POST \
-H "x-device-id: ${deviceID}" \
-H "x-request-id: ${requestID}" \
-u "${clientId}:${clientSecret}" \
--data-raw '{"username":"test@example.com","password":"your password"}'
access_token, refresh_token, and user info.curl "${base}/verification" \
-X POST \
-H "x-device-id: ${deviceID}" \
-H "x-request-id: ${requestID}" \
-u "${clientId}:${clientSecret}" \
--data-raw '{"phone_number":"+86 13800000000"}'
curl "${base}/verification/verify" \
-X POST \
-H "x-device-id: ${deviceID}" \
-H "x-request-id: ${requestID}" \
-u "${clientId}:${clientSecret}" \
--data-raw '{"verification_code":"000000","verification_id":"<from previous step>"}'
curl "${base}/signup" \
-X POST \
-H "x-device-id: ${deviceID}" \
-H "x-request-id: ${requestID}" \
-u "${clientId}:${clientSecret}" \
--data-raw '{
"phone_number":"+86 13800000000",
"verification_code":"000000",
"verification_token":"<from verify>",
"name":"手机用户",
"password":"password",
"username":"username"
}'
curl "${base}/signin-anonymously" \
-X POST \
-H "x-device-id: ${deviceID}" \
-H "x-request-id: ${requestID}" \
-u "${clientId}:${clientSecret}" \
--data-raw '{}'
curl "${base}/token" \
-X POST \
-H "x-device-id: ${deviceID}" \
-H "x-request-id: ${requestID}" \
-u "${clientId}:${clientSecret}" \
--data-raw '{"grant_type":"refresh_token","refresh_token":"<refresh_token>"}'
curl "${base}/token/introspect?token=${accessToken}" \
-H "x-request-id: ${requestID}" \
-u "${clientId}:${clientSecret}"
curl "${base}/revoke" \
-X POST \
-H "x-request-id: ${requestID}" \
-u "${clientId}:${clientSecret}" \
--data-raw '{"token":"${accessToken}"}'
# Get current user
curl "${base}/user/me" \
-H "Authorization: Bearer ${accessToken}"
# Change password
curl "${base}/user/password" \
-X PATCH \
-H "Authorization: Bearer ${accessToken}" \
--data-raw '{"old_password":"old","new_password":"new"}'
DELETE ${base}/user/me – delete current user.${base}/user/providers plus bind/unbind APIs – manage third-party accounts.