All Products
Search
Document Center

ApsaraMQ for MQTT:GetDeviceCredential

Last Updated:Aug 22, 2024

Queries the access credential of a device. If unique-certificate-per-device authentication is used as the authentication method on an ApsaraMQ for MQTT broker, an access credential that you apply for in advance is required for authentication when you connect your device to the broker. The connection can be established only after the authentication is passed.

Operation description

  • You can call this operation up to 500 times per second per account. If the limit is exceeded, throttling is triggered. We recommend that you take note of this limit when you call this operation. For more information, see Limits on QPS.
  • Each successful call to the GetDeviceCredential operation increases the messaging transactions per second (TPS) by one. This affects the billing of your instance. For more information, see Billing rules.

Debugging

OpenAPI Explorer automatically calculates the signature value. For your convenience, we recommend that you call this operation in OpenAPI Explorer.

Authorization information

There is currently no authorization information disclosed in the API.

Request parameters

ParameterTypeRequiredDescriptionExample
ClientIdstringYes

The client ID of the device whose access credential you want to query.

GID_test@@@test
InstanceIdstringYes

The ID of the ApsaraMQ for MQTT instance. The ID must be consistent with the ID of the instance that the ApsaraMQ for MQTT client uses. You can obtain the instance ID on the Instance Details page that corresponds to the instance in the ApsaraMQ for MQTT console.

post-cn-0pp12gl****
Note For information about other parameters, see Common parameters and Endpoints .

Response parameters

ParameterTypeDescriptionExample
object
RequestIdstring

The request ID. This parameter is a common parameter.

E4581CCF-62AF-44D9-B5B4-D1DQDC0E****
DeviceCredentialobject

The information about the access credential of the device.

UpdateTimelong

The timestamp that indicates when the access credential of the device was last updated. The value of this parameter is a UNIX timestamp in milliseconds.

1605541382000
DeviceAccessKeyIdstring

The AccessKey ID of the device.

DC.Z5fXh9sRRVufyLi6wo****
CreateTimelong

The timestamp that indicates when the access credential of the device was created. Unit: milliseconds.

1605541382000
InstanceIdstring

The ID of the ApsaraMQ for MQTT instance.

post-cn-0pp12gl****
DeviceAccessKeySecretstring

The AccessKey secret of the device.

DC.BJMkn4eMQJK2vaApTS****
ClientIdstring

The client ID of the device.

GID_test@@@test

Examples

Sample success responses

JSONformat

{
  "RequestId": "E4581CCF-62AF-44D9-B5B4-D1DQDC0E****",
  "DeviceCredential": {
    "UpdateTime": 1605541382000,
    "DeviceAccessKeyId": "DC.Z5fXh9sRRVufyLi6wo****",
    "CreateTime": 1605541382000,
    "InstanceId": "post-cn-0pp12gl****",
    "DeviceAccessKeySecret": "DC.BJMkn4eMQJK2vaApTS****",
    "ClientId": "GID_test@@@test"
  }
}

Error codes

HTTP status codeError codeError message
400ApplyTokenOverFlowYou have applied for tokens too many times. Please try again later.
400CheckAccountInfoFailedAn error occurred while checking the account information by the STS token.
400InstancePermissionCheckFailedAn error occurred while validating the permissions of the instance. Please verify the account that created the instance and its permissions settings.
400ParameterCheckFailedAn error occurred while validating the parameters. The parameters may be missing or invalid.
400PermissionCheckFailedAn error occurred while validating the resource permissions. Please check the account that created the instance, topic, and GroupId, and check their permission settings.
400InvalidParameter.%sAn error occurred while validating the parameter. The parameter may be missing or invalid.
404ApiNotSupportThe specified API is not supported.
500InternalErrorAn error occurred while processing your request. Try again later.
500SystemOverFlowAn error occurred while processing your request. Please try again.

For a list of error codes, visit the Service error codes.

Change history

Change timeSummary of changesOperation
2024-04-25The Error code has changedView Change Details