yexinru/doc-exports
1
0
Fork 0
forked from docs/doc-exports
Code Pull Requests Activity

Config API First Version

Browse Source 
Reviewed-by: Ziuzko, Alevtina <alevtina.ziuzko@t-systems.com>
Co-authored-by: Wei, Hongmin <weihongmin1@huawei.com>
Co-committed-by: Wei, Hongmin <weihongmin1@huawei.com>
This commit is contained in:
Wei, Hongmin
2024-08-22 10:49:27 +00:00
committed by zuul
parent c5b496f0d7
commit da6ca4fb3c
91 changed files with 21322 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
docs/config/api-ref/rms_03_0000.html Normal file
View File

@ -0,0 +1,9 @@
<a name="rms_03_0000"></a><a name="rms_03_0000"></a>
<h1 class="topictitle1">Calling APIs</h1>
<div id="body8662426"><p id="rms_03_0000__en-us_topic_0170091002_p1645204610259">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: <em id="rms_03_0000__en-us_topic_0170091002_i1385069210259">https://Endpoint/uri</em>. In the URL, <strong id="rms_03_0000__b050013114572">uri</strong> indicates the resource path, that is, the API access path.</p>
<p id="rms_03_0000__en-us_topic_0170091002_p4816427810259">Public cloud APIs use HTTPS as the transmission protocol. Requests/Responses are transmitted by using JSON messages, with the media type represented by <strong id="rms_03_0000__en-us_topic_0170091002_b3082532510259">Application/json</strong>.</p>
<p id="rms_03_0000__en-us_topic_0170091002_p188289482118">For details about how to use APIs, see <a href="https://docs.otc.t-systems.com/en-us/api/apiug/apig-en-api-180328001.html?tag=API Documents" target="_blank" rel="noopener noreferrer">API Usage Guidelines</a>.</p>
</div>
<div></div>