---
title: "Customize web service action handler class"
slug: "customize-web-service-action-handler-class"
description: "Learn how to customize web service action handler classes in Connectivity Studio for both inbound and outbound integrations to enhance functionality."
tags: ["Concept topic"]
updated: 2026-03-20T09:39:52Z
published: 2026-03-20T17:44:08Z
canonical: "docs.staedean.com/customize-web-service-action-handler-class"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.staedean.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Customize web service action handler class

In Connectivity Studio, usually, you can design the integration setup by configuration. Sometimes, it can be required to use a customization. This topic explains the standard web service action handler handler classes in Connectivity Studio and how to customize these classes. Only use customized classes if you really need specific functionality.

### **Standard web service action handler classes**

For web service actions, several standard handler classes are available. Each web service action direction has its own handler classes:

| Document type | Handler class | Description |
| --- | --- | --- |
| Outbound handler classes | BisWsClientHandler | Runs the outbound web service action. For the request message, the target connector must be of type **Azure file storage**. For the response message and error message, the source connector must be of type **Azure file storage**. |
| BisWsClientHandlerV3 | Runs the outbound web service action, using streaming. For the request message, the target connector must be of type **Web service**. For the response message and error message, the source connector must be of type **Web service**. |
| Outbound client HTTP classes | BisWsClientHttpFileRequest | Calls the external web service if files are used to exchange data. The result of the handler class is the input for the web service call. This class also handles the response from the web service. This response is the input for the handler class to process the response in D365 F&SCM. |
| BisWsClientHttpRequest | Calls the external web service if streaming used to exchange data. The result of the handler class is the input for the web service call. This class also handles the response from the web service. This response is the input for the handler class to process the response in D365 F&SCM. |
| Inbound handler classes | BisWsServerHandler | Runs the inbound web service action. For the request message, the source connector must be of type **Azure file storage**. For the response message and error message, the target connector must be of type **Azure file storage**. |
| BisWsServerHandlerV3 | Runs the inbound web service, using streaming. For the request message, the source connector must be of type **Web service**. For the response message and error message, the target connector must be of type **Web service**. |

**Customize web service action handler class - Outbound**

You can use a customized outbound web service action handler class. To do so, extend a standard outbound web service action handler class. For a customized outbound web service action handler class, you can change the methods as desired. The commonly changed methods are:

- runGet
- rungetResponseMessage
- rungetErrorMessage
- HandleHttpRequest
- RunPost
- unPostResponseMessage
- RunPostRequestMessage
- RunPostErrorMessage
- OnAfterPostResponseMessage
- GetClassDescription

### **Customize web service action Client HTTP class - Outbound**

To run the web service HTTP request, a separate class is used. If your HTTP request works different compared to the standard HTTP request, you can extend one of the standard client HTTP classes or create your own client HTTP class. Make sure, it implements the same interface with the same methods as exist in the standard client HTTP classes.

The required interface is: ![](https://cdn.document360.io/da662430-6a41-47b1-8c7e-7e4ac37a9756/Images/Documentation/Images/File%20imageCDBB62F7-4DF4-4C48-9E78-5F17435CAC1A)The required methods are: ![](https://cdn.document360.io/da662430-6a41-47b1-8c7e-7e4ac37a9756/Images/Documentation/Images/File%20image166FEB49-1BBD-4F1A-BBFD-9EFB55D1AFA5)

### **Customize web service action handler class - Inbound**

You can use a customized inbound web service action handler class. To do so, extend a standard inbound web service action handler class. For a customized inbound web service action handler class, you can change the methods as desired. The commonly changed methods are:

- 
  - Runget
  - OnGetRequestMessage
  - onGetResponseMessage
  - ongetErrorMessage
  - RunPost
  - onPostRequestMessage
  - onPostResponsemessage
  - OnPostErrormessage
  - GetClassDescription

## Related

- [Customize connector handler class](/customize-connector-handler-class.md)
- [Customize document handler class](/customize-document-handler-class.md)
- [Customize message handler class](/customize-message-handler-class.md)
- [Customize BIS entity class](/customize-bis-entity-class.md)
- [Develop custom code](/develop-custom-code.md)
- [Set up web service action - Outbound](/set-up-web-service-action-outbound.md)
- [Set up web service action - Inbound](/set-up-web-service-action-inbound.md)