forked from docs/doc-exports
Dong, Qiu Jian
21dca87c32
Reviewed-by: Eotvos, Oliver <oliver.eotvos@t-systems.com> Co-authored-by: Dong, Qiu Jian <qiujiandong1@huawei.com> Co-committed-by: Dong, Qiu Jian <qiujiandong1@huawei.com>
15 lines
1.4 KiB
HTML
15 lines
1.4 KiB
HTML
<a name="cci_02_0009"></a><a name="cci_02_0009"></a>
|
|
|
|
<h1 class="topictitle1">Calling APIs</h1>
|
|
<div id="body1520932981235"><p id="cci_02_0009__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="cci_02_0009__en-us_topic_0170091002_i1385069210259">https://Endpoint/uri</em>. <strong id="cci_02_0009__en-us_topic_0170091002_b5754736910259">uri</strong> indicates the resource path, that is, the API access path.</p>
|
|
<p id="cci_02_0009__en-us_topic_0170091002_p4816427810259">Public cloud APIs use HTTPS as the transmission protocol. Requests/Responses are transmitted by using JSON messages, with media type represented by <strong id="cci_02_0009__en-us_topic_0170091002_b3082532510259">Application/json</strong>.</p>
|
|
<p id="cci_02_0009__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>
|
|
<ul class="ullinks">
|
|
<li class="ulchildlink"><strong><a href="cci_02_0003.html">Authentication</a></strong><br>
|
|
</li>
|
|
</ul>
|
|
</div>
|
|
|