Cloud Run
Feature Introduction
This series of open APIs provides the ability to interface with CloudBase Run. Through these APIs you can invoke CloudBase Run services within an environment, with support for both SSE (Server-Sent Event) and WebSocket requests.
Access Guide
Calling the following APIs requires an AccessToken in the format Authorization: Bearer <token>. For details on how to obtain the token, refer to https://docs.cloudbase.net/http-api/basic/access-token.
HTTP Status Codes
Depending on the response result, status codes 2xx, 4xx, or 5xx may appear.
Error Codes
The following table lists the error codes specific to this series of APIs. For the complete list, refer to https://docs.cloudbase.net/error-code/service.
| Error Code | Description |
| SERVICE_NOT_FOUND | The specified service was not found |
| SERVICE_TIMEOUT | The CloudBase Run service call timed out |
| SERVICE_FORBIDDEN | Access to the CloudBase Run service was denied, possibly due to permission configuration or service status issues |
| SERVICE_NOT_READY | The CloudBase Run service is not ready |
| SERVICE_VERSION_NOT_FOUND | No matching CloudBase Run service version was found |
| SERVICE_ENDPOINT_NOT_FOUND | No available endpoint was found for the CloudBase Run service |
| SERVICE_LB_STATUS_ABNORMAL | The load balancer status of the CloudBase Run service is abnormal; try creating a new version |
| SERVICE_RESOURCE_NOT_FOUND | No resources associated with the service were found |
| SERVICE_CHARGE_OVERDUE | Service is suspended due to overdue payment. Please recharge in time. |
Authentication
- HTTP: Bearer Auth
- API Key: APIKey
The token corresponding to the environment ID is obtained using login authentication (v2)
| Security Scheme Type: | http |
|---|---|
| HTTP Authorization Scheme: | bearer |
Tencent Cloud 3.0 signature that starts with TC3-HMAC-SHA256, with Timestamp and Token appended to the end of the signature
| Security Scheme Type: | apiKey |
|---|---|
| Header parameter name: | Authorization |