forked from docs/doc-exports
Su, Xiaomeng
f5d48a5472
Reviewed-by: Pruthi, Vineet <vineet.pruthi@t-systems.com> Co-authored-by: Su, Xiaomeng <suxiaomeng1@huawei.com> Co-committed-by: Su, Xiaomeng <suxiaomeng1@huawei.com>
9 lines
1.2 KiB
HTML
9 lines
1.2 KiB
HTML
<a name="dli_02_0500"></a><a name="dli_02_0500"></a>
|
|
|
|
<h1 class="topictitle1">API Usage Guidelines</h1>
|
|
<div id="body0000001339724658"><p id="dli_02_0500__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="dli_02_0500__i1385069210259">https://Endpoint/uri</em>. In the URL, <strong id="dli_02_0500__b5754736910259">uri</strong> indicates the resource path, that is, the API access path.</p>
|
|
<p id="dli_02_0500__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="dli_02_0500__b3082532510259">Application/json</strong>.</p>
|
|
<p id="dli_02_0500__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>
|
|
|