forked from docs/doc-exports
zhangyue
3b5a58b1fe
Reviewed-by: gtema <artem.goncharov@gmail.com> Co-authored-by: zhangyue <zhangyue164@huawei.com> Co-committed-by: zhangyue <zhangyue164@huawei.com>
9 lines
1.2 KiB
HTML
9 lines
1.2 KiB
HTML
<a name="iam_02_0017"></a><a name="iam_02_0017"></a>
|
|
|
|
<h1 class="topictitle1">API Usage Guidelines</h1>
|
|
<div id="body1533025195339"><p id="iam_02_0017__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="iam_02_0017__i204914796115410">https://Endpoint/uri</em>. In the URL, <em id="iam_02_0017__i842352697154116">uri</em> indicates the resource path, that is, the API access path.</p>
|
|
<p id="iam_02_0017__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="iam_02_0017__b1025950229154127">Application/json</strong>.</p>
|
|
<p id="iam_02_0017__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>
|
|
|