forked from docs/doc-exports
Wang , Deng Ke
a96a12ecf1
Reviewed-by: gtema <artem.goncharov@gmail.com> Co-authored-by: Wang , Deng Ke <wangdengke2@huawei.com> Co-committed-by: Wang , Deng Ke <wangdengke2@huawei.com>
10 lines
1.2 KiB
HTML
10 lines
1.2 KiB
HTML
<a name="opengauss_api_0012"></a><a name="opengauss_api_0012"></a>
|
|
|
|
<h1 class="topictitle1">Using APIs</h1>
|
|
<div id="body1600411288656"><p id="opengauss_api_0012__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="opengauss_api_0012__i204914796115410">https://Endpoint/uri</em>. In the URL, <em id="opengauss_api_0012__i842352697154116">uri</em> indicates the resource path, that is, the API access path.</p>
|
|
<p id="opengauss_api_0012__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="opengauss_api_0012__b1025950229154127">Application/json</strong>.</p>
|
|
<p id="opengauss_api_0012__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>
|
|
<div></div>
|
|
|