forked from docs/doc-exports
Mei, Sai
46435e6aee
Reviewed-by: Hasko, Vladimir <vladimir.hasko@t-systems.com> Co-authored-by: Mei, Sai <meisai@huawei.com> Co-committed-by: Mei, Sai <meisai@huawei.com>
9 lines
1.3 KiB
HTML
9 lines
1.3 KiB
HTML
<a name="en-us_topic_0218811267"></a><a name="en-us_topic_0218811267"></a>
|
|
|
|
<h1 class="topictitle1">API Usage Guidelines</h1>
|
|
<div id="body1591087780150"><p id="en-us_topic_0218811267__p142221912201015">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="en-us_topic_0218811267__i15222191215108">Endpoint/uri</em>. In the URL, <em id="en-us_topic_0218811267__i522211124108">uri</em> indicates the resource path, that is, the API access path.</p>
|
|
<p id="en-us_topic_0218811267__p12221212101020">Public cloud APIs use HTTPS as the transmission protocol. Requests/Responses are transmitted using JSON messages, with the media type represented by <strong id="en-us_topic_0218811267__b1322221219106">Application/json</strong>.</p>
|
|
<p id="en-us_topic_0218811267__p8222121221019">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>
|
|
|