forked from docs/doc-exports
Hasko, Vladimir
0c7b91f4bd
Reviewed-by: gtema <artem.goncharov@gmail.com> Co-authored-by: Hasko, Vladimir <vladimir.hasko@t-systems.com> Co-committed-by: Hasko, Vladimir <vladimir.hasko@t-systems.com>
9 lines
1.3 KiB
HTML
9 lines
1.3 KiB
HTML
<a name="EN-US_TOPIC_0000001411119537"></a><a name="EN-US_TOPIC_0000001411119537"></a>
|
|
|
|
<h1 class="topictitle1">API Usage Guidelines</h1>
|
|
<div id="body1444378354187"><p id="EN-US_TOPIC_0000001411119537__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: https://<em id="EN-US_TOPIC_0000001411119537__i137795958918721">Endpoint/uri</em>. In the URL, <em id="EN-US_TOPIC_0000001411119537__i842352697154116">uri</em> indicates the resource path, that is, the API access path.</p>
|
|
<p id="EN-US_TOPIC_0000001411119537__p4816427810259">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_0000001411119537__b1025950229154127">Application/json</strong>.</p>
|
|
<p id="EN-US_TOPIC_0000001411119537__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>
|
|
|