vpruthi/doc-exports
1
0
Fork 0
forked from docs/doc-exports
Code Pull Requests Activity
doc-exports/docs/waf/api-ref/waf_02_0001.html
Li, Qiao 914011d51b waf_api_1109 
Reviewed-by: Hasko, Vladimir <vladimir.hasko@t-systems.com>
Co-authored-by: Li, Qiao <qiaoli@huawei.com>
Co-committed-by: Li, Qiao <qiaoli@huawei.com>
2022-11-16 15:31:27 +00:00

3.8 KiB
Raw Permalink 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.

The following table lists the additional request header fields required for the POST, PUT, PATCH, and DELETE methods.

Parameter

Description

Mandatory

Example

x-request-source-type

Type of a request resource

  • ApiCall: invoked by an API.
  • ConsoleAction: invoked by the console.
  • SystemAction: invoked by the system.

Yes

ApiCall