*
     * @param body the request header data to create
     * @return JSON response containing the created request header setting ID
     */
    // POST /api/admin/reqheader/setting
    @Execute
    public JsonResponse<ApiResult> post$setting(final CreateBody body) {
        validateApi(body, messages -> {});
        if (!isValidWebConfigId(body.webConfigId)) {

     *
     * @param body the web authentication data to create
     * @return JSON response containing the created web authentication setting ID
     */
    // POST /api/admin/webauth/setting
    @Execute
    public JsonResponse<ApiResult> post$setting(final CreateBody body) {
        validateApi(body, messages -> {});
        if (!isValidWebConfigId(body.webConfigId)) {

        })).status(Status.OK).result());
    }

    // POST /api/admin/accesstoken/setting
    /**
     * Creates a new access token setting.
     *
     * @param body the create body containing access token data
     * @return JSON response with the created access token ID
     */
    @Execute
    public JsonResponse<ApiResult> post$setting(final CreateBody body) {
        validateApi(body, messages -> {});

ここでの「オペレーション」とは、HTTPの「メソッド」の1つを指します。

以下のようなものの1つ:

* `POST`
* `GET`
* `PUT`
* `DELETE`

...さらによりエキゾチックなもの:

* `OPTIONS`
* `HEAD`
* `PATCH`
* `TRACE`

HTTPプロトコルでは、これらの「メソッド」の1つ（または複数）を使用して各パスにアクセスできます。

---

APIを構築するときは、通常、これらの特定のHTTPメソッドを使用して特定のアクションを実行します。

通常は次を使用します:

* `POST`: データの作成
* `GET`: データの読み取り
* `PUT`: データの更新
* `DELETE`: データの削除

## REST API call to plugin

To verify the custom token presented in the `AssumeRoleWithCustomToken` API, MinIO makes a POST request to the configured identity management plugin endpoint and expects a response with some details as shown below:

### Request `POST` to plugin endpoint

Query parameters:

| Parameter Name | Value Type | Purpose                                                                 |

    /**
     * Creates a new role setting.
     *
     * @param body the role data to create
     * @return JSON response containing the created role setting ID
     */
    // POST /api/admin/role/setting
    @Execute
    public JsonResponse<ApiResult> post$setting(final CreateBody body) {
        validateApi(body, messages -> {});
        body.crudMode = CrudMode.CREATE;
        final Role entity = getRole(body).orElseGet(() -> {

            **/build/releases-data-checkout/data/releases.xml
            **/build/git-checkout/build/reports/integTest/** => distribution-tests
            **/smoke-tests/build/reports/tests/** => post-smoke-tests
            **/build/version-info.properties => version-info.properties
            """.trimIndent()

        dependencies {

///

При створенні API, "шлях" є основним способом розділення "завдань" і "ресурсів".
#### Operation

"Операція" (operation) тут означає один з "методів" HTTP.

Один з:

* `POST`
* `GET`
* `PUT`
* `DELETE`

...та більш екзотичних:

* `OPTIONS`
* `HEAD`
* `PATCH`
* `TRACE`

     *
     * @param body the web configuration data to create
     * @return JSON response containing the created web configuration setting ID
     */
    // POST /api/admin/webconfig/setting
    @Execute
    public JsonResponse<ApiResult> post$setting(final CreateBody body) {
        validateApi(body, messages -> {});
        body.crudMode = CrudMode.CREATE;

        })).status(Status.OK).result());
    }

    // POST /api/admin/fileconfig/setting
    /**
     * Creates a new file configuration setting.
     *
     * @param body file configuration setting data to create
     * @return JSON response with created setting ID and status
     */
    @Execute
    public JsonResponse<ApiResult> post$setting(final CreateBody body) {
        validateApi(body, messages -> {});