This is normally called a **webhook**.

## Webhooks steps { #webhooks-steps }

The process normally is that **you define** in your code what is the message that you will send, the **body of the request**.

You also define in some way at which **moments** your app will send those requests or events.

                valueMap.remove("ip");
                super.printByEcs(valueMap);
            }

            @Override
            protected void printLog(final String message) {
                localLogMsg.set(message);
            }

            @Override
            protected String getClientIp() {
                return StringUtil.EMPTY;
            }
        };
    }

{* ../../docs_src/custom_response/tutorial009c.py hl[9:14,17] *}

Now instead of returning:

```json
{"message": "Hello World"}
```

...this response will return:

```json
{
  "message": "Hello World"
}
```

Of course, you will probably find much better ways to take advantage of this than formatting JSON. 😉

import java.io.UnsupportedEncodingException;

import jcifs.Configuration;
import jcifs.internal.smb1.trans.SmbComTransaction;
import jcifs.internal.util.SMBUtil;

/**
 * SMB1 NetServerEnum2 request message for enumerating network servers in a domain or workgroup.
 * This class implements the SMB1 transaction to query for available servers, supporting various
 * server types and filtering options for network browsing functionality.
 */

package jcifs.internal.smb1.trans2;

import jcifs.Configuration;
import jcifs.internal.smb1.trans.SmbComTransaction;
import jcifs.internal.util.SMBUtil;
import jcifs.util.Hexdump;

/**
 * Trans2 FindNext2 request message for SMB1 directory enumeration continuation.
 * This class implements the TRANS2_FIND_NEXT2 transaction to retrieve subsequent
 * directory entries after a Trans2FindFirst2 request, supporting large directory listings.
 */

import jcifs.internal.fscc.FileStandardInfo;
import jcifs.internal.smb1.trans.SmbComTransaction;
import jcifs.internal.smb1.trans.SmbComTransactionResponse;

/**
 * Trans2 QueryPathInformation response message for file metadata queries.
 * This class handles the response from a TRANS2_QUERY_PATH_INFORMATION request,
 * returning various file information levels based on the requested information level.
 */

```json
{
    "reason": <string>
}
```

The reason message is returned to the client.

## Example Plugin Implementation

        VersionRange versionRange;
        try {
            versionRange = VersionRange.createFromVersionSpec(d.getVersion());
        } catch (InvalidVersionSpecificationException e) {
            // MNG-5368: Log a message instead of returning 'null' silently.
            this.logger.error(
                    String.format(
                            "Invalid version specification '%s' creating dependency artifact '%s'.", d.getVersion(), d),

        // Note: Full testing requires a running OpenSearch cluster
        assertTrue(true);
    }

    public void test_getMessage_returnsCorrectValue() {
        // Test message getter exists
        FessConfig mockConfig = new FessConfig.SimpleImpl() {
            private static final long serialVersionUID = 1L;

            @Override
            public Set<String> getApiPingEsFieldSet() {

import org.codelibs.core.stream.StreamUtil;
import org.codelibs.fess.exception.InvalidQueryException;
import org.codelibs.fess.mylasta.direction.FessConfig;
import org.codelibs.fess.util.ComponentUtil;
import org.lastaflute.core.message.UserMessages;
import org.opensearch.index.query.BoolQueryBuilder;
import org.opensearch.index.query.QueryBuilder;
import org.opensearch.index.query.QueryBuilders;

import jakarta.servlet.http.HttpServletRequest;

/**