forked from docs/doc-exports
guoyanyan
245e895951
Reviewed-by: Hasko, Vladimir <vladimir.hasko@t-systems.com> Co-authored-by: guoyanyan <guoyanyan3@huawei.com> Co-committed-by: guoyanyan <guoyanyan3@huawei.com>
9 lines
1.6 KiB
HTML
9 lines
1.6 KiB
HTML
<a name="en-us_topic_0045219159"></a><a name="en-us_topic_0045219159"></a>
|
|
|
|
<h1 class="topictitle1">API Usage Guidelines</h1>
|
|
<div id="body1558942586465"><p id="en-us_topic_0045219159__en-us_topic_0082242144_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="en-us_topic_0045219159__en-us_topic_0082242144_en-us_topic_0020507759_i1385069210259">https://Endpoint/uri</em>. In the URL,<strong id="en-us_topic_0045219159__en-us_topic_0082242144_en-us_topic_0020507759_b5754736910259">uri</strong> indicates the resource path, that is, the API access path.</p>
|
|
<p id="en-us_topic_0045219159__en-us_topic_0082242144_en-us_topic_0020507759_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="en-us_topic_0045219159__en-us_topic_0082242144_en-us_topic_0020507759_b3082532510259">Application/json</strong>.</p>
|
|
<p id="en-us_topic_0045219159__en-us_topic_0082242144_en-us_topic_0020507759_p188289482118">For details about how to use APIs, see <em id="en-us_topic_0045219159__i18143852164819"><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></em>.</p>
|
|
</div>
|
|
|