From 48f6254910477be28b42cf257aec8a0f7c46f648 Mon Sep 17 00:00:00 2001 From: wanghuijuan738 Date: Thu, 6 Feb 2025 14:15:39 +0000 Subject: [PATCH] smn api 20250206 version: add information about mandatory Default protocol template. MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Reviewed-by: Daniel Kováč Co-authored-by: wanghuijuan738 Co-committed-by: wanghuijuan738 --- docs/smn/api-ref/ALL_META.TXT.json | 110 +++++++++---------- docs/smn/api-ref/CLASS.TXT.json | 2 +- docs/smn/api-ref/en-us_topic_0036017316.html | 8 +- docs/smn/api-ref/en-us_topic_0173558607.html | 2 +- docs/smn/api-ref/en-us_topic_0173558608.html | 6 +- docs/smn/api-ref/en-us_topic_0173593949.html | 2 +- docs/smn/api-ref/smn_api_510002.html | 2 +- docs/smn/api-ref/smn_api_53001.html | 13 ++- docs/smn/api-ref/smn_api_54003.html | 14 +-- docs/smn/api-ref/smn_api_56002.html | 10 +- docs/smn/api-ref/smn_api_56003.html | 2 +- docs/smn/api-ref/smn_api_56004.html | 2 +- docs/smn/api-ref/smn_api_56005.html | 2 +- docs/smn/api-ref/smn_api_66000.html | 2 +- 14 files changed, 89 insertions(+), 88 deletions(-) diff --git a/docs/smn/api-ref/ALL_META.TXT.json b/docs/smn/api-ref/ALL_META.TXT.json index 1ed030164..0d1d11960 100644 --- a/docs/smn/api-ref/ALL_META.TXT.json +++ b/docs/smn/api-ref/ALL_META.TXT.json @@ -15,7 +15,7 @@ { "documenttype":"api", "prodname":"smn", - "opensource":"false" + "opensource":"true;false" } ], "title":"API Usage Guidelines", @@ -34,7 +34,7 @@ { "documenttype":"api", "prodname":"smn", - "opensource":"false" + "opensource":"true;false" } ], "title":"APIs", @@ -53,7 +53,7 @@ { "documenttype":"api", "prodname":"smn", - "opensource":"false" + "opensource":"true;false" } ], "title":"Topic Operations", @@ -72,7 +72,7 @@ { "documenttype":"api", "prodname":"smn", - "opensource":"false" + "opensource":"true;false" } ], "title":"Creating a Topic", @@ -91,7 +91,7 @@ { "documenttype":"api", "prodname":"smn", - "opensource":"false" + "opensource":"true;false" } ], "title":"Updating a Topic", @@ -110,7 +110,7 @@ { "documenttype":"api", "prodname":"smn", - "opensource":"false" + "opensource":"true;false" } ], "title":"Querying Topics", @@ -129,7 +129,7 @@ { "documenttype":"api", "prodname":"smn", - "opensource":"false" + "opensource":"true;false" } ], "title":"Querying Details of a Topic", @@ -148,7 +148,7 @@ { "documenttype":"api", "prodname":"smn", - "opensource":"false" + "opensource":"true;false" } ], "title":"Querying a Topic Policy", @@ -167,7 +167,7 @@ { "documenttype":"api", "prodname":"smn", - "opensource":"false" + "opensource":"true;false" } ], "title":"Updating a Topic Policy", @@ -186,7 +186,7 @@ { "documenttype":"api", "prodname":"smn", - "opensource":"false" + "opensource":"true;false" } ], "title":"Deleting a Topic", @@ -205,7 +205,7 @@ { "documenttype":"api", "prodname":"smn", - "opensource":"false" + "opensource":"true;false" } ], "title":"Deleting a Specified Topic Policy", @@ -224,7 +224,7 @@ { "documenttype":"api", "prodname":"smn", - "opensource":"false" + "opensource":"true;false" } ], "title":"Deleting All Topic Policies", @@ -243,7 +243,7 @@ { "documenttype":"api", "prodname":"smn", - "opensource":"false" + "opensource":"true;false" } ], "title":"Subscription Operations", @@ -262,7 +262,7 @@ { "documenttype":"api", "prodname":"smn", - "opensource":"false" + "opensource":"true;false" } ], "title":"Adding a Subscription", @@ -281,7 +281,7 @@ { "documenttype":"api", "prodname":"smn", - "opensource":"false" + "opensource":"true;false" } ], "title":"Querying Subscriptions", @@ -300,7 +300,7 @@ { "documenttype":"api", "prodname":"smn", - "opensource":"false" + "opensource":"true;false" } ], "title":"Querying Subscriptions of a Specified Topic", @@ -319,7 +319,7 @@ { "documenttype":"api", "prodname":"smn", - "opensource":"false" + "opensource":"true;false" } ], "title":"Deleting a Subscription", @@ -338,7 +338,7 @@ { "documenttype":"api", "prodname":"smn", - "opensource":"false" + "opensource":"true;false" } ], "title":"Template Operations", @@ -357,7 +357,7 @@ { "documenttype":"api", "prodname":"smn", - "opensource":"false" + "opensource":"true;false" } ], "title":"Creating a Message Template", @@ -376,7 +376,7 @@ { "documenttype":"api", "prodname":"smn", - "opensource":"false" + "opensource":"true;false" } ], "title":"Modifying a Message Template", @@ -395,7 +395,7 @@ { "documenttype":"api", "prodname":"smn", - "opensource":"false" + "opensource":"true;false" } ], "title":"Querying Message Templates", @@ -414,7 +414,7 @@ { "documenttype":"api", "prodname":"smn", - "opensource":"false" + "opensource":"true;false" } ], "title":"Querying the Details of a Message Template", @@ -433,7 +433,7 @@ { "documenttype":"api", "prodname":"smn", - "opensource":"false" + "opensource":"true;false" } ], "title":"Deleting a Message Template", @@ -452,7 +452,7 @@ { "documenttype":"api", "prodname":"smn", - "opensource":"false" + "opensource":"true;false" } ], "title":"Message Publishing", @@ -471,7 +471,7 @@ { "documenttype":"api", "prodname":"smn", - "opensource":"false" + "opensource":"true;false" } ], "title":"Publishing Messages in the Text Format", @@ -490,7 +490,7 @@ { "documenttype":"api", "prodname":"smn", - "opensource":"false" + "opensource":"true;false" } ], "title":"Publishing Messages Using a Message Structure", @@ -509,7 +509,7 @@ { "documenttype":"api", "prodname":"smn", - "opensource":"false" + "opensource":"true;false" } ], "title":"Publishing Messages Using a Template", @@ -528,7 +528,7 @@ { "documenttype":"api", "prodname":"smn", - "opensource":"false" + "opensource":"true;false" } ], "title":"Resource Tag Operations", @@ -547,7 +547,7 @@ { "documenttype":"api", "prodname":"smn", - "opensource":"false" + "opensource":"true;false" } ], "title":"Adding a Tag", @@ -566,7 +566,7 @@ { "documenttype":"api", "prodname":"smn", - "opensource":"false" + "opensource":"true;false" } ], "title":"Querying Tags of a Topic", @@ -585,7 +585,7 @@ { "documenttype":"api", "prodname":"smn", - "opensource":"false" + "opensource":"true;false" } ], "title":"Querying Tags in a Specified Project", @@ -604,7 +604,7 @@ { "documenttype":"api", "prodname":"smn", - "opensource":"false" + "opensource":"true;false" } ], "title":"Querying Topics by Tag", @@ -623,7 +623,7 @@ { "documenttype":"api", "prodname":"smn", - "opensource":"false" + "opensource":"true;false" } ], "title":"Deleting a Tag", @@ -642,7 +642,7 @@ { "documenttype":"api", "prodname":"smn", - "opensource":"false" + "opensource":"true;false" } ], "title":"Adding or Deleting Tags in Batches", @@ -661,7 +661,7 @@ { "documenttype":"api", "prodname":"smn", - "opensource":"false" + "opensource":"true;false" } ], "title":"Version Querying", @@ -680,7 +680,7 @@ { "documenttype":"api", "prodname":"smn", - "opensource":"false" + "opensource":"true;false" } ], "title":"Listing All SMN API Versions", @@ -699,7 +699,7 @@ { "documenttype":"api", "prodname":"smn", - "opensource":"false" + "opensource":"true;false" } ], "title":"Querying the SMN API v2 Version", @@ -718,7 +718,7 @@ { "documenttype":"api", "prodname":"smn", - "opensource":"false" + "opensource":"true;false" } ], "title":"Permissions Policies and Supported Actions", @@ -737,7 +737,7 @@ { "documenttype":"api", "prodname":"smn", - "opensource":"false" + "opensource":"true;false" } ], "title":"Permissions Policies and Supported Actions", @@ -756,7 +756,7 @@ { "documenttype":"api", "prodname":"smn", - "opensource":"false" + "opensource":"true;false" } ], "title":"Topic Operations", @@ -775,7 +775,7 @@ { "documenttype":"api", "prodname":"smn", - "opensource":"false" + "opensource":"true;false" } ], "title":"Template Operations", @@ -794,7 +794,7 @@ { "documenttype":"api", "prodname":"smn", - "opensource":"false" + "opensource":"true;false" } ], "title":"Tag Operations", @@ -813,7 +813,7 @@ { "documenttype":"api", "prodname":"smn", - "opensource":"false" + "opensource":"true;false" } ], "title":"Message Publishing", @@ -826,16 +826,16 @@ "code":"44", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"api", - "kw":"Sending an Application Message,Permissions Policies and Supported Actions,API Reference", + "kw":"Sending an Application Message (Deprecated),Permissions Policies and Supported Actions,API Reference", "search_title":"", "metedata":[ { "documenttype":"api", "prodname":"smn", - "opensource":"false" + "opensource":"true;false" } ], - "title":"Sending an Application Message", + "title":"Sending an Application Message (Deprecated)", "githuburl":"" }, { @@ -851,7 +851,7 @@ { "documenttype":"api", "prodname":"smn", - "opensource":"false" + "opensource":"true;false" } ], "title":"Public Parameters", @@ -870,7 +870,7 @@ { "documenttype":"api", "prodname":"smn", - "opensource":"false" + "opensource":"true;false" } ], "title":"General Request Return Code", @@ -889,7 +889,7 @@ { "documenttype":"api", "prodname":"smn", - "opensource":"false" + "opensource":"true;false" } ], "title":"Exception Response", @@ -908,7 +908,7 @@ { "documenttype":"api", "prodname":"smn", - "opensource":"false" + "opensource":"true;false" } ], "title":"Returned Value", @@ -927,7 +927,7 @@ { "documenttype":"api", "prodname":"smn", - "opensource":"false" + "opensource":"true;false" } ], "title":"Error Codes", @@ -946,7 +946,7 @@ { "documenttype":"api", "prodname":"smn", - "opensource":"false" + "opensource":"true;false" } ], "title":"Obtaining a Project ID", @@ -965,7 +965,7 @@ { "documenttype":"api", "prodname":"smn", - "opensource":"false" + "opensource":"true;false" } ], "title":"Appendix", @@ -984,7 +984,7 @@ { "documenttype":"api", "prodname":"smn", - "opensource":"false" + "opensource":"true;false" } ], "title":"Topic Attribute List", @@ -1003,7 +1003,7 @@ { "documenttype":"api", "prodname":"smn", - "opensource":"false" + "opensource":"true;false" } ], "title":"Change History", diff --git a/docs/smn/api-ref/CLASS.TXT.json b/docs/smn/api-ref/CLASS.TXT.json index a87411691..3505d6779 100644 --- a/docs/smn/api-ref/CLASS.TXT.json +++ b/docs/smn/api-ref/CLASS.TXT.json @@ -389,7 +389,7 @@ { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "product_code":"smn", - "title":"Sending an Application Message", + "title":"Sending an Application Message (Deprecated)", "uri":"en-us_topic_0173593949.html", "doc_type":"api", "p_code":"38", diff --git a/docs/smn/api-ref/en-us_topic_0036017316.html b/docs/smn/api-ref/en-us_topic_0036017316.html index daa1b4c50..3d86e4c9b 100644 --- a/docs/smn/api-ref/en-us_topic_0036017316.html +++ b/docs/smn/api-ref/en-us_topic_0036017316.html @@ -1,8 +1,8 @@ - +

API Usage Guidelines

-

Public cloud APIs comply with the RESTful API design principles. REST-based Web services are organized into resources. Each resource is identified by one or more Uniform Resource Identifiers (URIs). An application accesses a resource based on the resource's Unified Resource Locator (URL). A URL is usually in the following format: https://Endpoint/uri. In the URL,uri indicates the resource path, that is, the API access path.

-

Public cloud APIs use HTTPS as the transmission protocol. Requests/Responses are transmitted by using JSON messages, with media type represented by Application/json.

-

For details about how to use APIs, see API Usage Guidelines.

+

Public cloud APIs comply with the RESTful API design principles. REST-based Web services are organized into resources. Each resource is identified by one or more Uniform Resource Identifiers (URIs). An application accesses a resource based on the resource's Unified Resource Locator (URL). A URL is usually in the following format: https://Endpoint/uri. In the URL, uri indicates the resource path, that is, the API access path.

+

Public cloud APIs use HTTPS as the transmission protocol. Requests/Responses are transmitted by using JSON messages, with media type represented by Application/json.

+

For details about how to use APIs, see API Usage Guidelines.

diff --git a/docs/smn/api-ref/en-us_topic_0173558607.html b/docs/smn/api-ref/en-us_topic_0173558607.html index ce8025efb..60ed3d767 100644 --- a/docs/smn/api-ref/en-us_topic_0173558607.html +++ b/docs/smn/api-ref/en-us_topic_0173558607.html @@ -14,7 +14,7 @@
  • Message Publishing
    • -
  • Sending an Application Message
    +
  • Sending an Application Message (Deprecated)
    • diff --git a/docs/smn/api-ref/en-us_topic_0173558608.html b/docs/smn/api-ref/en-us_topic_0173558608.html index 7f54b6a2d..a405db9b9 100644 --- a/docs/smn/api-ref/en-us_topic_0173558608.html +++ b/docs/smn/api-ref/en-us_topic_0173558608.html @@ -2,15 +2,15 @@

    Permissions Policies and Supported Actions

    This section describes fine-grained permissions management for your SMN resources. If your account does not need individual IAM users, you can skip over this section.

    -

    By default, new IAM users do not have permissions assigned. You need to add a user to one or more groups, and attach permissions policies or roles to these groups. Users inherit permissions from the groups to which they are added and can perform specified operations on cloud services based on the permissions.

    +

    By default, new IAM users do not have permissions assigned. You need to add a user to one or more groups and attach permissions policies or roles to these groups. Users inherit permissions from the groups to which they are added and can perform specified operations on cloud services based on the permissions.

    You can grant users permissions by using roles and policies. Roles: A type of coarse-grained authorization mechanism that defines service-level permissions based on user responsibilities. There are only a limited number of roles for granting permissions to users. Policies: A type of fine-grained authorization mechanism that defines permissions required to perform operations on specific cloud resources under certain conditions. This mechanism allows for more flexible policy-based authorization and secure access control.

    Policy-based authorization is useful if you want to allow or deny the access to an API.

    An account has all of the permissions required to call all APIs, but IAM users must have the required permissions specifically assigned. The permissions required for calling an API are determined by the actions supported by the API. Only users who have been granted permissions allowing the actions can call the API successfully. For example, if an IAM user wants to query ECSs using an API, the user must have been granted permissions that allow the ecs:servers:list action.

    Supported Actions

    IAM provides system-defined policies that can be directly used. You can also create custom policies to supplement system-defined policies for more refined access control. Actions supported by policies are specific to APIs. Common concepts related to policies include:

    -
    • Permissions: Statements in a policy that allow or deny certain operations.
    • APIs: REST APIs that can be called by a user who has been granted specific permissions.
    • Actions: Specific operations that are allowed or denied.
    • Related actions: Actions on which a specific action depends to take effect. When assigning permissions for the action to a user, you also need to assign permissions for the dependent actions.
    • IAM or enterprise projects: Type of projects for which an action will take effect. Policies that contain actions for both IAM and enterprise projects can be used and take effect for both IAM and Enterprise Management. Policies that only contain actions for IAM projects can be used and only take effect for IAM. Administrators can check whether an action supports IAM projects or enterprise projects in the action list. "√" indicates that the action supports the project and "×" indicates that the action does not support the project.
    +
    • Permissions: statements in a policy that allow or deny certain operations.
    • APIs: REST APIs that can be called by a user who has been granted specific permissions.
    • Actions: specific operations that are allowed or denied.
    • Related actions: actions on which a specific action depends to take effect. When assigning permissions for the action to a user, you also need to assign permissions for the dependent actions.
    • IAM or enterprise projects: type of projects for which an action will take effect. Policies that contain actions for both IAM and enterprise projects can be used and applied for both IAM and Enterprise Management. Policies that only contain actions for IAM projects can be used and only take effect for IAM. Administrators can check whether an action supports IAM projects or enterprise projects in the action list. "√" indicates that the action supports the project and "×" indicates that the action does not support the project.

    SMN supports the following actions that can be defined in custom policies:

    -
    • Topic Operations, including actions supported by topic management APIs, such as APIs for creating, querying, updating, and deleting topics
    • Template Operations, including actions supported by message template management APIs, such as the APIs for creating, querying, updating, and deleting message templates
    • Tag Operations, including actions supported by TMS APIs, such as the APIs for querying resources, adding a resource tag, adding or deleting resource tags in batches, and deleting a resource a tag
    • Message Publishing, including actions supported by message publishing management APIs, such as the message publishing API
    • Sending an Application Message, including actions supported by direct application messaging management API, such as the API for sending an application message
    +
    • Topic Operations, including actions supported by topic management APIs, such as APIs for creating, querying, updating, and deleting topics
    • Template Operations, including actions supported by message template management APIs, such as the APIs for creating, querying, updating, and deleting message templates
    • Tag Operations, including actions supported by TMS APIs, such as the APIs for querying resources, adding a resource tag, adding or deleting resource tags in batches, and deleting a resource a tag
    • Message Publishing, including actions supported by message publishing management APIs, such as the message publishing API
    • Sending an Application Message (Deprecated), including actions supported by direct application messaging management API, such as the API for sending an application message
    diff --git a/docs/smn/api-ref/en-us_topic_0173593949.html b/docs/smn/api-ref/en-us_topic_0173593949.html index 7d5934487..9bb1e4e39 100644 --- a/docs/smn/api-ref/en-us_topic_0173593949.html +++ b/docs/smn/api-ref/en-us_topic_0173593949.html @@ -1,6 +1,6 @@ -

    Sending an Application Message

    +

    Sending an Application Message (Deprecated)

    diff --git a/docs/smn/api-ref/smn_api_510002.html b/docs/smn/api-ref/smn_api_510002.html index 8a87a6d88..1d28a52eb 100644 --- a/docs/smn/api-ref/smn_api_510002.html +++ b/docs/smn/api-ref/smn_api_510002.html @@ -41,7 +41,7 @@ - diff --git a/docs/smn/api-ref/smn_api_53001.html b/docs/smn/api-ref/smn_api_53001.html index a4a2acaf4..1fe34e1a0 100644 --- a/docs/smn/api-ref/smn_api_53001.html +++ b/docs/smn/api-ref/smn_api_53001.html @@ -5,6 +5,7 @@
    • Function

      Create a message template for quick message sending to reduce the request data volume.

      By default, a user can create a maximum of 100 message templates. However, in a high-concurrency scenario, which is rare, extra templates may be successfully created.

      +

      Message templates are identified by name, but you can create different templates with the same name as long as they are configured for different protocols. All template messages must include a Default template or they cannot be sent out. The Default template is used anytime a template has not been configured for a given protocol, but as long as there is a template for the protocol, then any subscriber who selected that protocol when they subscribed will receive a message using the corresponding template.

    URI

    • URI format

      POST /v2/{project_id}/notifications/message_template

      @@ -36,13 +37,13 @@

    Request

    • Parameter description -

    Permission

    Type

    Description

    +

    Description

    Parameter

    +
    - - @@ -90,11 +91,11 @@

    Response

    • Parameter description -

    Parameter

    Mandatory

    Type

    +

    Type

    Description

    +

    Description

    Parameter

    +
    - - diff --git a/docs/smn/api-ref/smn_api_54003.html b/docs/smn/api-ref/smn_api_54003.html index 71ca60df3..16b0ff74d 100644 --- a/docs/smn/api-ref/smn_api_54003.html +++ b/docs/smn/api-ref/smn_api_54003.html @@ -3,7 +3,7 @@

    Publishing Messages Using a Template

    Description

    • API name

      Publish

    -
    • Function

      Use the message template to publish a message to a topic. After the message ID is returned, the message has been saved and is to be pushed to the subscribers of the topic. This API allows you to send messages to different types of subscribers using different template protocols with the same name.

      +
      • Function

        Use the message template to publish a message to a topic. After the message ID is returned, the message has been saved and is to be pushed to the subscribers of the topic. This API allows you to send messages to different types of subscribers using the same template name but different protocols.

    URI

    • URI format

      POST /v2/{project_id}/notifications/topics/{topic_urn}/publish

      @@ -44,13 +44,13 @@

    Request

    • Parameter description -

    Parameter

    Type

    +

    Type

    Description

    +

    Description

    Parameter

    +
    - - @@ -116,11 +116,11 @@

    Response

    • Parameter description -

    Parameter

    Mandatory

    Type

    +

    Type

    Description

    +

    Description

    Parameter

    +
    - - diff --git a/docs/smn/api-ref/smn_api_56002.html b/docs/smn/api-ref/smn_api_56002.html index cd00e6251..0b21ac3e7 100644 --- a/docs/smn/api-ref/smn_api_56002.html +++ b/docs/smn/api-ref/smn_api_56002.html @@ -50,7 +50,7 @@ @@ -59,13 +59,13 @@

    Request

    • Parameter description -

    Parameter

    Type

    +

    Type

    Description

    +

    Description

    Resource ID

    Obtain a resource ID:

    -
    • Add X-SMN-RESOURCEID-TYPE=name in the request header and set the resource ID to the topic name.
    • Call the GetResourceInstances API to obtain the resource ID.
    +
    • Add X-SMN-RESOURCEID-TYPE=name in the request header and set the resource ID to the topic name.
    • Call the GetResourceInstances API to obtain the resource ID.

    Parameter

    +
    - - - diff --git a/docs/smn/api-ref/smn_api_56003.html b/docs/smn/api-ref/smn_api_56003.html index 1118537a0..cd1d29ffb 100644 --- a/docs/smn/api-ref/smn_api_56003.html +++ b/docs/smn/api-ref/smn_api_56003.html @@ -47,7 +47,7 @@ diff --git a/docs/smn/api-ref/smn_api_56004.html b/docs/smn/api-ref/smn_api_56004.html index 25da677ce..ca4191ef6 100644 --- a/docs/smn/api-ref/smn_api_56004.html +++ b/docs/smn/api-ref/smn_api_56004.html @@ -47,7 +47,7 @@ diff --git a/docs/smn/api-ref/smn_api_56005.html b/docs/smn/api-ref/smn_api_56005.html index 90410b1a8..1f72f1eca 100644 --- a/docs/smn/api-ref/smn_api_56005.html +++ b/docs/smn/api-ref/smn_api_56005.html @@ -46,7 +46,7 @@ diff --git a/docs/smn/api-ref/smn_api_66000.html b/docs/smn/api-ref/smn_api_66000.html index 5cbd38d72..9612e2726 100644 --- a/docs/smn/api-ref/smn_api_66000.html +++ b/docs/smn/api-ref/smn_api_66000.html @@ -5,7 +5,7 @@

    Obtain the Project ID by Calling an API

    You can obtain the project ID by calling the IAM API used to query project information based on the specified criteria.

    -

    The API used to obtain a project ID is GET https://{Endpoint}/v3/projects. {Endpoint} is the IAM endpoint and can be obtained from Regions and Endpoints.

    +

    The API used to obtain a project ID is GET https://{Endpoint}/v3/projects. {Endpoint} is the IAM endpoint and can be obtained from Regions and Endpoints.

    The following is an example response. The value of id is the project ID.

    {
     "projects": [

    Parameter

    Mandatory

    +

    Mandatory

    Type

    +

    Type

    Description

    +

    Description

    Resource ID

    Obtain a resource ID:

    -
    • Add X-SMN-RESOURCEID-TYPE=name in the request header and set the resource ID to the topic name.
    • Call the GetResourceInstances API to obtain the resource ID.
    +
    • Add X-SMN-RESOURCEID-TYPE=name in the request header and set the resource ID to the topic name.
    • Call the GetResourceInstances API to obtain the resource ID.

    Resource ID

    Obtain a resource ID:

    -
    • Add X-SMN-RESOURCEID-TYPE=name in the request header and set the resource ID to the topic name.
    • Call the GetResourceInstances API to obtain the resource ID.
    +
    • Add X-SMN-RESOURCEID-TYPE=name in the request header and set the resource ID to the topic name.
    • Call the GetResourceInstances API to obtain the resource ID.

    Resource ID

    Obtain a resource ID:

    -
    • Add X-SMN-RESOURCEID-TYPE=name in the request header and set the resource ID to the topic name.
    • Call the GetResourceInstances API to obtain the resource ID.
    +
    • Add X-SMN-RESOURCEID-TYPE=name in the request header and set the resource ID to the topic name.
    • Call the GetResourceInstances API to obtain the resource ID.