Sie verfügt über eine *Pfadoperation*, die einen `Invoice`-Body empfängt, und einen Query-Parameter `callback_url`, der die URL für den Callback enthält.

Dieser Teil ist ziemlich normal, der größte Teil des Codes ist Ihnen wahrscheinlich bereits bekannt:

{* ../../docs_src/openapi_callbacks/tutorial001_py310.py hl[7:11,34:51] *}

/// tip | Tipp

     */
    private final Class<?> targetClass;

    /**
     * The parameter types.
     */
    private final Class<?>[] argTypes;

    /**
     * Creates a {@link NoSuchConstructorRuntimeException}.
     *
     * @param targetClass
     *            Target class
     * @param argTypes
     *            Array of parameter types
     * @param cause
     *            The cause of the exception
     */

import java.util.Map;

/**
 * Interface for script engines that can evaluate templates with parameters.
 * This interface provides a contract for different script engine implementations
 * to process template strings with parameter substitution.
 */
public interface ScriptEngine {

    /**
     * Evaluates a template string with the provided parameter map.
     * The template is processed using the script engine's templating mechanism,

```

///

## `File` und `Form` importieren { #import-file-and-form }

{* ../../docs_src/request_forms_and_files/tutorial001_an_py39.py hl[3] *}

## `File` und `Form`-Parameter definieren { #define-file-and-form-parameters }

Erstellen Sie Datei- und Formularparameter, so wie Sie es auch mit `Body` oder `Query` machen würden:

{* ../../docs_src/request_forms_and_files/tutorial001_an_py39.py hl[10:12] *}

        buffer[37] = 0x00;
        buffer[38] = 0x00;

        // Parameter count (2 bytes)
        buffer[39] = 0x00;
        buffer[40] = 0x00;

        // Parameter offset (2 bytes)
        buffer[41] = 0x00;
        buffer[42] = 0x00;

        // Parameter displacement (2 bytes)
        buffer[43] = 0x00;
        buffer[44] = 0x00;

        // Data count (2 bytes)

      <version>1.0.0</version>
      <name>ExpressionDocumentation</name>
      <description>The root of a parameter plugin expression document.</description>
      <fields>
        <field>
          <version>1.0.0</version>
          <name>expressions</name>
          <description>The list of plugin parameter expressions described by this
            document.</description>
          <association>

* `@app.get()`
* `@app.post()`
* `@app.put()`
* `@app.delete()`
* etc.

{* ../../docs_src/response_status_code/tutorial001_py39.py hl[6] *}

/// note

/// tip

Some editors check for unused function parameters, and show them as errors.

Using these `dependencies` in the *path operation decorator* you can make sure they are executed while avoiding editor/tooling errors.

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

///

/// info

                    logger.warn("Failed to store search parameters in cookie.", e);
                }
            }
        });
    }

    /**
     * Serializes request parameters to a compressed and encoded string.
     *
     * @param parameters Array of request parameters to serialize
     * @return Base64-encoded, GZIP-compressed JSON string of parameters
     * @throws SearchQueryException if serialization fails

* Importieren Sie `HTMLResponse`.
* Übergeben Sie `HTMLResponse` als den Parameter `response_class` Ihres *Pfadoperation-Dekorators*.

{* ../../docs_src/custom_response/tutorial002_py39.py hl[2,7] *}

/// info | Info

Der Parameter `response_class` wird auch verwendet, um den „Medientyp“ der Response zu definieren.