forked from docs/doc-exports
Qin Ying, Fan
65b77b76d4
Reviewed-by: Hajba, László Antal <laszlo-antal.hajba@t-systems.com> Co-authored-by: Qin Ying, Fan <fanqinying@huawei.com> Co-committed-by: Qin Ying, Fan <fanqinying@huawei.com>
9 lines
1.3 KiB
HTML
9 lines
1.3 KiB
HTML
<a name="eip_api01_0000"></a><a name="eip_api01_0000"></a>
|
|
|
|
<h1 class="topictitle1">API Usage Guidelines</h1>
|
|
<div id="body1540262827892"><p id="eip_api01_0000__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: <em id="eip_api01_0000__en-us_topic_0020507759_i1385069210259">https://Endpoint/uri</em>. In the URL, <strong id="eip_api01_0000__en-us_topic_0020507759_b5754736910259">uri</strong> indicates the resource path, that is, the API access path.</p>
|
|
<p id="eip_api01_0000__en-us_topic_0020507759_p4816427810259">Public cloud APIs use HTTPS as the transmission protocol. Requests and responses are transmitted using JSON messages, with media type represented by <strong id="eip_api01_0000__b1132248266143256">Application/json</strong>.</p>
|
|
<p id="eip_api01_0000__en-us_topic_0020507759_p899246910259">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>
|
|
|