You can call the Subscribe operation to create a subscription for a topic.
Try it now
Test
RAM authorization
|
Action |
Access level |
Resource type |
Condition key |
Dependent action |
|
mns:Subscribe |
update |
*Subscription
|
|
None |
Request parameters
|
Parameter |
Type |
Required |
Description |
Example |
| TopicName |
string |
Yes |
The name of the topic. |
topic****1 |
| SubscriptionName |
string |
Yes |
The name of the subscription. |
testSubscription |
| PushType |
string |
Yes |
The type of the endpoint.
|
queue |
| Endpoint |
string |
Yes |
The endpoint that receives messages in this subscription. The endpoint format varies based on the endpoint type:
|
http://*****.com/uri1/xxx |
| NotifyStrategy |
string |
No |
The retry policy for pushing messages to the endpoint when an error occurs. Valid values:
|
BACKOFF_RETRY |
| NotifyContentFormat |
string |
No |
The format of the message that is pushed to the endpoint. Valid values:
|
XML |
| MessageTag |
string |
No |
The tag for message filtering in this subscription. Only messages with the same tag are pushed. The value is a string of up to 16 characters. By default, messages are not filtered. |
important |
| DlqPolicy |
object |
No |
The dead-letter queue policy. |
|
| Enabled |
boolean |
No |
Specifies whether to enable dead-letter message delivery. |
true |
| DeadLetterTargetQueue |
string |
No |
The target queue for dead-letter message delivery. |
deadLetterTargetQueue |
| TenantRateLimitPolicy |
object |
No |
||
| Enabled |
boolean |
No |
||
| MaxReceivesPerSecond |
integer |
No |
||
| StsRoleArn |
string |
No |
||
| DmAttributes |
object |
No |
||
| AccountName |
string |
No |
||
| Subject |
string |
No |
||
| DysmsAttributes |
object |
No |
||
| TemplateCode |
string |
No |
||
| SignName |
string |
No |
||
| KafkaAttributes |
object |
No |
||
| BusinessMode |
string |
No |
Response elements
|
Element |
Type |
Description |
Example |
|
object |
|||
| RequestId |
string |
The request ID. |
06273500-249F-5863-121D-74D51123**** |
| Code |
integer |
The response code. |
200 |
| Status |
string |
The status of the response. |
Success |
| Message |
string |
The response message. |
operation success |
| Success |
boolean |
Indicates whether the request was successful. |
true |
| Data |
string |
The response data. |
{'Code': 200, 'Success': True} |
Examples
Success response
JSON format
{
"RequestId": "06273500-249F-5863-121D-74D51123****",
"Code": 200,
"Status": "Success",
"Message": "operation success",
"Success": true,
"Data": "{'Code': 200, 'Success': True}"
}
Error codes
See Error Codes for a complete list.
Release notes
See Release Notes for a complete list.