So, what we will do next is add the code to document how that *external API* should look like to receive the callback from *your API*.

That documentation will show up in the Swagger UI at `/docs` in your API, and it will let external developers know how to build the *external API*.

This example doesn't implement the callback itself (that could be just a line of code), only the documentation part.

labels.virtual_host_value=Virtual Host
labels.append_query_param_enabled=Append Search Parameters
labels.login_required=Login Required
labels.result_collapsed=Collapse Duplicate Results
labels.login_link=Show Login Link
labels.thumbnail=Show Thumbnail
labels.ignore_failure_type=Ignore Failure Types
labels.failure_count_threshold=Failure Count Threshold
labels.popular_word_word_enabled=Popular Word Response
labels.supported_search_web=Web

        int length = 32;

        Hexdump.hexdump(ps, data, offset, length);
        String output = baos.toString();

        assertNotNull(output);
        // Should start at offset 0 in display but show data from offset 16
        assertTrue(output.contains("00000:"));
        // First byte should be 0x10 (16 in decimal)
        assertTrue(output.contains(" 10 11 12"));
    }

    @Test

    }

    // -----------------------------------------------------
    //                                     Parameter Logging
    //                                     -----------------
    // logging filter cannot show the parameters when multi-part so logging here
    protected void showFieldLoggingTitle() {
        if (logger.isDebugEnabled()) {
            logger.debug("[Multipart Request Parameter]");
        }
    }

        };

        SystemHelper systemHelper = new SystemHelper() {
            @Override
            public boolean isChangedClusterState(int status) {
                // Status 0 = GREEN is alive, should not show changed
                return false;
            }

            @Override
            public String getHostname() {
                return "test-hostname";
            }
        };

</div>

I'm the creator of **FastAPI**. You can read more about that in [Help FastAPI - Get Help - Connect with the author](help-fastapi.md#connect-with-the-author){.internal-link target=_blank}.

...But here I want to show you the community.

---

**FastAPI** receives a lot of support from the community. And I want to highlight their contributions.

These are the people that:

        crawlJob.fileConfigIds(null);
        crawlJob.dataConfigIds(null);

        String result = crawlJob.execute();

        assertNotNull(result);
        // When all configs are null, runAll is true, so they show ALL
        assertTrue(result.contains("Web  Config Id: ALL"));
        assertTrue(result.contains("File Config Id: ALL"));
        assertTrue(result.contains("Data Config Id: ALL"));
    }

But once you know the basic information of **HTTPS for developers** you can easily combine and configure different tools to help you manage everything in a simple way.

round:"pink",color:"#FF0000",fontWeight:"bold",border:"red solid 1px",borderWidth:"0px 0px 4px",display:"inline-block",fontSize:d.fontSize,padding:d.padding},h=d.bad;0===e.length&&(e=a("<span></span>"),e.addClass("strength-meter").appendTo(c)),b?e.show():e.hide(),1===f?h=d.weak:2===f?(g.background="lightyellow",g.borderColor="yellow",g.color="goldenrod",h=d.good):f>=3&&(g.background="lightgreen",g.borderColor="darkgreen",g.color="darkgreen",h=d.strong),e.css(g).text(h)})}});var f=function(b,c,d,e,f){var...

You can see it directly at: <a href="http://127.0.0.1:8000/openapi.json" class="external-link" target="_blank">http://127.0.0.1:8000/openapi.json</a>.

It will show a JSON starting with something like:

```JSON
{
    "openapi": "3.1.0",
    "info": {
        "title": "FastAPI",
        "version": "0.1.0"
    },
    "paths": {
        "/items/": {