All Products
Search

This Product

    Simple Message Queue (formerly MNS):Subscribe

    Document Center

    Simple Message Queue (formerly MNS):Subscribe

    Last Updated:Jan 30, 2026

    Creates a subscription for a topic.

    Try it now

    Try this API in OpenAPI Explorer, no manual signing needed. Successful calls auto-generate SDK code matching your parameters. Download it with built-in credential security for local usage.

    Test

    RAM authorization

    The table below describes the authorization required to call this API. You can define it in a Resource Access Management (RAM) policy. The table's columns are detailed below:

    • Action: The actions can be used in the Action element of RAM permission policy statements to grant permissions to perform the operation.

    • API: The API that you can call to perform the action.

    • Access level: The predefined level of access granted for each API. Valid values: create, list, get, update, and delete.

    • Resource type: The type of the resource that supports authorization to perform the action. It indicates if the action supports resource-level permission. The specified resource must be compatible with the action. Otherwise, the policy will be ineffective.

      • For APIs with resource-level permissions, required resource types are marked with an asterisk (*). Specify the corresponding Alibaba Cloud Resource Name (ARN) in the Resource element of the policy.

      • For APIs without resource-level permissions, it is shown as All Resources. Use an asterisk (*) in the Resource element of the policy.

    • Condition key: The condition keys defined by the service. The key allows for granular control, applying to either actions alone or actions associated with specific resources. In addition to service-specific condition keys, Alibaba Cloud provides a set of common condition keys applicable across all RAM-supported services.

    • Dependent action: The dependent actions required to run the action. To complete the action, the RAM user or the RAM role must have the permissions to perform all dependent actions.

    Action

    Access level

    Resource type

    Condition key

    Dependent action

    mns:Subscribe

    update

    *Subscription

    acs:mns:{#regionId}:{#accountId}:/topics/{#TopicName}/subscriptions/{#SubscriptionName}
    • mns:PushType
    		 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. Valid values:

    • http: HTTP push.

    • queue: Queue push.

    • mpush: Mobile Push.

    • alisms: Alibaba Cloud text message push.

    • email: Email push.

    queue
    Endpoint

    string

    Yes

    The endpoint address that receives messages for this subscription. The format varies based on the endpoint type:

    • HTTP: http(s)://{URL}

    • Queue: {QueueName}

    • Mobile Push: {AppKey}

    • Alibaba Cloud text message: {phoneNumber}

    • Email: {emailAddress}

    http://*****.com/uri1/xxx
    NotifyStrategy

    string

    No

    The retry policy for message push failures to the endpoint. Valid values:

    • BACKOFF_RETRY: Backoff retry.

    • EXPONENTIAL_DECAY_RETRY: Exponential decay retry.

    BACKOFF_RETRY
    NotifyContentFormat

    string

    No

    The format of the message to push to the endpoint. Valid values:

    • XML

    • JSON

    • SIMPLIFIED

    XML
    MessageTag

    string

    No

    The tag for filtering messages. Only messages that have a matching tag are pushed. The tag can be up to 16 characters long.

    By default, messages are not filtered.

    important
    DlqPolicy

    object

    No

    The dead-letter queue policy.

    Enabled

    boolean

    No

    Specifies whether to deliver dead-letter messages.

    true
    DeadLetterTargetQueue

    string

    No

    The destination queue for dead-letter messages.

    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 ID of the request.

    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.