# configured git repository. This avoids duplicate builds being triggered when pushes to multiple branches are
      # done in quick succession.
      - generic-webhook-trigger:
          post-content-params:
            - type: JSONPath
              key: ref
              value: '$.ref'
          regex-filter-text: '$ref'
          regex-filter-expression: "^refs/heads/%BRANCH%$"

Bir API oluştururken, "path", "concerns" ve "resources" ayrımını yapmanın ana yoludur.

#### Operation { #operation }

Burada "Operation", HTTP "method"larından birini ifade eder.

Şunlardan biri:

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

...ve daha egzotik olanlar:

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

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

    // POST /api/admin/pathmap/setting
    /**
     * Creates a new path mapping setting.
     *
     * @param body path mapping 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 -> {});

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

    // POST /api/admin/relatedcontent/setting
    /**
     * Creates a new related content setting.
     *
     * @param body related content 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 -> {});

        byte[] fullData = new byte[totalLength];
        int pos = 0;
        System.arraycopy(avFlagsData, 0, fullData, pos, avFlagsData.length);
        pos += avFlagsData.length;
        System.arraycopy(avTimestampData, 0, fullData, pos, avTimestampData.length);
        pos += avTimestampData.length;
        System.arraycopy(avTargetNameData, 0, fullData, pos, avTargetNameData.length);
        pos += avTargetNameData.length;

    return response.body().string();
  }
}
```


Post to a Server
----------------

This program posts data to a service. [Full source][post_example].

```java
public static final MediaType JSON = MediaType.get("application/json");

OkHttpClient client = new OkHttpClient();

String post(String url, String json) throws IOException {
  RequestBody body = RequestBody.create(json, JSON);

The user of your API (an external developer) will create an invoice in your API with a POST request.

Then your API will (let's imagine):

* Send the invoice to some customer of the external developer.
* Collect the money.
* Send a notification back to the API user (the external developer).
    * This will be done by sending a POST request (from *your API*) to some *external API* provided by that external developer (this is the "callback").

O usuário da sua API (um desenvolvedor externo) criará uma fatura na sua API com um request POST.

Então sua API irá (vamos imaginar):

* Enviar a fatura para algum cliente do desenvolvedor externo.
* Coletar o dinheiro.
* Enviar a notificação de volta para o usuário da API (o desenvolvedor externo).
    * Isso será feito enviando um request POST (de *sua API*) para alguma *API externa* fornecida por esse desenvolvedor externo (este é o "callback").

これをヘッダーパラメータとして受け取り、クライアントが離脱した位置からストリームを再開できます:

{* ../../docs_src/server_sent_events/tutorial004_py310.py hl[25,27,31] *}

## POST での SSE { #sse-with-post }

SSE は `GET` だけでなく、**任意の HTTP メソッド**で動作します。

これは、`POST` 上で SSE をストリーミングする [MCP](https://modelcontextprotocol.io) のようなプロトコルで有用です:

{* ../../docs_src/server_sent_events/tutorial005_py310.py hl[14] *}

## 技術詳細 { #technical-details }

     * @param body the request body containing stopwords item information
     * @return JSON response with result status
     */
    // POST /api/admin/dict/stopwords/setting/{dictId}
    @Execute
    public JsonResponse<ApiResult> post$setting(final String dictId, final CreateBody body) {
        body.dictId = dictId;
        validateApi(body, messages -> {});
        body.crudMode = CrudMode.CREATE;