forked from laiweijian4/doc-exports
zhangyue
5d0d5cb580
Reviewed-by: Muller, Martin <martin.muller@t-systems.com> Co-authored-by: zhangyue <zhangyue164@huawei.com> Co-committed-by: zhangyue <zhangyue164@huawei.com>
9 lines
1.2 KiB
HTML
9 lines
1.2 KiB
HTML
<a name="sfs_02_0001"></a><a name="sfs_02_0001"></a>
|
|
|
|
<h1 class="topictitle1">API Usage Guidelines</h1>
|
|
<div id="body8662426"><p id="sfs_02_0001__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: https://<em id="sfs_02_0001__aca1eab249b8e49e7a4c208db8c1c484f">Endpoint/uri</em>. In the URL, <strong id="sfs_02_0001__b5754736910259">uri</strong> indicates the resource path, that is, the API access path.</p>
|
|
<p id="sfs_02_0001__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="sfs_02_0001__b3082532510259">Application/json</strong>.</p>
|
|
<p id="sfs_02_0001__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>
|
|
|