<distribution>repo</distribution>
      <comments>free</comments>
    </license>
  </licenses>

  <developers>
    <developer>
      <id>dev</id>
      <name>project-developer</name>
      <email>developer@</email>
      <url>https://developer</url>
      <organization>developer</organization>
      <organizationUrl>https://devel.org</organizationUrl>
      <roles>
        <role>devel</role>
      </roles>

The process that happens when your API app calls the *external API* is named a "callback". Because the software that the external developer wrote sends a request to your API and then your API *calls back*, sending a request to an *external API* (that was probably created by the same developer).

    <developerConnection>developer-connection</developerConnection>
    <url>repository-url</url>
  </scm>

  <mailingLists>
    <mailingList>
      <name>Maven User List</name>
      <subscribe>subscribe</subscribe>
      <unsubscribe>unsubscribe</unsubscribe>
      <archive>archive</archive>
    </mailingList>
  </mailingLists>

  <developers>
    <developer>
      <name>Jason van Zyl</name>

         * it will be reported as "external". It is up to developer to correctly interpret output (GAV) of issues
         * and realize that in this case he wears two hats:" "user" and "(plugin) developer".
         */
        EXTERNAL
    }

    /**
     * Reports plugin issues applicable to the plugin as a whole.
     * <p>

    """
    Create an invoice.

    This will (let's imagine) let the API user (some external developer) create an
    invoice.

    And this path operation will:

    * Send the invoice to the client.
    * Collect the money from the client.
    * Send a notification back to the API user (the external developer), as a callback.
        * At this point is that the API will somehow send a POST request to the

Once the **patch** is successfully applied, developer must run tests to validate the fix that was backported by running following tests, locally.

    Se você quiser ler mais sobre essas codificações e campos de formulário, vá para o <a href="https://developer.mozilla.org/pt-BR/docs/Web/HTTP/Methods/POST" class="external-link" target="_blank"><abbr title="Mozilla Developer Network">MDN</abbr> web docs para <code>POST</code></a>.

!!! warning "Aviso"

```Python hl_lines="8-9  11  14"
{!../../../docs_src/middleware/tutorial001.py!}
```

!!! tip
    Keep in mind that custom proprietary headers can be added <a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers" class="external-link" target="_blank">using the 'X-' prefix</a>.

    <developerConnection>developer-connection</developerConnection>
    <url>repository-url</url>
  </scm>

  <mailingLists>
    <mailingList>
      <name>Maven User List</name>
      <subscribe>subscribe</subscribe>
      <unsubscribe>unsubscribe</unsubscribe>
      <archive>archive</archive>
    </mailingList>
  </mailingLists>

  <developers>
    <developer>
      <name>Jason van Zyl</name>

    <license>
      <name>parent-license</name>
      <url>https://parent.url/license</url>
      <distribution>repo</distribution>
    </license>
  </licenses>

  <developers>
    <developer>
      <name>parent-developer</name>
    </developer>
  </developers>
  <contributors>
    <contributor>
      <name>parent-contributor</name>
    </contributor>
  </contributors>

  <mailingLists>
    <mailingList>