forked from docs/doc-exports
Chen, Junjie
7f68b84da4
Reviewed-by: Hasko, Vladimir <vladimir.hasko@t-systems.com> Co-authored-by: Chen, Junjie <chenjunjie@huawei.com> Co-committed-by: Chen, Junjie <chenjunjie@huawei.com>
9 lines
1.5 KiB
HTML
9 lines
1.5 KiB
HTML
<a name="en-us_topic_0036182510"></a><a name="en-us_topic_0036182510"></a>
|
|
|
|
<h1 class="topictitle1">Using APIs</h1>
|
|
<div id="body0000001381767973"><p id="en-us_topic_0036182510__p35306501">Public cloud application programming interfaces (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: <strong id="en-us_topic_0036182510__b19651844193113">https://<em id="en-us_topic_0036182510__i19378047153111">Endpoint</em>/<em id="en-us_topic_0036182510__i9440105020318">uri</em></strong>. In the URL, <strong id="en-us_topic_0036182510__b9616944"><em id="en-us_topic_0036182510__i3456638163113">uri</em></strong><em id="en-us_topic_0036182510__i1845633893118"> </em>indicates the resource path, that is, the API access path.</p>
|
|
<p id="en-us_topic_0036182510__p49323054">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_0036182510__b19443632">Application/json</strong>.</p>
|
|
<p id="en-us_topic_0036182510__p16419926165312">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>
|
|
|