forked from laiweijian4/doc-exports
Hasko, Vladimir
255730fbf9
Reviewed-by: Kucerak, Kristian <kristian.kucerak@t-systems.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="lts_02_0001"></a><a name="lts_02_0001"></a>
|
|
|
|
<h1 class="topictitle1">API Description</h1>
|
|
<div id="body58217140"><p id="lts_02_0001__a80b30f7e2c774b5f888f7da0099f1b9a">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="lts_02_0001__a35b42483c5c74c75ac870f1e756a7fd3">https://lts.eu-de.otc.t-systems.com/uri</em>. In the URL,<strong id="lts_02_0001__aad4d6866384546d58723d0cdf7d76780">uri</strong> indicates the resource path, that is, the API access path.</p>
|
|
<p id="lts_02_0001__ab9fdf3b2753847448d72b20aa21dda30">Public cloud APIs use HTTPS as the transmission protocol. Requests/Responses are transmitted by using JSON messages, with media type represented by <strong id="lts_02_0001__a0b8644f4b79943b59aa984e84a658804">Application/json</strong>.</p>
|
|
<p id="lts_02_0001__en-us_topic_0020507759_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>
|
|
|