All Products
Search
Document Center

ApsaraMQ for MQTT:DeleteCustomAuthPermission

Last Updated:Jul 31, 2025

Deletes permissions on a topic.

Debugging

You can run this interface directly in OpenAPI Explorer, saving you the trouble of calculating signatures. After running successfully, OpenAPI Explorer can automatically generate SDK code samples.

Authorization information

The following table shows the authorization information corresponding to the API. The authorization information can be used in the Action policy element to grant a RAM user or RAM role the permissions to call this API operation. Description:

  • Operation: the value that you can use in the Action element to specify the operation on a resource.
  • Access level: the access level of each operation. The levels are read, write, and list.
  • Resource type: the type of the resource on which you can authorize the RAM user or the RAM role to perform the operation. Take note of the following items:
    • For mandatory resource types, indicate with a prefix of * .
    • If the permissions cannot be granted at the resource level, All Resources is used in the Resource type column of the operation.
  • Condition Key: the condition key that is defined by the cloud service.
  • Associated operation: other operations that the RAM user or the RAM role must have permissions to perform to complete the operation. To complete the operation, the RAM user or the RAM role must have the permissions to perform the associated operations.
OperationAccess levelResource typeCondition keyAssociated operation
mq:DeleteCustomAuthPermissiondelete
*Instance
acs:mq:{#regionId}:{#accountId}:{#InstanceId}
    none
none

Request parameters

ParameterTypeRequiredDescriptionExample
InstanceIdstringYes

The ID of the ApsaraMQ for MQTT instance.

mqtt-cn-0pp1ldu****
IdentityTypestringYes

The identity type. Valid values:

  • USER
  • CLIENT
USER
IdentitystringYes

The username or client ID.

test
TopicstringYes

The topic on which you want to grant permissions. Multi-level topics and Wildcard characters are supported.

test/t1

Response parameters

ParameterTypeDescriptionExample
object

The response schema.

RequestIdstring

The request ID.

34063BCA-0946-49C1-B824-2ED2C905****
Codeinteger

The HTTP status code.

200
Successboolean

Indicates whether the request is successful. Valid values: true and false.

True
Messagestring

The message returned.

operation success.

Examples

Sample success responses

JSONformat

{
  "RequestId": "34063BCA-0946-49C1-B824-2ED2C905****",
  "Code": 200,
  "Success": true,
  "Message": "operation success."
}

Error codes

HTTP status codeError codeError message
400InstancePermissionCheckFailedAn error occurred while validating the permissions of the instance. Please verify the account that created the instance and its permissions settings.
400InvalidParameter.%sAn error occurred while validating the parameter. The parameter may be missing or invalid.
404ApiNotSupportThe specified API is not supported.

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

Change history

Change timeSummary of changesOperation
No change history