Imagine you develop an app that allows creating invoices.

These invoices will have an `id`, `title` (optional), `customer`, and `total`.

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).

    void flush();

    /**
     * Registers the specified cache record for usage with the given project. Integrators can use the information
     * collected from this method in combination with a custom cache implementation to dispose unused records from the
     * cache.
     *
     * @param project The project that employs the plugin realm, must not be {@code null}.

.Values.configPathmc }}certs {{ end }} resources: {{ toYaml .Values.makeUserJob.resources | indent 10 }} {{- end }} minio/templates/post-install-custom-command.yaml {{- if .Values.customCommands }} apiVersion: batch/v1 kind: Job metadata: name: {{ template "minio.fullname" . }}-custom-command-job namespace: {{ .Release.Namespace | quote }} labels: app: {{ template "minio.name" . }}-custom-command-job chart: {{ template "minio.chart" . }} release: {{ .Release.Name }} heritage: {{ .Release.Service }} annotations: "helm.sh/hook":...

.Values.configPathmc }}certs {{ end }} resources: {{ toYaml .Values.makeUserJob.resources | indent 10 }} {{- end }} minio/templates/post-install-custom-command.yaml {{- if .Values.customCommands }} apiVersion: batch/v1 kind: Job metadata: name: {{ template "minio.fullname" . }}-custom-command-job namespace: {{ .Release.Namespace | quote }} labels: app: {{ template "minio.name" . }}-custom-command-job chart: {{ template "minio.chart" . }} release: {{ .Release.Name }} heritage: {{ .Release.Service }} annotations: "helm.sh/hook":...

.Values.configPathmc }}certs {{ end }} resources: {{ toYaml .Values.makeUserJob.resources | indent 10 }} {{- end }} minio/templates/post-install-custom-command.yaml {{- if .Values.customCommands }} apiVersion: batch/v1 kind: Job metadata: name: {{ template "minio.fullname" . }}-custom-command-job namespace: {{ .Release.Namespace | quote }} labels: app: {{ template "minio.name" . }}-custom-command-job chart: {{ template "minio.chart" . }} release: {{ .Release.Name }} heritage: {{ .Release.Service }} annotations: "helm.sh/hook":...

      assertThat(rewrittenResponse.trailers()).isEqualTo(headersOf("t1", "v1"))
    }
  }

  /**
   * We had a bug where a custom `ResponseBody` interacted poorly with `Response.trailers()`.
   * Confirm custom trailers can be read without even accessing the response body.
   */
  @Test
  fun customTrailersDoNotUseResponseBody() {
    val response =
      Response

        if (mojoExecutionConfigurator == null) {
            //
            // The plugin has a custom component configurator but does not have a custom mojo execution configurator
            // so fall back to the default mojo execution configurator.
            //
            mojoExecutionConfigurator = mojoExecutionConfigurators.get("default");

.Values.configPathmc }}certs {{ end }} resources: {{ toYaml .Values.makeUserJob.resources | indent 10 }} {{- end }} minio/templates/post-install-custom-command.yaml {{- if .Values.customCommands }} apiVersion: batch/v1 kind: Job metadata: name: {{ template "minio.fullname" . }}-custom-command-job namespace: {{ .Release.Namespace | quote }} labels: app: {{ template "minio.name" . }}-custom-command-job chart: {{ template "minio.chart" . }} release: {{ .Release.Name }} heritage: {{ .Release.Service }} annotations: "helm.sh/hook":...

It might also help avoid confusion for new developers that see an unused parameter in your code and could think it's unnecessary.

///

/// info

In this example we use invented custom headers `X-Key` and `X-Token`.

But in real cases, when implementing security, you would get more benefits from using the integrated [Security utilities (the next chapter)](../security/index.md){.internal-link target=_blank}.

    * Wird in Requests und Responses als `float` der Gesamtsekunden dargestellt.
    * Pydantic ermöglicht auch die Darstellung als „ISO 8601 Zeitdifferenz-Kodierung“, <a href="https://docs.pydantic.dev/latest/concepts/serialization/#custom-serializers" class="external-link" target="_blank">siehe die Dokumentation für weitere Informationen</a>.
* `frozenset`:
    * Wird in Requests und Responses wie ein `set` behandelt: