Reviewed-by: Miskanin, Jan <jan.miskanin@t-systems.com>
Co-authored-by: zhangyue <zhangyue164@huawei.com>
Co-committed-by: zhangyue <zhangyue164@huawei.com>

2024-08-16 12:25:57 +00:00

4.7 KiB

Raw Blame History

API Usage Guidelines

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://Endpoint/uri. In the URL, uri indicates the resource path, that is, the API access path.

Public cloud APIs use HTTPS as the transmission protocol. Requests/Responses are transmitted by using JSON messages, with media type represented by Application/json.

For details about how to use APIs, see API Usage Guidelines.

An endpoint is the request address for calling an API. Endpoints vary depending on services and regions.

**Table 1** SFS endpoint information
Service Name	Region	URL	Protocol
Scalable File Service Turbo	eu-de	sfs-turbo.eu-de.otc.t-systems.com	HTTPS
Scalable File Service Turbo	eu-nl	sfs-turbo.eu-nl.otc.t-systems.com	HTTPS
Scalable File Service	eu-de	sfs.eu-de.otc.t-systems.com	HTTPS
SFS 3.0 Capacity-Oriented	eu-de	sfs3.eu-de.otc.t-systems.com	HTTPS

4.7 KiB Raw Blame History

API Usage Guidelines

4.7 KiB

Raw Blame History