We often encounter API’s where we unfortunately have to ‘accept’ HTTP statusses other than the ‘200’-range of success responses. Sometimes '404’s are ‘normal functioning’ for example.
However, what we now have to do is always create a ‘duplicate’ of the Client in order to accept a ‘failure response’ on that specific place in the configurations. Since we don’t want to accept failure responses anywhere else.
It’d be great if we could prevent having to duplicate the client, and if there was just a ‘plugin’ on the HTTP subscriber/publisher/transformer that we could use.
Thanks for reaching out and for clearly explaining your use case.
You’re absolutely right that, at the moment, accepting non-2xx HTTP status codes (such as a 404 that represents expected behavior) requires duplicating the Client to scope that behavior to a specific flow. We understand this results in unnecessary duplication and additional maintenance.
We’ve documented your request and submitted a feature request to our product development team to explore making this configurable at a more granular level.
For now, duplicating the Client remains the only available workaround, but we’ll keep you informed if the team identifies alternative approaches or makes progress on this enhancement.
Thanks again for your feedback; it’s very valuable in helping us improve the platform.