forked from docs/doc-exports
fanqinying
b662a89e70
Reviewed-by: Hajba, László Antal <laszlo-antal.hajba@t-systems.com> Co-authored-by: fanqinying <fanqinying@huawei.com> Co-committed-by: fanqinying <fanqinying@huawei.com>
9 lines
1.3 KiB
HTML
9 lines
1.3 KiB
HTML
<a name="cc_01_0013"></a><a name="cc_01_0013"></a>
|
|
|
|
<h1 class="topictitle1">API Usage Guidelines</h1>
|
|
<div id="body19408657"><p id="cc_01_0013__en-us_topic_0020507759_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="cc_01_0013__en-us_topic_0020507759_i137795958918721">Endpoint/uri</em>. In the URL, <em id="cc_01_0013__en-us_topic_0020507759_i842352697154116">uri</em> indicates the resource path, that is, the API access path.</p>
|
|
<p id="cc_01_0013__en-us_topic_0020507759_p4816427810259">Public cloud APIs use HTTPS as the transmission protocol. Requests/Responses are transmitted using JSON messages, with the media type represented by <strong id="cc_01_0013__en-us_topic_0020507759_b1025950229154127">Application/json</strong>.</p>
|
|
<p id="cc_01_0013__en-us_topic_0020507759_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>
|
|
|